[Feature] Add conversions

[fivetran-avinash]

PR Overview

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

This PR will result in the following new package version:

See CHANGELOG

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:

• Created a snapchat_ads__conversion_fields variable to pass through additional conversion metrics in the stg_snapchat_ads__ad_hourly_report,stg_snapchat_ads__ad_squad_hourly_report and stg_snapchat_ads__campaign_hourly_report models.
  • Set variable defaults in the dbt_project.yml to bring in the most used conversion field conversion_purchases.
• Ensured backwards compatibility with existing passthrough column variables in these models by creating snapchat_ads_add_pass_through_columns and snapchat_ads_fill_pass_through_columns macro checks for whether these fields already are brought in by the existing passthrough variables. This ensures there are no duplicate column errors if both the new conversion variable and the old passthrough variable are leveraged in either stg_snapchat_ads__*_hourly_report* data model.
• Brought in the conversion_purchases_value field to the above mentioned stg_snapchat_ads__*_hourly_report* model

The above new field additions are 🚨 breaking changes 🚨 for users who were not already bringing in conversion fields via passthrough columns.

Documentation Update

• Documents the ability to transform metrics provided to the snapchat_ads__conversion_fields variable in the README.
• Added new metrics to src and stg yml files.

Under the Hood

• Updated snapchat_*_hourly_report_data seed files with relevant conversion fields for more robust testing.

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:

Compiled models successfully using various permutations of the passthrough columns/conversion fields vars.

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

🛝

[fivetran-joemarkiewicz]

LGTM with just one question, but shouldn't be blocking

[fivetran-joemarkiewicz]

Was there a reason for this change? Is there something in a previous dbt-databricks version that isn't supported in these changes?

[fivetran-jamie]

No real reason, just saw that this was inconsistent with the requirement.txt files of some other packages. Happy to revert if preferable

[fivetran-joemarkiewicz]

Thanks for the clarification. This is fine to keep, I just wanted to make sure there wasn't a particular reason and if we had to change the required dbt version range. But this looks fine to keep thanks!