Mapping for Self-Attributing Networks (SANs)

While self-attributing networks give attribution providers a lot of granularity due to the server-to-server integration, the data they give reflects the network's own reporting hierarchy. Singular standardizes the data by mapping it to Singular's internal reporting hierarchy, so that the data is made available in internal BI postbacks for SANs and non-SAN networks in the same way.

The table below details the mapping for SANs. You can reference it when you build your data processing pipeline in the BI platform.

Note that values are only populated when they are provided by the SAN. For example, creative_id may only be available for certain campaign types.

Partner Name network tracker_ campaign_ name tracker_ campaign_ id tracker_sub_ campaign_ name tracker_sub_ campaign_id tracker_ creative_ name tracker_ creative_ id tracker_ publisher_ id tracker_ publisher_ site_ name tracker_ publisher_ site_ id
Adwords (multiple values) e.g. Google Search, Google Display campaign_name campaign_id   adgroup_id   creative_id or video_id placement   placement
Apple Search Ads iOS Search Ads iad-campaign-name iad-campaign-id iad-adgroup-name iad-adgroup-id          
Facebook Facebook Campaign Name Campaign ID AdSet Name AdSet ID Ad Name Ad ID "Facebook", "Instagram", "Audience Network" "Facebook", "Instagram", "Audience Network"  
Snapchat Snapchat campaign_name campaign_id ad_squad_name ad_squad_id ad_name ad_id      
Twitter Twitter campaign_name campaign_id   line_item_id   tweet_id publisher_app_id   publisher_app_id
Yahoo Yahoo Gemini campaign_name campaign_id adgroup_name adgroup_id creative_name creative_id      
Was this article helpful?
0 out of 0 found this helpful