Feature/add conversions

PR Overview

This PR will address the following Issue/Feature: No issue created

This PR will result in the following new package version:

v0.8.0 -- looking at our UI, basic_ad_actions is a child of basic_ad and is included by default with it, but juuuust in case someone doesn't have the new table, let's make it breaking, as it is a schema change.

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

🚨 Breaking Changes 🚨

Incorporates the basic_ad_actions pre-built report in order to grab conversion data. basic_ad_actions is a child table of the already-required basic_ad report, broken down by action_type.
- Addition of the new stg_facebook_ads__basic_ad_actions (and its _tmp counterpart) staging model. Given that this is a schema change for the package, this a breaking change.

Feature Updates

With the inclusion of the basic_ad_actions source table, creates a facebook_ads__basic_ad_actions_passthrough_metrics variable to pass through additional conversion value metrics to downstream models. By default, the package includes only the conversion value calculated using the default attribution window, but your report may include calculations using the other windows defined here. See README for details on how to use the new var.
Adds optimization_goal field to stg_facebook_ads__ad_set_history model. This is defined as the optimization goal this ad set is using, possible values of which are defined here.
Adds conversion_domain field to stg_facebook_ads__ad_history model. This is defined as the domain you've configured the ad to convert to.

Documentation

Documents the ability to transform metrics provided to the facebook_ads__basic_ad_passthrough_metrics variable. See README for details.

PR Checklist

Basic Validation

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

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

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

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

Detailed Validation

Please share any and all of your validation steps:

See Validation tests in transform PR

fivetran / dbt_facebook_ads_source