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

Hub Fix

• v0.1.1 is not working on dbt's hub. This release is to fix this.

dbt 0.19.0 Compatibility

This release introduces compatibility with dbt 0.19.0. There are no known breaking changes.

Initial Release

This is the initial release of this package.

The main focus of the package is to transform the core ad object tables into analytics-ready models, including an 'ad adapter' model that can be easily unioned in to other ad platform packages to get a single view.

Currently the package supports Redshift, BigQuery and Snowflake.