Not sure if this is suggested somewhere, but in my field, digital marketing, I'm sure there's a pareto distribution of many users using the same sources, with the same config. At the same time, many of these users will likely not be power users, but instead marketers and analysts lacking technical experience. For these sources, I think it's make sense to have a menu of "recipes" or "sensible defaults", which for example Google Ads, one recipe could mean something like: 1. OAuth login (on Airbyte Cloud) 2. Pulling Campaign Performance data with Campaign Name,Impressions, Impr. share,Clicks,Cost,Conversions,Conversion value etc 3. Pre-selects incremental stream with dedup history with pre-defined primary keys and cursor fields. 4. Pre-defined DBT transformations that renames fields from

segment.date

to

Date

,

metrics.cost_micros

to

Cost

and casts them to the proper type I can see how this would reduce the setup time for a source from 5+ hours for Google Ads (for an analyst like myself) to 5min This may not be the market you're primarily going after, but having sources like this would mean that using Airbyte would suddenly be within reach (from a UI standpoint) of the hundreds of thousands marketers our there who are getting ripped off by Funnel.io, Supermetrics etc (in Europe)

I'm sure these points are useful on their own as intermediate steps until the complete thing is realized

In this issue, I’ve mentioned this approach under

Plug-N-Play with popular DBT packages

https://github.com/airbytehq/airbyte/issues/2566 For example, the use case you mention, if you google for

dbt_google_ads

, you could find some packages already built “ready” for analytics… and the community would be free to contribute more of such “recipes” or “sensible defaults”, especially making them compatible with Airbyte (or fill some github issue with requests on how to make the outputs more similar) WDYT?