PR #82 includes the following updates:

Breaking Changes

Source Package Consolidation

• Removed the dependency on the fivetran/google_ads_source package.
  • All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
  • If you reference fivetran/google_ads_source in your packages.yml, you must remove this dependency to avoid conflicts.
  • Any source overrides referencing the fivetran/google_ads_source package will also need to be removed or updated to reference this package.
  • Update any google_ads_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
• As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

dbt Fusion Compatibility Updates

• Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
• Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
  • Removed all dbt_utils.unique_combination_of_columns tests.
  • Removed all accepted_values tests.
  • Moved loaded_at_field: _fivetran_synced under the config: block in src_google_ads.yml.

Under the Hood

• Updated conditions in .github/workflows/auto-release.yml.
• Added .github/workflows/generate-docs.yml.

Full Changelog: v0.14.0...v1.0.0

PR #79 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 (Source PR #68). 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 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

PR #77 introduces the following updates:

Schema Updates

2 total changes • 1 possible breaking change

Feature Updates

• Added criterion_id to the recently introduced google_ads__search_term_report model. This was added to align with other advertising platforms in the downstream Ad Reporting data model, which includes keyword IDs in the combined search report end model.
• Removed keyword_text from the uniqueness test for google_ads__search_term_report in favor of criterion_id.

Under the Hood

• Added a consistency data validation test for google_ads__search_term_report.

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

Schema Updates

3 total changes • 0 possible breaking changes

Feature Updates

• Added the google_ads__using_search_term_keyword_stats variable, which can be used to disable the above transformations related to the new search_term_keyword_stats table. This variable is dynamically set for Fivetran Quickstart users. See README for more details. (#76)
• 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. (#76)

Documentation

• Added Quickstart model counts to README. (#73)
• Corrected references to connectors and connections in the README. (#73)
• Updated the LICENSE. (#76)
• Adjusted README header format. (#76)
• Added discussion of keyword_text qualifiers to the DECISIONLOG. (#76)

Under the Hood

• Removed the horizontal_sum_conversions integrity test, as it is based on a false premise of metrics tying out across different grains, which we discuss here. (#76)
• Added integrity test to verify transformations of the search_term_keyword_stats source table. (#76)
• Added google_ads__using_search_term_keyword_stats variable to the quickstart.yml file.
• Included google_ads__using_search_term_keyword_stats in Buildkite run.

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

PR #66 includes the following updates:

Feature Updates: Conversion Support!

• We have added the following source fields to each google_ads end 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_persist_pass_through_columns macro to ensure that the new conversion fields are backwards compatible with users who have already included them via passthrough fields.
• Added integrity and consistency validation tests within integration_tests folder for the transformation models (to be used by maintainers only).

Contributors

• Seer Interactive
• @fivetran-poonamagate

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

PR #62 includes the following updates:

Bug Fixes

• This package now leverages the new google_ads_extract_url_parameter() (located within the dbt_google_ads_source package) 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

PR #52 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 🚘

• In the source package, 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 and downstream model and applied the fivetran_utils.source_relation macro.
  • The source_relation column is included in all joins in the transform package.
• Updated tests to account for the new source_relation column.

PR #60 includes the following update:

Dependency Updates

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

Under the Hood

• Updates the DECISIONLOG to clarify why there exist differences among aggregations across different grains.

Full Changelog: v0.9.3...v0.10.0

PR #57 includes the following updates:

Bug fixes

• Updated end models to select key columns from the stats source instead of the reports source to avoid introducing null values.

Contributors

• @edwardskatie (PR #54)

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

🎉 Features 🎉

• Added the column currency_code to the following models (PR #48):
  • google_ads__ad_group_report
  • google_ads__ad_report
  • google_ads__campaign_report
  • google_ads__keyword_report
  • google_ads__url_report

Under the Hood:

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

Contributors

• @asmundu (PR #36)

Full Changelog: v0.9.0...v0.9.2

Happy International Gourmet Coffee Day! ☕

I myself enjoy a typical black coffee everyday, but on a day like today I think I will spice it up and try a cortado!

Bug fixes

• Adjusted keyword report to leverage the stats ids as opposed to the history ids to have more accurate reporting. (PR #41)

Contributors

• @jkokatjuhhavoila (PR #41)

Full Changelog: v0.9.0...v0.9.1