Skip to content

CHANGELOG.md

Latest commit

 

History

History
152 lines (111 loc) · 10.3 KB

CHANGELOG.md

File metadata and controls

152 lines (111 loc) · 10.3 KB
Raw

dbt_amazon_ads v1.3.1

PR #51 includes the following updates:

Feature Updates

  • Adds DuckDB as a supported destination.

dbt_amazon_ads v1.3.0

PR #49 includes the following updates:

Schema/Data Changes (--full-refresh required after upgrading)

1 total change • 1 possible breaking change

Data Model(s) Change type Old New Notes
All models source_relation column (when using a single amazon_ads schema) Empty string ('') <database>.<schema>

Feature Updates

  • Introduces the new (recommended) amazon_ads_sources variable for more robust union data configuration. The oldamazon_ads_union_schemas and amazon_ads_union_databases variables will still be supported. See the README for specific details.

Under the Hood

  • Adds the fivetran_using_source_casing variable for case-sensitive destination support. When enabled, downstream transformations respect source casing to ensure consistent results. See the Additional Configurations section of the README for details.
  • Introduces fivetran_utils.partition_by_source_relation to conditionally include source_relation in partition clauses only when multiplesources are configured.

dbt_amazon_ads v1.2.0

PR #32 includes the following updates:

Documentation

  • Updates README with standardized Fivetran formatting.

Under the Hood

  • In the quickstart.yml file:
    • Adds table_variables for relevant sources to prevent missing sources from blocking downstream Quickstart models.
    • Adds supported_vars for Quickstart UI customization.

dbt_amazon_ads v1.1.0

PR #31 includes the following updates:

Features

  • Increases the required dbt version upper limit to v3.0.0

dbt_amazon_ads v1.0.0

PR #28 includes the following updates:

Breaking Changes

Source Package Consolidation

  • Removed the dependency on the fivetran/amazon_ads_source package.
    • All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
    • If you reference fivetran/amazon_ads_source in your packages.yml, you must remove this dependency to avoid conflicts.
    • Any source overrides referencing the fivetran/amazon_ads_source package will also need to be removed or updated to reference this package.
    • Update any amazon_ads_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
  • As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

dbt Fusion Compatibility Updates

  • Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
  • Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
    • Removed all dbt_utils.unique_combination_of_columns tests.
    • Moved loaded_at_field: _fivetran_synced under the config: block in src_amazon_ads.yml.

Under the Hood

  • Updated conditions in .github/workflows/auto-release.yml.
  • Added .github/workflows/generate-docs.yml.

dbt_amazon_ads v0.5.0

PR #23 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 (Source PR #24). 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:

  1. (Recommended) Upgrade to dbt Core >= 1.9.6
  2. Do not upgrade your installed version of the amazon_ads package. Pin your dependency on v0.4.0 in your packages.yml file.
  3. Utilize a dbt override to overwrite the package's amazon_ads source and apply freshness via the old top-level property route. This will require you to copy and paste the entirety of the src_amazon_ads.yml file and add an overrides: amazon_ads_source property.

Under the Hood

  • Updated the package maintainer PR template.

Documentation

  • Added Quickstart model counts to README. (#21)
  • Corrected references to connectors and connections in the README. (#21)
  • Updated LICENSE.
  • Updated README headers.

dbt_amazon_ads v0.4.0

PR #16 includes the following updates:

Feature Update: Conversions Support

  • We have added conversion metrics to each of the end models by default.
  • 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.

The above new field additions are breaking changes for users who were not already bringing in conversion fields via passthrough columns.

Under the Hood

  • Created amazon_ads_persist_pass_through_columns macro to ensure that the new conversion fields are backwards compatible with users who have already included them via passthrough columns . The package will dynamically avoid "duplicate column" errors.
  • Added integrity and consistency validation tests within integration_tests folder for the transformation models (to be used by maintainers only).
  • Added documentation explaining potential discrepancies across reporting grains. See the DECISIONLOG.md.

dbt_amazon_ads v0.3.0

PR #11 includes the following updates:

Feature update 🎉

Under the hood 🚘

  • In the source package, updated tmp models to union source data using the fivetran_utils.union_data macro.
  • To distinguish which source each field comes from, added source_relation column in each staging and downstream model and applied the fivetran_utils.source_relation macro.
    • The source_relation column is included in all joins in the transform package.
  • Updated tests to account for the new source_relation column.

dbt_amazon_ads v0.2.0

PR #6 includes the following updates:

🚨 Breaking changes

🎉 Features

  • Updated documentation to reference changes in the source package.

🚘 Under the Hood

  • Updated testing seed data to reflect the source seed changes.

PR #4 includes the following updates:

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

dbt_amazon_ads v0.1.0

🎉 This is the initial release of this package! 🎉

📣 What does this dbt package do?

  • Produces modeled tables that leverage Amazon Ads data from Fivetran's connector in the format described by this ERD and builds off the output of our Amazon Ads source package.
  • Provides insight into your ad performance across the following grains:
    • Account, portfolio, campaign, ad group, ad, keyword, and search term
  • Materializes output models designed to work simultaneously with our multi-platform Ad Reporting package.
  • Generates a comprehensive data dictionary of your source and modeled Amazon Ads data through the dbt docs site.