[Feature] <title> Where does the account history table come from?

[bparbhurestore]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

I'm trying to understand the source models a bit better and I'm trying to traceback the ads account_history table or the stg_google_ads__account_history_tmp and the stg_google_ads__account_history table. These source models feed the google_ads transformations that are being used in the transformations-based package. This shows up in the url reports that get used in that package. I don't see much transparency in terms of how this is created and would like to know more. Is the process proprietary?

How would you implement this feature?

Ad much more deliberate sources in our dbt_project sources. As the sources listed do not describe this table.

Describe alternatives you've considered

I'm not sure.

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance.
• No.

Anything else?

Yes, can there be a definition of how the stg_google_ads__account_history_tmp table is created.

[fivetran-joemarkiewicz]

Hi @bparbhurestore thanks for opening this feature request inquiry. This package (and all other Fivetran dbt packages) leverage the data synced directly from the respective Fivetran connector. You can see in our README within the what does this dbt package do section that this package will:

leverage data in the format described by this ERD. These staging tables clean, test, and prepare your Google Ads data from Fivetran's connector for analysis

In the case of how the stg_google_ads__account_history_tmp table is created, this dbt package will read from the source table account_history which is synced by the Fivetran Google Ads connector. You will be able to see more specifics around the source information in the src.yml file.