Releases: fivetran/dbt_amazon_ads_source
v0.5.0 dbt_amazon_ads_source
PR #24 includes the following updates:
Breaking Change for dbt Core < 1.9.6
Note: This is not relevant to Fivetran Quickstart users.
Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core. This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:
[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `amazon_ads` in file
`models/src_amazon_ads.yml`. The `freshness` top-level property should be moved
into the `config` of `amazon_ads`.
IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.
If you are using dbt Core < 1.9.6 and want to continue running Amazon Ads freshness tests, please elect one of the following options:
- (Recommended) Upgrade to dbt Core >= 1.9.6
- Do not upgrade your installed version of the
amazon_ads_sourcepackage. Pin your dependency on v0.4.0 in yourpackages.ymlfile. - Utilize a dbt override to overwrite the package's
amazon_adssource and apply freshness via the old top-level property route. This will require you to copy and paste the entirety of thesrc_amazon_ads.ymlfile and add anoverrides: amazon_ads_sourceproperty.
Under the Hood
- Updated the package maintainer PR template.
Documentation
- Corrected references to connectors and connections in the README. (#23)
- Updated LICENSE.
- Updated README headers.
Full Changelog: v0.4.0...v0.5.0
v0.4.0 dbt_amazon_ads_source
PR #21 includes the following updates:
Feature Update: Conversion support
-
We have added conversion metrics by default to the following staging models:
stg_amazon_ads__ad_group_level_reportstg_amazon_ads__advertised_product_reportstg_amazon_ads__campaign_level_reportstg_amazon_ads__targeting_keyword_reportstg_amazon_ads__search_term_ad_keyword_report
-
The conversion metrics are the following:
purchases_30_d: Number of attributed conversion events occurring within 30 days of an ad click.sales_30_d: Total value of sales occurring within 30 days of an ad click.
-
To bring in other conversion fields (
purchases_same_sku_30_d,sales_14_d, etc.), please refer to our passthrough column variables.
Under the hood: Backwards compatibility
- In the event that you were already passing the above fields in via our passthrough columns, the package will dynamically avoid "duplicate column" errors.
- This was done via the new
amazon_ads_fill_pass_through_columnsandamazon_ads_add_pass_through_columnsmacros to ensure that the new conversion fields are backwards compatible with users who have already included them via passthrough fields.
The above new field additions are breaking changes for users who were not already bringing in conversion fields via passthrough columns.
Contributors
Full Changelog: v0.3.0...v0.4.0
v0.3.0 dbt_amazon_ads_source
PR #17 includes the following updates:
Feature update 🎉
- Unioning capability! This adds the ability to union source data from multiple amazon_ads connectors. Refer to the Union Multiple Connectors README section for more details.
Under the hood 🚘
- Updated tmp models to union source data using the
fivetran_utils.union_datamacro. - To distinguish which source each field comes from, added
source_relationcolumn in each staging model and applied thefivetran_utils.source_relationmacro. - Updated tests to account for the new
source_relationcolumn.\
Full Changelog: v0.2.0...v0.3.0
v0.2.0 dbt_amazon_ads_source
PR #11 includes the following updates:
🚨 Breaking changes
- This release is labeled breaking to reflect the Fivetran Amazon Ads connector's upgrade from version 2 to 3 of the Sponsored Products API. Further details are also available in the June 2023 release notes.
- Removed:
- Columns
campaign_type,daily_budget,placement, andpremium_bid_adjustmentfrom thecampaign_historytable.
- Columns
🎉 Features
- Added:
- Columns
native_language_localeto thekeyword_historytable. - Columns
budget,budget_type, andeffective_budgetto thecampaign_historytable.
- Columns
- Updated documentation with descriptions of the new columns.
🚘 Under the Hood
- Any
idfields that were not already data type STRING have been casted to STRING. This ensures smoother joins in downstream models. get_*_columnmacros now set the data type of theidcolumn from INTEGER to STRING.- Updated testing seed data to reflect the column changes.
- Updated discrepancies between seed data and documentation.
PR #8 includes the following updates:
- Incorporated the new
fivetran_utils.drop_schemas_automationmacro into the end of each Buildkite integration test job. - Updated the pull request templates.
Full Changelog: v0.1.1...v0.2.0
v0.1.1 dbt_amazon_ads_source
Happy Friday and international fun at work day!
Bugfix releases may not be the most fun for others, but I always have fun pushing patch updates to make sure these packages are up to date and working as intended. I have fun doing this each and everyday, but I will have even more fun doing it today! 🕺
Bug Fixes
- The
portfolio_historysource config has been adjusted to be more accurate and allow for full project compilation in dbt-core >=1.4.0. (#5)
Full Changelog: v0.1.0...v0.1.1
v0.1.0 dbt_amazon_ads_source
Happy Year of the Rabbit! 🐇 This is the initial release of this package! 🎉
📣 What does this dbt package do?
- Materializes Amazon Ads staging tables, which leverage data in the format described by this ERD. These staging tables clean, test, and prepare your Amazon Ads data from Fivetran's connector for analysis by doing the following:
- Names columns for consistency across all packages and for easier analysis
- Adds freshness tests to source data
- Adds column-level testing where applicable. For example, all primary keys are tested for uniqueness and non-null values.
- Generates a comprehensive data dictionary of your Amazon Ads data through the dbt docs site.
- These tables are designed to work simultaneously with our Amazon Ads transformation package.
- For more information refer to the README.