You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data for snapchat follows this hierarchy: campaign < ad group < ad < creative. We only have impression data down to the ad level (ref: ad_hourly_report).
Currently, in our snapchat__ad_adapter model, we are joining the ad table with creatives, and using the ad_history table to map ad_ids to creative_ids. This table does not always have a 1:1 relationship between ad_ids and creative_ids. Customers can potentially have multiple unique creatives per ad. The creative_id and creative_name should be removed from the snapchat__ad_adapter table as it potentially creates row duplicates for spend & impressions. Creative UTM fields should be OK.
Steps to reproduce
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Metric calculations should only be down to the ad id level.
Project variables configuration
copy dbt_project.yml here
Package Version
copy packages.yml here
Warehouse
BigQuery
Redshift
Snowflake
Postgres
Databricks
Other (provide details below)
Additional context
Screenshots
Please indicate the level of urgency
Are you interested in contributing to this package?
Yes, I can do this and open a PR for your review.
Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed.
No, I'd prefer if someone else fixed this. I don't have the time and/or don't know what the root cause of the problem is.
The text was updated successfully, but these errors were encountered:
Are you a current Fivetran customer?
Fivetran created issue
Describe the bug
Data for snapchat follows this hierarchy: campaign < ad group < ad < creative. We only have impression data down to the ad level (ref:
ad_hourly_report
).Currently, in our
snapchat__ad_adapter
model, we are joining the ad table with creatives, and using thead_history
table to map ad_ids to creative_ids. This table does not always have a 1:1 relationship between ad_ids and creative_ids. Customers can potentially have multiple unique creatives per ad. The creative_id and creative_name should be removed from the snapchat__ad_adapter table as it potentially creates row duplicates for spend & impressions. Creative UTM fields should be OK.Steps to reproduce
Expected behavior
Metric calculations should only be down to the ad id level.
Project variables configuration
copy dbt_project.yml here
Package Version
copy packages.yml here
Warehouse
Additional context
Screenshots
Please indicate the level of urgency
Are you interested in contributing to this package?
The text was updated successfully, but these errors were encountered: