Releases: fivetran/dbt_ad_reporting
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
forcalculation_method: derived
for derived metrics
Contributors
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
andcurrent_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 todbt_utils.generate_surrogate_key
. Since the method for creating surrogate keys differ, we suggest all users do afull-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
andtype
->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 toFalse
in yourdbt_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 🚘
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 thead_reporting__keyword_report
model for the Twitter Ads platform. (#71)
Bugfixes
- The
not_null
test on thead_reporting__keyword_report
has been adjusted to be tested on thekeyword_id
as opposed to thekeyword_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! ❗
dbt_ad_reporting v1.0.1
🎉 Feature Enhancements 🎉
PR #57 incorporates the following change:
- The package now includes a set of pre-defined metrics related to clicks, impressions, and spend (definitions here).
- Refer to the README for the included metrics and instructions on how to use them.
- Note: This requires you to manually add a dependency on the dbt metrics package to use.
Fixes
PR #60 incorporates the following change:
- The LinkedIn Ads schema and database variables were incorrectly documented within the README. The README has been updated to reflect the correct variable names.
linkedin_schema
has been properly updated to reflectlinkedin_ads_schema
linkedin_database
has been updated to reflectlinkedin_ads_database
.
Contributors
dbt_ad_reporting 1.0.0
🚨 Breaking Changes 🚨
PR #54 incorporates these breaking changes:
- The previous
ad_reporting
model has been renamed toad_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'surl_report
model.
🎉 Feature Enhancements 🎉
PR #54 includes the following new features:
- Apple Search Ads has officially been released and added to Ad Reporting.
- In addition to the
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
- This package now leverages
ad_reporting__<platform>_enabled
variables to enable/disable all upstream packages and respective models all in one place. - New corresponding documentation and updated docs for new models.
- This package leverages several different macros in order to successfully build each model and features a
macros_docs.yml
within themacros
directory that provides details for each macro.
dbt_ad_reporting v0.8.0
Happy Tuesday! 🌮
This release of the dbt_ad_reporting
package includes the following updates:
🚨 Breaking Changes 🚨
- The
api_source
variable for the Google Ads package is now defaulted togoogle_ads
as opposed toadwords
. 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)- Please note, the
adwords
version of this package will be fully removed from the package in August of 2022. This means, models undermodels/adwords_connector
will be removed in favor ofmodels/google_ads_connector
models.
- Please note, the
Features
- By default the
ad_reporting
models are now materialized in a customer schema named<target_schema>
+ad_reporting
. This can be adjusted within themodels
section of your rootdbt_project.yml
if desired. (#53)
dbt_ad_reporting 0.7.0
Happy Thursday!
This release of the dbt_ad_reporting
package includes the following updates:
🚨 Breaking Changes 🚨
- The Google Ads dependency has been updated to now reference the latest version of the
dbt_google_ads
package (v0.6.0). This version of the package incorporates new and modified tables within theGoogle 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.