Add conversion metrics

[fivetran-jamie]

PR Overview

This PR will address the following Issue/Feature:
add conversions project

This PR will result in the following new package version:

v0.8.0

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

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).
  • 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

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

• dbt run –full-refresh && dbt test
• dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

• The appropriate issue has been linked, tagged, and properly assigned
• All necessary documentation and version upgrades have been applied
• docs were regenerated (unless this PR does not include any code or yml updates)
• BuildKite integration tests are passing
• Detailed validation steps have been provided below

Detailed Validation

Please share any and all of your validation steps:

See validation tests added

If you had to summarize this PR in an emoji, which would it be?

🐦

[fivetran-joemarkiewicz]

@fivetran-jamie this generally looks to go from my end! I was able to test all the passthrough and default override cases and everything looks to be working as expected!

I have a few comments below, but nothing that would be blocking the approval. Once those updates are applied, this should be good to go!

[fivetran-catfritz]

@fivetran-jamie All lgtm!