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