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 the google_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 the ad_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.

Contributors

• @bnealdefero (#20)

dbt_google_ads_source v0.7.0

Happy Tuesday! 🌮

This release of the dbt_google_ads_source package includes the following updates:

🚨 Breaking Changes 🚨

• The api_source variable is now defaulted to google_ads as opposed to adwords. The Adwords API has since been deprecated by Google and is now no longer the standard API for the Google Ads connector. Please ensure you are using a Google Ads API version of the Fivetran connector before upgrading this package. (#28)
  • Please note, the adwords version of this package will be fully removed from the package in August of 2022. This means, models under models/adwords_connector will be removed in favor of models/google_ads_connector models.

dbt_google_ads_source 0.6.0

Happy Wednesday 🐫

This release of the dbt_google_ads_source package includes the following updates:

🚨 Breaking Changes 🚨

• The account source table has been renamed to be account_history. This has been reflected in this release. (#25)
• The ad_final_url_history model has been removed from the connector. The url fields are now references within the final_urls field within the ad_history table. (#25)
  • Please be aware that the logic in the stg_google_ads__ad_history model for the Google Ads API will only pull through the first url in the final_urls list. This column should contain only one url. However, in the even that two are include a test will warn you that the other urls have been removed from the final model.

google_ads_source 0.5.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_fivetran_utils. The latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt_google_ads_source 0.4.1

Happy Tuesday!

This v0.4.1 release of the dbt_google_source package contains the below changes. Refer to the CHANGELOG for additional information on the below changes.

Bug Fixes

• Renaming of the folder names within the dbt_project.yml to match the current spelling of the /models/ folder names. This allows for the materialization of the tmp models to accurately be materialized as views. (#19)

Contributors

• @NoToWarAlways (#19)

Google Ads API Compatibility

Happy Friday!

This release includes a major upgrade to the Fivetran dbt_google_ads package. This update features:

• Added functionality to use this package if you have switched to the Google Ads API within your Fivetran Google Ads connector. To make this switch you will leverage the api_source variable detailed within the README. PR #18
• Addition of the passthrough metrics to the base models which can then be used by downstream models. PR #18

Shout outs to @DylanBaker for all his help on this upgrade and @leinemann for the suggestion of the passthrough columns! 🎉

UTM Auto Tagging Feature

UTM Auto Tagging Feature Addition

This release includes the following non-breaking additions:

• The addition of the google_auto_tagging_enabled variable which when true allows UTM fields to be auto populated based off the campaign and ad group. Otherwise, the package will leverage the manually UTM tagging. #15

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Postgres Compatibility

🎉 Postgres Compatibility 🎉

This release incorporates Postgres compatibility changes. These changes are non-breaking and only include changes for integration testing and Postgres specific updates to the package.

Fivetran Utils Dependency Update

🚧 Fivetran Utils Dependency Update 🚧

This release includes the following non-breaking changes:

• Update to the packages.yml to reference the recently released Fivetran Utils package. This is a necessary update to ensure this package is compatible with previous dbt releases before dbt v0.20.0 updates take place.