Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/conversions #21

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Feature/conversions #21

wants to merge 8 commits into from

Conversation

fivetran-reneeli
Copy link

@fivetran-reneeli fivetran-reneeli commented Oct 1, 2024

PR Overview

This PR will address the following Issue/Feature:
Adding conversion metrics

This PR will result in the following new package version:

v0.4.0

breaking change to users who weren't bringing in conversion metrics already through the passthrough variable.

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

Feature update: Conversion Support

  • We have added conversion metrics to the following staging models:

    • ad_group_level_report
    • advertised_product_report
    • campaign_level_report
    • targeting_keyword_report
    • search_term_ad_keyword_report
  • The conversion metrics are the following:

    • purchases_30_d: Number of attributed conversion events occurring within 30 days of an ad click.
    • sales_30_d: Total value of sales occurring within 30 days of an ad click.

Under the hood: Backwards compatibility

  • In the event that you were already passing the above fields in via our passthrough columns, the package will dynamically avoid "duplicate column" errors.
  • This was done via the new google_ads_fill_pass_through_columns and google_ads_add_pass_through_columns macros to ensure that the new conversion fields are backwards compatible with users who have already included them via passthrough fields.

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

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:

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

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

💃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant