Feature: Adding conversions

[fivetran-avinash]

PR Overview

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

This PR will result in the following new package version: 0.7.0

See CHANGELOG for why changes are breaking.

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

Feature Updates: Conversion Support!

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

• Adds a conversion_purchases_value field to each _report end model, representing the value of conversions that occurred on each day for each account, ad, ad squad, campaign and url.
  • Set current variable defaults in the dbt_project.yml to bring in the most used conversion field conversion_purchases by default.
• Adds a total_conversions metric in our end models to track all conversions being brought in by the snapchat_ads_conversion_fields variable.

IMPORTANT: The above new field additions are breaking changes.

Documentation Update

• Documents how to set your own passthrough fields with the variable snapchat_ads__conversion_fields in the README.

Under the Hood

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

Contributors

• Seer Interactive

PR Checklist

Basic Validation

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

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

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

• [NA] 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:

Validated the new tests worked on both dev and integration tests

Integration tests run

Dev run

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

📱

[fivetran-jamie]

switch

[fivetran-joemarkiewicz]

LGTM with just one question and a request to remove some commented out code.

[fivetran-joemarkiewicz]

Same comment from the source if there is a reason we had to use 1.6.0 and not 1.3.0

[fivetran-joemarkiewicz]

Same response from source, this is fine to keep