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.
PR #66 includes the following breaking changes:
{{ 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
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.fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].sql -> expression and type -> calculation_method
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.
Happy Wednesday!
This release of the dbt_ad_reporting package includes the following updates:
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)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)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! ❗
PR #57 incorporates the following change:
PR #60 incorporates the following change:
linkedin_schema has been properly updated to reflect linkedin_ads_schema
linkedin_database has been updated to reflect linkedin_ads_database.PR #54 incorporates these breaking changes:
ad_reporting model has been renamed to ad_reporting__url_report and will only include records that have non-null url values for more information on specific filters please refer to each platform package's url_report model.PR #54 includes the following new features:
ad_reporting__url_report model update, we have added five new models:
ad_reporting__account_report
ad_reporting__campaign_report
ad_reporting__ad_group_report
ad_reporting__ad_report
ad_reporting__keyword_search_report
ad_reporting__<platform>_enabled variables to enable/disable all upstream packages and respective models all in one place.macros_docs.yml within the macros directory that provides details for each macro.Happy Tuesday! 🌮
This release of the dbt_ad_reporting package includes the following updates:
api_source variable for the Google Ads package 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. (#53)
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.ad_reporting models are now materialized in a customer schema named <target_schema> + ad_reporting. This can be adjusted within the models section of your root dbt_project.yml if desired. (#53)Happy Thursday!
This release of the dbt_ad_reporting package includes the following updates:
dbt_google_ads package (v0.6.0). This version of the package incorporates new and modified tables within the Google Ads API version of the connector. For more information, refer to the relevant dbt_google_ads and dbt_google_ads_source v0.6.0 release notes.🎉 dbt v1.0.0 Compatibility and TikTok Ads Addition 🎉
ad_reporting model. (#36)Adjusts the require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
Upgrades the package dependencies to refer to the latest individual ad package versions. Additionally, the latest individual ad package versions have a dependency on the latest dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.TikTok Ads has been added as a dependency and is enabled by default. Be sure to disable the models via the README if you do not have a TikTok Ads connector.
For more information refer to the README.
🎉 dbt v1.0.0 Compatibility Pre Release 🎉 An official dbt v1.0.0 compatible version of the package will be released once existing feature/bug PRs are merged.
require-dbt-version to now be within the range [">=1.0.0", "<2.0.0"]. Additionally, the package has been updated for dbt v1.0.0 compatibility. If you are using a dbt version <1.0.0, you will need to upgrade in order to leverage the latest version of the package.
dbt_fivetran_utils. Further, the latest dbt_fivetran_utils package also has a dependency on dbt_utils [">=0.8.0", "<0.9.0"].
dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.