v0.14.0 dbt_google_ads_source

PR #68 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `google_ads` in file
`models/src_google_ads.yml`. The `freshness` top-level property should be moved
into the `config` of `google_ads`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Google Ads freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the google_ads_source package. Pin your dependency on v0.13.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's google_ads source and apply freshness via the old top-level property route. This will require you to copy and paste the entirety of the src_google_ads.yml file and add an overrides: google_ads_source property.

Under the Hood

• Updated the package maintainer PR template.

Full Changelog: v0.13.0...v0.14.0

v0.13.0 dbt_google_ads_source

PR #67 introduces the following updates:

Schema Updates

1 total changes • 0 possible breaking changes

Model/Column	Change type	Old name	New name	Notes
stg_google_ads__search_term_keyword_stats	New Column		criterion_id	Parsed out of keyword_ad_group_criterion field

Full Changelog: v0.12.0...v0.13.0

v0.12.0 dbt_google_ads_source

Schema Updates

2 total changes • 0 possible breaking changes

Model/Column	Change type	Old name	New name	Notes
stg_google_ads__search_term_keyword_stats	New Model			Uses new search_term_keyword_stats source table
stg_google_ads__search_term_keyword_stats_tmp	New Model			Uses new search_term_keyword_stats source table

Feature Updates

• Introduced the google_ads__using_search_term_keyword_stats variable, which can be used to disable transformations related to the new search_term_keyword_stats table included in the above models. See README for more details. (#65)
• Introduced the google_ads__search_term_keyword_stats_passthrough_metrics variable, which can be used to pass through additional metrics fields from the search_term_keyword_stats report to the above models. See README for more details. (#65)

Documentation

• Corrected references to connectors and connections in the README. (#64)
• Updated the LICENSE. (#65)
• Adjusted README header format. (#65)
• Added discussion of keyword_text qualifiers to the DECISIONLOG. (#65)

Full Changelog: v0.11.0...v0.12.0

v0.11.0 dbt_google_ads_source

PR #59 includes the following updates:

Feature Updates: Conversion Support!

• We have added the following source fields to each stg_google_ads__<entity>_stats model:
  • conversions: The number of conversions you've received, across your conversion actions. Conversions are measured with conversion tracking and may include modeled conversions in cases where you are not able to observe all conversions that took place. You can use this column to see how often your ads led customers to actions that you’ve defined as valuable for your business.
  • conversions_value: The sum of monetary values for your conversions. You have to enter a value in the Google Ads UI for your conversion actions to make this metric useful.
  • view_through_conversions: For video campaigns, view-through conversions tell you when an impression of your video ad leads to a conversion on your site. The last impression of a video ad will get credit for the view-through conversion. An impression is different than a “view” of a video ad. A “view” is counted when someone watches 30 seconds (or the whole ad if it’s shorter than 30 seconds) or clicks on a part of the ad. A “view” that leads to a conversion is counted in the conversions column.
• In the event that you were already passing the above fields in via our passthrough columns, the package will dynamically avoid "duplicate column" errors.

The above new field additions are 🚨 breaking changes 🚨 for users who were not already bringing in conversion fields via passthrough columns.

Under the Hood

• Updated the package maintainer PR template.
• Created google_ads_fill_pass_through_columns and google_ads_add_pass_through_columns macros to ensure that the new conversion fields are backwards compatible with users who have already included them via passthrough fields.

Contributors

• Seer Interactive
• @fivetran-poonamagate

Full Changelog: v0.10.1...v0.11.0

v0.10.1 dbt_google_ads_source

PR #54 includes the following updates:

Bug Fixes

• This package now leverages the new google_ads_extract_url_parameter() macro for use in parsing out url parameters. This was added to create special logic for Databricks instances not supported by dbt_utils.get_url_parameter().
  • This macro will be replaced with the fivetran_utils.extract_url_parameter() macro in the next breaking change of this package.

Under the Hood

• Included auto-releaser GitHub Actions workflow to automate future releases.

Full Changelog: v0.10.0...v0.10.1

v0.10.0 dbt_google_ads_source

PR #43 includes the following updates:

Feature update 🎉

• Unioning capability! This adds the ability to union source data from multiple google_ads connectors. Refer to the Union Multiple Connectors README section for more details.

Under the Hood 🚘

• Updated tmp models to union source data using the fivetran_utils.union_data macro.
• To distinguish which source each field comes from, added source_relation column in each staging model and applied the fivetran_utils.source_relation macro.
• Updated tests to account for the new source_relation column.

PR #47 includes the following update:

Dependency Updates

• Removes the dependency on dbt-expectations. Specifically we removed the dbt_expectations.expect_column_values_to_not_match_regex_list test.

Full Changelog: v0.9.5...v0.10.0

v0.9.5 dbt_google_ads_source

Rollback

PR #46 rolls back PR #45

• This was causing conflicting dbt-expectation versions because of the version required in other packages.

Full Changelog: v0.9.4...v0.9.5

v0.9.4 dbt_google_ads_source

PR #45 includes the following updates:

Under the Hood:

• Updates the dbt-expectations dependency to the latest version.
• Updates the DECISIONLOG to clarify why there exist differences among aggregations across different grains.

Full Changelog: v0.9.3...v0.9.4

v0.9.3 dbt_google_ads_source

This release addresses a bug that was introduced via a grain change in the Google Ads connector *_history tables. This bug introduced duplicates and uniqueness test failures in staging *_history models (PR #41)

🐛 Bug fix

• Added the new _fivetran_active field to the get_<table>_history_columns() macros. This will create a null version of the column if _fivetran_active is not found in your source tables yet.
• Added a where coalesce(_fivetran_active, true) filter to the final CTEs of the staging *_history models.

Full Changelog: v0.9.2...v0.9.3

v0.9.2 dbt_google_ads_source

This release of dbt_google_ads_source includes the following changes:

🐛 Bug fix

• Updated configuration to allow the source database to be set as target.database when using Databricks. (#38)

Under the Hood:

• Incorporated the new fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (#37)
• Updated the pull request templates. (#37)

Full Changelog: v0.9.1...v0.9.2