Skip to content

Latest commit

 

History

History
29 lines (23 loc) · 2.6 KB

DECISIONLOG.md

File metadata and controls

29 lines (23 loc) · 2.6 KB
Raw

Snapchat Ads Decision Log

Ads Associated with Multiple Ad Groups and Multiple Campaigns

An ad can be associated with multiple ad squads and therefore multiple campaigns on any given day. Therefore, snapchat_ads__ad_report doesn't contain ad_squad or campaign fields since it reports on an ad level. Similarly, snapchat_ads__campaign_report and snapchat_ads__ad_squad_report do not contain ad fields. This prevents overattributing performance to just one ad.

UTM Filtering

This package contains a snapchat_ads__url_report which provides daily metrics for your utm compatible ads. It is important to note that not all Ads leverage utm parameters. Therefore, this package takes an opinionated approach to filter out any records that do not contain utm parameters or leverage a url within the ad.

If you would like to leverage a report that contains all ads and their daily metrics, I would suggest you leverage the snpapchat_ads__ad_report which does not apply any filtering.

Ad Account Report Metrics Associated with Deleted Entities

Similar to some other Ad Platforms, Snapchat Ads will hard-delete entities (i.e. ads, ad squads, campaigns, accounts) from their *_history tables but retain associated records in their respective *_hourly_report tables. This typically does not pose an issue for our not_null tests on our end models, as most entities have their own <entity>_hourly_report source tables that come with the appropriate entity-level ID. However, snapchat_ads__account_report draws from the ad_hourly_report table, rolls it up to the account level, and joins in the ad_account_id using history tables. Thus, if any ad report record is associated with a deleted ad, campaign, ad squad, or account, the ad_account_id will be null.

We have opted to keep these records in snapchat_ads__account_report, as it may be valuable to know that non-zero ad metrics are associated with deleted entities (though null-account records will be grouped together). However, we have changed the severity of the not_null test on ad_account_id to be warn instead of error.

If you would like to disable this not_null test completely to avoid warnings, add the following to your root project dbt_project.yml:

tests:
  snapchat_ads:
    not_null_snapchat_ads__account_report_ad_account_id:
      +enabled: false

And if you are using the downstream Ad Reporting data models, you'd also want to apply the same change to ad_reporting__account_report:

tests:
  ad_reporting:
    not_null_ad_reporting__account_report_account_id:
      +enabled: false