v1.2.0 dbt_twitter

PR #45 includes the following updates:

Documentation

• Updates README with standardized Fivetran formatting.
• Removes duplicative column yml definitions.

Under the Hood

• In the quickstart.yml file:
  • Adds supported_vars for Quickstart UI customization.

Full Changelog: v1.1.0...v1.2.0

v1.1.0 dbt_twitter

PR #43 includes the following updates:

Features

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

Full Changelog: v1.0.1...v1.1.0

v1.0.1 dbt_twitter

PR #38 includes the following updates:

Bug Fixes

• Updated twitter_ads__promoted_tweet_report and twitter_ads__url_report models to source account_id and promoted_tweet_id fields from stg_twitter_ads__promoted_tweet_report rather than from *_history staging models.
  • Prevents a failure on not_null test that can occur due to *_history tables hard-deleting entities like promoted tweets, while retaining related records in report tables.

Full Changelog: v1.0.0...v1.0.1

v1.0.0 dbt_twitter

PR #36 includes the following updates:

Breaking Changes

Source Package Consolidation

• Removed the dependency on the fivetran/twitter_source package.
  • All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
  • If you reference fivetran/twitter_source in your packages.yml, you must remove this dependency to avoid conflicts.
  • Any source overrides referencing the fivetran/twitter_source package will also need to be removed or updated to reference this package.
  • Update any twitter_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_twitter.yml.

Under the Hood

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

Full Changelog: v0.10.0...v1.0.0

v0.10.0 dbt_twitter

PR #32 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 #31). 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 `twitter_ads` in file
`models/src_twitter_ads.yml`. The `freshness` top-level property should be moved
into the `config` of `twitter_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 Twitter 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 twitter_ads package. Pin your dependency on v0.9.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's twitter_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_twitter_ads.yml file and add an overrides: twitter_ads_source property.

Under the Hood

• Updated the package maintainer PR template.

Full Changelog: v0.9.0...v0.10.0

v0.9.0 dbt_twitter

This release includes the following updates:

Schema Changes

6 total changes • 0 possible breaking changes

Model	Change type	Old name	New name	Notes
twitter_ads__campaign_country_report	New Transform Model			Each record in this table represents the daily performance of ads at the account, campaign, and ad-placement level, segmented by country.
twitter_ads__campaign_region_report	New Transform Model			Each record in this table represents the daily performance of ads at the account, campaign, and ad-placement level, segmented by geographic region.
stg_twitter_ads__campaign_locations_report	New Staging Model			Uses campaign_locations_report source table
stg_twitter_ads__campaign_locations_report_tmp	New Staging Model			Uses campaign_locations_report source table
stg_twitter_ads__campaign_regions_report	New Staging Model			Uses campaign_regions_report source table
stg_twitter_ads__campaign_regions_report_tmp	New Staging Model			Uses campaign_regions_report source table

Feature Updates

• Added the twitter_ads__using_campaign_locations_report and twitter_ads__using_campaign_regions_report variables, which can be used to enable or disable the above transformations related to the campaign_locations_report and campaign_regions_report tables. (#31)
  • These variables are dynamically set for Fivetran Quickstart users, but false by default otherwise. See README for more details.
• Introduced the twitter_ads__campaign_locations_report_passthrough_metrics and twitter_ads__campaign_regions_report_passthrough_metrics passthrough column variables, which can be used to pass through additional metrics fields from their respective source reports to downstream models (twitter_ads__campaign_country_report and twitter_ads__campaign_region_report, respectively). See README for more details. (#31)

Documentation

• Added Quickstart model counts to README. (#30)
• Corrected references to connectors and connections in the README. (#30)
• Fixed broken links to dbt model documentation in the README. (#29)
• Applied minor formatting improvements to the README. (#29)
• Updated LICENSE. (#31)

Under the Hood

• Added data validation tests for the new country and region report end models. (#31)

Full Changelog: v0.8.0...v0.9.0

v0.8.0 dbt_twitter

PR #26 includes the following BREAKING CHANGE updates:

Feature Updates: Native Conversion Support

We have added more robust support for conversions in our data models by doing the following:

• Created the twitter_ads__conversion_fields and twitter_ads__conversion_sale_amount_fields variables to pass through conversion metrics (total number and monetary value, respectively). Conversion metrics are split into these 2 variables due to the N:1 relationship between Twitter conversions and their conversion value fields.
  • By default, twitter_ads__conversion_fields will include conversion_purchases_metric and conversion_custom_metric.
  • By default, twitter_ads__conversion_sale_amount_fields will include conversion_purchases_sale_amount and conversion_custom_sale_amount.
  • These conversion fields will be included in each end model report. Additionally, they will be summed up into new total_conversions and total_conversions_sale_amount columns.
  • See README for more details on how to configure these variables.

Under the Hood

• Ensured the above changes maintain backwards compatibility with existing passthrough column variables.
  • Added a new version of the persist_pass_through_columns() macro in which we can include coalesces and properly check between conversion field values and the existing passthrough columns.
• Added integrity and consistency validation tests within integration_tests for the Twitter Ads transformation models.

Documentation

• Highlighted all metrics included in the package by default. Previously, url_clicks and spend_micro were missing from this README section.
• Documented how to configure the new twitter_ads__conversion_fields and twitter_ads__conversion_sale_amount_fields variables here.
• Added Contributors subsection to README.

Contributors

• Seer Interactive

Full Changelog: v0.7.0...v0.8.0

v0.7.0 dbt_twitter

PR #21 includes the following updates:

Feature update 🎉

• Unioning capability! This adds the ability to union source data from multiple twitter connectors. Refer to the Union Multiple Connectors README section for more details.

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.

PR #18 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.

Full Changelog: v0.6.0...v0.7.0

dbt_twitter v0.6.0

🚨 Breaking Changes 🚨:

PR #14 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 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
• Dependencies on fivetran/fivetran_utils have been upgraded, previously [">=0.3.0", "<0.4.0"] now [">=0.4.0", "<0.5.0"].

dbt_twitter v0.5.1

Happy Wednesday!

This release of the dbt_twitter package includes the following updates:

Fixes

• Fix the package name in the README (#16)

Feature Enhancement

• Addition of the keyword_id to the twitter_ads__keyword_report model. (#15)

Under the Hood

• BuildKite testing integration. (#15)

Contributors

• @johnf (#16)