For Media Agencies and Market Research Firms
Prior to campaign launch, client should consider the following and alert the Audience Project Manager immediately with any applicable information or questions/concerns so that Audience can accurately track the campaign. To achieve maximum feasibility for the Exposed and Control sample, it is recommended that all media be tagged prior to campaign launch if possible. The following are key points to keep in mind.
AD SERVER
Which ad server(s) is the agency using? See Appendix A
If more than one ad server, which site(s) and placements are running in which ad server?
Be sure to connect Audience with the person who will be handling the tagging, so that Audience can reach out if there are any technical needs or questions.
IMPLEMENTATION
Have you received the “Audience Campaign Onboarding” spreadsheet from the Audience Project Manager?
Are all creatives tagged with an Audience pixel tag?
Make sure the Audience pixel tag contains the Audience campaign ID that was provided to you for the particular campaign by the Audience Project Manager.
Agency should always implement their cache-buster on Audience's tag in place of Audience's cache-buster placeholder. If this is not possible, then the Audience Project Manager should be advised.
REPORTING
To enable Lucid to accurately monitor the campaign tracking, client should set up a one-time automated delivery report. This report functions as an impressions discrepancy troubleshooting tool. Please note, this outlines the report setup and cadence - this is not a request for a login or general reporting access to your ad server.
Send to: deliveryreports@cint.com
How often to send: Daily.
Date range of the data should be cumulative. Include data representing the entire date range of the tagged media.
Name/title of report: Include the full campaign name that was provided by Lucid. If possible, include the Lucid campaign ID.
Type of file: CSV.
See Appendix A for columns of data to include.
SITE-SERVED
Are there any site-served 1x1s in the media plan?
On which publisher(s)?
Which placements and creatives?
Is a placement running across web and app?
Which sites/apps?
Agency should break out the placement by web OR app and name it accordingly.
Does the publisher’s ad server have space for multiple 1x1s in a particular creative?
If Audience sends a wrapped/piggybacked tag, publisher should be reminded not to also implement the original agency 1x1 in addition to the wrapped tag. This would cause the agency’s tracking to be duplicated. Wrapped tags are only used when the publisher explicitly mentions that only one 1x1 is acceptable.
APPENDIX A
Ad Servers and the Corresponding Data To Include in Delivery Reports
ACE
Campaign Name
Date
Site Name
Placement Name
Creative Name
Impressions Tracked
Adobe Ad Cloud DSP
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the ${TM_SITE_ID_NUM} macro)
Placement Name
Placement ID (corresponding with the ${TM_PLACEMENT_ID_NUM} macro)
Creative Name
Creative ID (corresponding with the ${TM_AD_ID_NUM} macro)
Environment / Platform Type
Impressions Tracked
Amobee DSP
Campaign Name
Campaign ID
Date
Placement Name
Placement ID (corresponding with the $!{LINE_ITEM_ID} macro)
Creative Name
Creative ID (corresponding with the $!{CREATIVE_ID} macro)
Environment
Platform Type
Impressions Tracked
AOL One
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the ${campaignId} macro)
Placement Name
Placement ID (corresponding with the ${bidId} macro)
Creative Name
Creative ID (corresponding with the ${creativeId} macro)
Environment
Platform Type
Impressions Tracked
AppNexus (Xandr)
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the ${SITE_ID} macro)
Placement Name
Placement / Line Item ID (corresponding with the ${CPG_ID} macro)
Creative Name
Creative ID (corresponding with the ${CREATIVE_ID} macro)
Environment
Platform Type
Impressions Tracked
Atlas
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the {{SITE.ID}} macro)
Placement Name
Placement ID (corresponding with the {{PLACEMENT.ID}} macro)
Creative Name
Creative ID (corresponding with the {{AD.ID}} macro)
Impressions Tracked
Beeswax
Campaign ID
Campaign Name
Line Item ID
Line Item Name
Creative ID
Creative Name
Impressions
Date
Celtra
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the {celtraSupplierId} macro)
Placement Name
Placement ID (corresponding with the {celtraPlacementId} macro)
Creative Name
Creative ID (corresponding with the {celtraCreativeId} macro)
Impressions Tracked
DBM
Campaign Name
Date
App/URL Name
App/URL ID (corresponding with the ${UNIVERSAL_SITE_ID} macro)
Line Item Name
Line Item ID (corresponding with the ${CAMPAIGN_ID} macro)
Creative Name
Creative ID (corresponding with the ${CREATIVE_ID} macro)
Impressions Tracked
DCM
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the %esid! macro)
Placement Name
Placement ID (corresponding with the %epid! macro)
Creative Name
Creative ID (corresponding with the %ecid! macro)
Environment
Platform Type
Impressions Tracked
DFP
Date
Order
Order ID
Line item
Line item ID
Ad Unit
Ad Unit ID
Creative
Creative ID
Master and Companion creative
Master and Companion creative ID
Environment
Total impressions
Eyeview
Campaign Name
Date
Site Name
Site ID (corresponding with the %site_id% macro)
Placement Name
Placement ID (corresponding with the %placement_id% macro)
Creative Name
Creative ID (corresponding with the %creative_id% macro)
Impressions Tracked
Flashtalking
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the [%siteID%] macro)
Placement Name
Placement ID (corresponding with the [%placementID%] macro)
Creative Name
Creative ID (corresponding with the [%creativeID%] macro)
Impressions Tracked
FreeWheel
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the #{site.title} macro)
Placement Name
Placement ID (corresponding with the #{ad.placement.name} macro)
Creative Name
Creative ID (corresponding with the #{ad.creative.name} macro)
Impressions Tracked
Innovid
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the {iv_publisherid} macro)
Placement Name
Placement ID (corresponding with the {iv_placementid} macro)
Creative Name
Creative ID (corresponding with the {iv_creativeid} macro)
Impressions Tracked
LKQD
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the $$siteid$$ macro)
Placement Name
Placement ID (corresponding with the $$dealid$$ macro)
Creative Name
Creative ID (corresponding with the $$creativeid$$ macro)
Environment
Platform Type
Impressions Tracked
MediaMath
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the [BID_ATTR.site_id] macro)
Placement Name
Placement ID (corresponding with the [BID_ATTR.ad_id] macro)
Creative Name
Creative ID (corresponding with the [AD_ATTR.creative] macro)
Environment
Platform Type
Impressions Tracked
PulsePoint
Campaign Name
Campaign ID
Date
Publisher Name
Publisher ID (corresponding with the %%PID%% macro)
Ad Group Name
Ad Group ID (corresponding with the %%ADGRPID%% macro)
Ad Size (corresponding with the %%ADSIZE%% macro)
Impressions Tracked
RUI
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the <!--#APPSTORE_BUNDLE_ID--> macro)
Placement Name
Placement ID (corresponding with the <!--#LINE_ID--> macro)
Creative Name
Creative ID (corresponding with the <!--#CREATIVE_ID--> macro)
Environment (identifying desktop vs mobile app vs mobile web)
Impressions Tracked
Servo
Campaign Name
Date
Site Name
Site ID (corresponding with the $$_CDID_$$ macro)
Placement Name
Placement ID (corresponding with the $$_PLACEMENTID_$$ macro)
Creative Name
Creative ID (corresponding with the $$_CREATIVEID_$$ macro)
Impressions Tracked
Specific Media
Campaign Name
Date
Site Name
Site ID (corresponding with the <sid> macro)
Placement Name
Placement ID (corresponding with the <lid> macro)
Creative Nam
Creative ID (corresponding with the <bid> macro)
Impressions Tracked
Sizmek
Campaign Name
Campaign ID (corresponding with the [%tp_CampaignID%] macro)
Date
Site Name
Site ID (corresponding with the [%tp_SiteID%] macro)
Placement Name
Placement ID (corresponding with the [%tp_PlacementID%] macro)
Ad Name
Ad ID (corresponding with the [%tp_AdID%] macro)
Mobile Device Info
Device Type
Mobile OS
Impressions Tracked
SpotX
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the $CHANNEL_ID macro)
Placement Name
Placement ID (corresponding with the $PUBLISHER_ID macro)
Creative Name
Creative ID (corresponding with the $SPOT_MARKET_ID macro)
Device Type
Mobile OS
Impressions Tracked
Teads
Campaign Name
Campaign ID
Date
Placement Name
Placement ID (corresponding with the [GID] macro)
Creative Name
Creative ID (corresponding with the [CID] macro)
Device Type
Mobile OS
Impressions Tracked
The Trade Desk
Campaign Name
Campaign ID
Date
Site Name
Site ID (corresponding with the %%TTD_SITE%% macro)
Placement Name
Placement ID (corresponding with the %%TTD_CAMPAIGNID%% macro)
Creative Name
Creative ID (corresponding with the %%TTD_CREATIVEID%% macro)
Impressions Tracked
Tremor
Campaign Name
Date
Site Name
Site ID (corresponding with the ###PUBLISHER_ID### macro)
Placement Name
Placement ID (corresponding with the ###AD_ID### macro)
Creative Name
Impressions Tracked
Tremor (Alphonso)
Campaign Name
Date
Site Name
Placement Name
Placement ID (corresponding with the [LINE_ID] macro)
Creative Name
Creative ID (corresponding with the [CREATIVE_ID] macro)
Impressions Tracked
Trueffect
Campaign Name
Date
Site Name
Site ID (corresponding with the @@SIID@@ macro)
Placement Name
Placement ID (corresponding with the @@PLID@@ macro)
Creative Name
Creative ID (corresponding with the @@CRID@@ macro)
Impressions Tracked
Turn
Campaign Name
Date
Site Name
Site ID (corresponding with the $!{SITE_ID} macro)
Placement Name
Placement ID (corresponding with the $!{PACKAGE_ID} macro)
Creative Name
Creative ID (corresponding with the $!{CREATIVE_ID} macro)
Impressions Tracked
Vindico
Campaign Name
Date
Site Name
Site ID (corresponding with the %V-SITE-ID% macro)
Placement Name
Placement ID (corresponding with the %V-OTLT-ID macro)
Creative Name
Creative ID (corresponding with the %V-INAM-ID% macro)
Impressions Tracked
Xaxis
Campaign Name
Date
Site Name
Site ID (corresponding with the ${TAG_ID} macro)
Placement Name
Placement ID (corresponding with the ${CP_ID} macro)
Creative Name
Creative ID (corresponding with the ${CREATIVE_ID} macro)
Impressions Tracked
YFN
Campaign Name
Campaign ID
Date
Site Name
Site ID
Placement Name
Placement ID (corresponding with the ${placement_id} macro)
Creative Name
Creative ID (corresponding with the ${advertisement_id} macro)
Impressions Tracked
Other (not listed)
APPENDIX B
About the Audience tag: Pixel Vendor Implementation Guide
Pixel Tagging and Tracking Checklist
For Publishers
Prior to campaign launch, client should consider the following and alert the Audience Project Manager immediately with any applicable information or questions/concerns so that Audience can accurately track the campaign. The following are key points to keep in mind.
AD SERVER
Which ad server(s) is the publisher using?
If more than one ad server, which placements are running in which ad server?
Does publisher’s ad server have a macro for cache-buster (random number generator)?
Be sure to connect Audience with the person who will be handling the tagging, so that Audience can reach out if there are any technical needs or questions.
IMPLEMENTATION
Are all creatives tagged with an Audience pixel tag?
Make sure the Audience pixel tag contains the Audience campaign ID that was provided to you for the particular campaign by the Proof Project Manager.
Does the publisher’s ad server have space for multiple 1x1s in a particular creative?
If Audience sends a wrapped/piggybacked tag, publisher should NOT implement the original agency 1x1 in addition to the wrapped tag. This would cause the agency’s tracking to be duplicated.
Publisher should always implement their cache-buster on Audience's tag in place of Audience's cache-buster placeholder. To do so, replace the placeholder that’s in the Proof tag with the cache-buster macro.
If this is not possible, then the Audience Project Manager should be advised.
APPENDIX A
About the Audience tag: Pixel Vendor Implementation Guide