v1.5.0 dbt_ad_reporting

🚨 Breaking Changes 🚨

PR #98 includes the following changes based on the underlying individual package upgrades:

• Amazon Ads dependency upgraded to v0.2.0. Please see the respective upstream Amazon Ads and Amazon Ads Source releases for more details.
• Pinterest Ads dependency upgraded to v0.9.0. Please see the respective upstream Pinterest Ads and Pinterest Ads Source releases for more details.
• Tiktok Ads dependency upgraded to v0.4.0. Please see the respective upstream Tiktok Ads and Tiktok Ads Source

Bug Fixes

• Adding the correct variable name in ad_reporting__url_report for passthrough metrics. (PR #96)

Contributors

• @aleix-cd (PR #96)

Full Changelog: v1.4.0...v1.5.0

v1.4.0 dbt_ad_reporting

🎉 Feature Enhancement 🎉

• Added ad_reporting__<report>_passthrough_metrics variables to easily add common metrics across all platforms into the ad_reporting models! This allows metrics other than the standard clicks, impressions, and cost to be included in the final ad reporting models. See below for a full list of new variables and example metrics to passthrough. (PR #85)
  • It is important to call out that this is only possible if the relevant upstream Ad platform variables have the same metric to be unioned in the roll up model. Please see the README section for details around how to configure the passthrough metrics.
  • Please ensure you exercised due diligence when adding metrics to these models. The metrics added by default (clicks, impressions, and cost) have been vetted by the Fivetran team maintaining this package for accuracy. There are metrics included within the source reports, for example metric averages, which may be inaccurately represented at the grain for reports created in this package. You will want to ensure whichever metrics you pass through are indeed appropriate to aggregate at the respective reporting levels provided in this package.

vars:
  ad_reporting__account_passthrough_metrics:
    - name: conversions
    - name: view_through_conversions
  ad_reporting__campaign_passthrough_metrics: 
    - name: total_shares
    - name: conversions
  ad_reporting__ad_group_passthrough_metrics:
    - name: conversions
    - name: interactions
  ad_reporting__ad_passthrough_metrics: ## For both Ad and URL reports
    - name: conversions
    - name: video_views_captured
  ad_reporting__keyword_passthrough_metrics:
    - name: interactions
  ad_reporting__search_passthrough_metrics:
    - name: conversions
    - name: local_spend_amount

• Addition of the pinterest__using_keywords (default=true) variable that allows users to disable the relevant keyword reports in the downstream Pinterest models if they are not used. (PR #89)

Under the Hood:

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

Contributors

• @aleix-cd (PR #85)

Full Changelog: v1.3.1...v1.4.0

v1.3.1 dbt_ad_reporting

Updates

PR #79 includes the following updates:

• Updated package dependencies for Linkedin Ads v0.7.0, for more information please refer to Linkedin Ads PR #28
• Updated README package dependencies to reflect current package versions

v1.3.0 dbt_ad_reporting

🎉 Introducing Reddit Ads Compatibility 🎉

(PR #83) includes the following feature additions:

• We have added Reddit Ads as another platform to our Ad Reporting package.
• Your Reddit Ads data can now be rolled into the below models:
  • ad_reporting__account_report
  • ad_reporting__campaign_report
  • ad_reporting__ad_group_report
  • ad_reporting__ad_report
  • ad_reporting__url_report

Note: If you are NOT using Reddit Ads, add the below variable to your dbt_project.yml to disable the Reddit Ads models.

vars:
  ad_reporting__reddit_ads_enabled: False ## True by default

🌊 Changes 🌊

Full Changelog: v1.2.1...v1.3.0

dbt_ad_reporting 1.2.1

Happy national sticky bun day! 🐰

Updates

• Updating ad_reporting_metrics.yml to be up to date with dbt Metrics documentation (PR #82)

Bug Fixes

• Enabling additional Snapchat Ads columns in ad_reporting__url_report that were previously mapped to null values. (#81)
  • These columns are: ad_group_id (ad_squad_id), ad_group_name (ad_squad_name), campaign_id and campaign_name.

Under the Hood

• Swapped out calculation_method: expression for calculation_method: derived for derived metrics

Contributors

• @dumkydewilde (#81)

v1.2.0 dbt_ad_reporting

🚨 Breaking Changes 🚨 and 🎉 Feature Enhancements 🎉

Happy Year of the Rabbit! 🐇

PR #75 includes the following new features:

• Amazon Ads has officially been released and added to the Ad Reporting package.
• Your Amazon Ad data can now be rolled into the below models:
  • ad_reporting__account_report
  • ad_reporting__campaign_report
  • ad_reporting__ad_group_report
  • ad_reporting__ad_report
  • ad_reporting__search_report
  • ad_reporting__keyword_report
• Documentation has been updated to include Amazon Ads information.

Notes

• Amazon Ads data does NOT apply to ad_reporting__url_report.
• If you are NOT using Amazon Ads, add the below variable to your dbt_project.yml to disable the Amazon Ads models.

vars:
  ad_reporting__amazon_ads_enabled: False ## True by default

dbt_ad_reporting v1.1.0

🚨 Breaking Changes 🚨:

PR #66 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
• dbt_utils.surrogate_key has also been updated to dbt_utils.generate_surrogate_key. Since the method for creating surrogate keys differ, we suggest all users do a full-refresh for the most accurate data. For more information, please refer to dbt-utils release notes for this update.
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].
• Metric attirbutes have been renamed to be consistent with the latest version of dbt-metrics: sql -> expression and type -> calculation_method

🎉 Features 🎉

• Added ability for a user to allow records having nulls in url fields to be included in the ad_reporting__url_report and the underlying *url_report models. This is done by setting the below variable to False in your dbt_project.yml file. (#72)

vars:
  ad_reporting__url_report__using_null_filter: False # Use this variable to include null urls for ALL upstream ad platform packages enabled in your project. Default is True. 

• Updated README with this information. (#72)

🚘 Under the Hood 🚘

• Disabled the not_null test for ad_reporting__url_report when null urls are allowed. (#72)
• Updated this package's integration_tests/seeds/microsoft_ads_campaign_performance_daily_report_data in light of PR #23 on dbt_microsoft_ads_source.(#68)

dbt_ad_reporting v1.0.4

Happy Wednesday!

This release of the dbt_ad_reporting package includes the following updates:

Feature Enhancement

• The keyword_id field (which is a surrogate key generated from the combination of 'account_id', 'line_item_id', 'segment', and 'placement' fields within the Twitter Ads source) has been added to the ad_reporting__keyword_report model for the Twitter Ads platform. (#71)

Bugfixes

• The not_null test on the ad_reporting__keyword_report has been adjusted to be tested on the keyword_id as opposed to the keyword_text. This is needed as there may be times where keyword historical records may be removed and lose reference in an upstream join. As such, the text may be lost and the null test should be applied to the ID instead. (#71)

Contributors

• @clay-walker for being instrumental in understanding and addressing this issue. (#63)

dbt_ad_reporting 1.0.3

🕷️ Bugfixes 🕷️

• Updated twitter_ads__using_keywords to have consistent defaults. (#70)

dbt_ad_reporting 1.0.2

🕷️ Bugfixes 🕷️

• Updated twitter_ads__using_keywords to have consistent defaults. (#70)

❗ My 🐶 jumped on my arm as I was saving the release before merging to main so this was an accidental release, please look to 1.0.3 for this update. Good thing he's cute! ❗