v0.11.0 dbt_google_ads

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

v0.10.1 dbt_google_ads

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

v0.10.0 dbt_google_ads

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

v0.9.3 dbt_google_ads

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

v0.9.2 dbt_google_ads

🎉 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

v0.9.1 dbt_google_ads

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

dbt_google_ads v0.9.0

🚨 Breaking Changes 🚨:

PR #35 includes the following breaking changes:

• Dispatch update for dbt-utils to dbt-core cross-db macros migration. Specifically {{ dbt_utils.<macro> }} have been updated to {{ dbt.<macro> }} for the below macros:
  • any_value
  • bool_or
  • cast_bool_to_text
  • concat
  • date_trunc
  • dateadd
  • datediff
  • escape_single_quotes
  • except
  • hash
  • intersect
  • last_day
  • length
  • listagg
  • position
  • replace
  • right
  • safe_cast
  • split_part
  • string_literal
  • type_bigint
  • type_float
  • type_int
  • type_numeric
  • type_string
  • type_timestamp
  • array_append
  • array_concat
  • array_construct
• For current_timestamp and current_timestamp_in_utc macros, the dispatch AND the macro names have been updated to the below, respectively:
  • dbt.current_timestamp_backcompat
  • dbt.current_timestamp_in_utc_backcompat
• packages.yml has been updated to reflect new default fivetran/fivetran_utils version, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

🎉 Features 🎉

• For use in the dbt_ad_reporting package, users can now allow records having nulls in url fields to be included in the ad_reporting__url_report model. See the dbt_ad_reporting README for more details (#39).

🚘 Under the Hood 🚘

• Disabled the not_null test for google_ads__url_report when null urls are allowed (#39).

dbt_google_ads 0.8.1

Updates:

• Updates google_ads__ad_report model to get ad_id from ad_stats table rather than from ads_history. (#37)

dbt_google_ads 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. (#34)
• Removal of the google_ads__ad_adapter model. (#34)
• Major updates have also been applied to the dbt_google_ads_source package which is a dependency of this package. Please refer to the v0.8.0 release notes for more details before upgrading your package.
• 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:

This applies to all passthrough metrics within the dbt_google_ads 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 🎉

• Addition of the following new end models. These models were added to provide further flexibility and ensure greater accuracy of your Google Ads reporting. Additionally, these new end models will be leveraged in the respective downstream dbt_ad_reporting models.

  • google_ads__account_report
    • Each record in this table represents the daily performance at the account level.
  • google_ads__campaign_report
    • Each record in this table represents the daily performance of a campaign at the campaign/advertising_channel/advertising_channel_subtype level.
  • google_ads__ad_group_report
    • Each record in this table represents the daily performance at the ad group level.
  • google_ads__keyword_report
    • Each record in this table represents the daily performance at the ad group level for keywords.
  • google_ads__ad_report
    • Each record in this table represents the daily performance at the ad level.
  • google_ads__url_report
    • Each record in this table represents the daily performance of URLs at the ad level.

• Added testing for each end model to ensure granularity and accuracy of the modeled data. (#34)

• README updates for easier navigation and use of the package. (#34)

• Inclusion of additional passthrough metrics within the respective end state models detailed above: (#34)

  • 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

Contributors

• @bnealdefero (#20)

dbt_google_ads v0.7.0

Happy Tuesday! 🌮

This release of the dbt_google_ads 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. (#32)
  • 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.