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)

dbt_twitter 0.5.0

PR #12 includes the following changes:

🚨 Breaking Changes 🚨

• The twitter__ad_adapter has been refactored and renamed to twitter_ads__url_report.
• The twitter__campaign_report has been refactored and renamed to twitter_ads__campaign_report.
• The twitter__line_item_report has been refactored and renamed to twitter_ads__line_item_report.

🎉 Feature Enhancements 🎉

• Addition of the following new end models:

  • twitter_ads__promoted_tweet_report
    • Each record in this table represents the daily performance at the promoted tweet level.
  • twitter_ads__account_report
    • Each record in this table represents the daily performance at the advertiser account level.
  • twitter_ads__line_item_report
    • Each record in this table represents the daily performance at the line item (ad group) level.
  • twitter_ads__keyword_report
    • Each record in this table represents the daily performance at line item level for keywords. This can be disabled by setting the twitter_ads__using_keywords variable to False.
  • twitter_ads__campaign_report
    • Each record in this table represents the daily performance at the campaign level.
  • twitter_ads__url_report
    • Each record in this table represents the daily performance at the URL level.

• Inclusion of passthrough metrics:

  • twitter_ads__line_item_report_passthrough_metrics
  • twitter_ads__campaign_report_passthrough_metrics
  • twitter_ads__line_item_keywords_report_passthrough_metrics
  • twitter_ads__promoted_tweet_report_passthrough_metrics - These metrics will be passed to the account report as well.

This applies to all passthrough columns within the dbt_twitter package and not just the twitter_ads__line_item_report_passthrough_metrics example.

vars:
  twitter_ads__line_item_report_passthrough_metrics:
    - name: "my_field_to_include" # Required: Name of the field within the source.
      alias: "field_alias" # Optional: If you wish to alias the field within the staging model.

• README updates for easier navigation and use of the package.
• Included grain uniqueness tests for each end model.

twitter 0.4.0

🎉 dbt v1.0.0 Compatibility 🎉

🚨 Breaking Changes 🚨

• 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.
  • For help upgrading your package, I recommend reviewing this GitHub repo's Release Notes on what changes have been implemented since your last upgrade.
  • For help upgrading your dbt project to dbt v1.0.0, I recommend reviewing dbt-labs upgrading to 1.0.0 docs for more details on what changes must be made.
• Upgrades the package dependency to refer to the latest dbt_twitter_source. Additionally, the latest dbt_twitter_source package has 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"].
  • Please note, if you are installing a version of dbt_utils in your packages.yml that is not in the range above then you will encounter a package dependency error.

dbt 0.20.0 Compatibility

🎉 dbt 0.20.0 Compatibility 🎉

🚨 This is a breaking change! 🚨 dbt v0.20.0 or greater is required for this release. If you are not ready to upgrade, consider using a previous release of this package.

Additional considerations when upgrading to this package:

• This package utilizes the latest v0.7.x release of the dbt-labls/dbt_utils package. If your project also utilizes a version of the fishtown-analytics/dbt_utils package then you will receive a duplicate package error. If this is the case you will need to consider upgrading your other packages to be compatible with this update or use a previous release of this package.
• Similar to the above point, all previous Fivetran dbt packages utilize the fishtown-analytics/dbt_utils package and you will need to upgrade all Fivetran dbt packages to the latest dbt 0.20.0 compatibility releases in order for your packages to run without package conflicts.

Postgres Compatibility

🎉 Postgres Compatibility 🎉

This release incorporates Postgres compatibility changes. These changes are non-breaking and only include changes for integration testing and Postgres specific updates to the package.

Databricks Compatibility

This release incorporates the following non-breaking changes:

• Databricks compatibility

Custom Schema Update

🚨 This update introduces a breaking changes in the form of custom schemas to output models into a respective <target.schema>+_twitter_ads schema. Refer to the ReadMe for more details. 🚨

The release also:

• Incorporates Github pages for easy dbt docs hosting
• Minor documentation updates