dbt_google_ads_source 0.8.0
🚨 Breaking Changes 🚨
- The
adwords
api version of the package has been fully removed. As the Fivetran Google Ads connector now requires the Google Ads API, this functionality is no longer used. (#29) - The declaration of passthrough variables within your root
dbt_project.yml
has changed. To allow for more flexibility and better tracking of passthrough columns, you will now want to define passthrough metrics in the following format: (#29)
This applies to all passthrough metrics within the
dbt_google_ads_source
package and not just thegoogle_ads__ad_stats_passthrough_metrics
example.
vars:
google_ads__ad_stats_passthrough_metrics:
- name: "my_field_to_include" # Required: Name of the field within the source.
alias: "field_alias" # Optional: If you wish to alias the field within the staging model.
🎉 Feature Enhancements 🎉
PR #29 includes the following changes:
-
Addition of the following staging models which pull from the source counterparts. The inclusion of the additional
_stats
source tables is to generate a more accurate representation of the Google Ads data. For example, not all Ad types are included within thead_stats
table. Therefore, the addition of the further grain reports will allow for more flexibility and accurate Google Ad reporting.stg_google_ads__account_stats
stg_google_ads__ad_group_criterion_history
stg_google_ads__ad_group_stats
stg_google_ads__campaign_stats
stg_google_ads__keyword_stats
-
Inclusion of additional passthrough metrics:
google_ads__ad_group_stats_passthrough_metrics
google_ads__campaign_stats_passthrough_metrics
google_ads__keyword_stats_passthrough_metrics
google_ads__account_stats_passthrough_metrics
-
README updates for easier navigation and use of the package.
-
Addition of identifier variables for each of the source tables to allow for further flexibility in source table direction within the dbt project.
-
Included grain uniqueness tests for each staging table.