Fivetran's ad reporting dbt package. Combine your Facebook, Google, Pinterest, LinkedIn, Twitter, Snapchat, Microsoft, TikTok, Reddit, Amazon, and Apple Search advertising metrics using this package.
account_id test in ad_reporting__account_report to warn. This is required since Snapchat can hard-delete records from the history tables, but not from the reporting tables. This ensures that accurate statistics are being reported and production pipelines aren't failing (PR #110).
Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.7.0...v1.7.1
PR #103 includes the following update.
Identifiers for the following packages have been updated for consistency with the source name and compatibility with the union schema feature. See the package's changelog for a full list of changes.
Linkedin ads updates:
tmp staging models from views to tables. This is to bring the materializations into alignment with other ad reporting packages and eliminate errors in Redshift.dbt_linkedin_source from linkedin to linkedin_ads. This was to bring the naming used in this package in alignment with our other ad packages and for compatibility with the union schema feature. If you are using this source, you will need to update the name.Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.6.1...v1.7.0
ad_reporting__ad_report --> ad_report in order to avoid the dunder(__) keyword. (PR #105)Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.6.0...v1.6.1
PR #100 includes the following updates:
[">=1.6.0", "<2.0.0"]. Be sure to upgrade your dbt-core version when upgrading this package to avoid dbt version compatibility errors.ad_reporting__ad_report.yml semantic model which is required to define metrics.metricflow_time_spine.sql which is required by Metricflow. This will be deprecated in future releases. If you have already created a metricflow_time_spine.sql model in your project, you will need to disable it for this package by setting the variable ad_reporting__metricflow_time_spine_enabled to false in your project.## root dbt_project.yml
vars:
ad_reporting__metricflow_time_spine_enabled: false ## true by default
dbt_date:time_zone which is used by the dbt_date.get_base_dates macro within the metricflow_time_spine model. This variable is nested under the ad_reporting hierarchy in the variables config and should not affect any global declarations if you leverage the dbt_date package in your own environment.
America/Los_Angeles, but you may be able override this in your own root project.## root dbt_project.yml
vars:
"dbt_date:time_zone": "America/Chicago" # Default is "America/Los_Angeles"
Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.5.0...v1.6.0
PR #98 includes the following changes based on the underlying individual package upgrades:
ad_reporting__url_report for passthrough metrics. (PR #96)Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.4.0...v1.5.0
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)
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
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)fivetran_utils.drop_schemas_automation macro into the end of each Buildkite integration test job. (PR #86)Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.3.1...v1.4.0
(PR #83) includes the following feature additions:
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.ymlto disable the Reddit Ads models.
vars:
ad_reporting__reddit_ads_enabled: False ## True by default
Full Changelog: https://github.com/fivetran/dbt_ad_reporting/compare/v1.2.1...v1.3.0
Happy national sticky bun day! 🐰
ad_reporting_metrics.yml to be up to date with dbt Metrics documentation (PR #82)ad_reporting__url_report that were previously mapped to null values. (#81)
calculation_method: expression for calculation_method: derived for derived metricsHappy Year of the Rabbit! 🐇
PR #75 includes the following new features:
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
Notes
ad_reporting__url_report.dbt_project.yml to disable the Amazon Ads models.vars:
ad_reporting__amazon_ads_enabled: False ## True by default