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

BUG - [Snapchat Ads creative id ad adapter model] #8

Closed
9 tasks
fivetran-sheringuyen opened this issue Feb 18, 2022 · 0 comments
Closed
9 tasks

BUG - [Snapchat Ads creative id ad adapter model] #8

fivetran-sheringuyen opened this issue Feb 18, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@fivetran-sheringuyen
Copy link
Contributor

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 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

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. 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.
@fivetran-sheringuyen fivetran-sheringuyen added the bug Something isn't working label Feb 18, 2022
@fivetran-reneeli fivetran-reneeli mentioned this issue Mar 10, 2022
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant