Our company likes to organize and use a shared schema for all of our Google Ads data. However, there are three issues with the new connector after Fivetran switched from one report per connector vs one schema per connector that are incompatible with our workflow:

1) We don't get to choose different clients for each report that we're building. For example, we have one set of clients that we're building reports for with an age/gender breakdown, but because universal app campaigns cannot use breakdowns, we also have to create a separate connector specifically for app campaigns. However, this only applies to 4 of our clients--if we want to keep it in the same schema, we would be syncing in 80+ clients and be filtering down to just 4.

2) We don't get to choose different conversion windows for each report. In our attribution methodology, we use both the default 30 day attribution window and the 1 day attribution window. This means for every single type of connector, we also have to split it to different schemas / datasets in our warehouse, leading to things be significantly more disorganized.

3) When we build new reports, the sync does not count as historical. So because of the size of our Google Ads account, we could easily end up syncing 10mil+ new rows if we build a new report inside an existing connector. That means each time we are creating something that should register as a historical sync, we need to create a new schema. I opened up a separate issue with support about this, but want to flag here as well.