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.
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_adaptermodel, we are joining the ad table with creatives, and using thead_historytable 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
Package Version
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?