3rd Party Trackers

What are 3rd party trackers?  

 In the Eskimi platform, “3rd Party Tags” are any externally-provided code designed to monitor, record, or track the performance of Eskimi campaigns. 

 3rd Party Tags are typically HTML tags ( IMG pixels  or  Javascript tags ) that are implemented by Eskimi on a publisher’s page when your ad is displayed, seen, or clicked. These tags are used to transfer data to other platforms, outside of Eskimi’s proprietary dashboard. 

 

 What are the types of 3rd party trackers? 

 3rd party pixels (image): A tracking pixel is a tool used to track ad impressions. It consists of a piece of code inserted into the creative. This code causes a 1x1 transparent image to track with the ad. 

 How to validate that you have a 3rd party pixel (image):  

 

 

 Be 1x1 pixels (they come in a URL format) 

 

 

 Use a clickable pixel/image tag rather than code such as JavaScript tags 

 

 

 Only use macros including Cachebuster, IP, User Agent (UA), Timestamp, or Episode ID. 

 

 

 1x1 pixel examples: 

 https://ad.doubleclick.net/ddm/trackimp/N705418.1727343ESKIMI.COM/B28985587.353603375;dc_trk_aid=545020201

dc_trk_cid=182974786;ord=

[timestamp];dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};ltd=? 

 https://track.adform.net/adfserve/?bn=60266225;1x1inv=1;srctype=3;ord={cachebuster} 

 Practical validation: You can always Paste the URL into a browser to make sure it loads properly. The browser will load an all black page with a tiny dot of white in the center. If the browser loads something else you might be using a JavaScript tag, not an image pixel. 

 

 3rd Party JavasScript: Javascript tags that allow advertisers to capture more information rather than only impressions. JS trackers are the backbone of 3rd party companies like IAS, MOAT, DV etc.  

 How to validate that you have a 3rd party JavaScript:  

 

 The tag will be in a <script><script> 

 It will be a code rather than a clickable pixel/image  

 Allow various macros. Eskimi macros have to be implemented into the tag (ex.: {creative_id}, {site_id} etc.). Any 3rd party macros will not be supported and Eskimi system will not be able to fetch the data . (Eskimi macros can be found in campaign setup page, under click URL parameters). 

 

 JavaScript tag examples: 

 <script type="text/javascript" 

src="https://pixel.adsafeprotected.com/jload?anId=931059&advId={campaign_id}&campId={creative_title}

&pubId={site_title}&chanId={site_id}&placementId={creative_size}">

</script> 

 <noscript class="MOAT-heinekenkheskimidisplay418936584220?moatClientLevel1={campaign_id}&amp;moatClientLevel2=

{site_id}&amp;moatClientLevel3={creative_title}&amp;moatClientLevel4={creative_size}">

</noscript>

<script src="https://z.moatads.com/heinekenkheskimidisplay418936584220/moatad.js#moatClientLevel1={campaign_id}&moatClientLevel2=

{site_id}&moatClientLevel3={creative_title}&moatClientLevel4={creative_size}" type="text/javascript">

</script> 

 https://z.moatads.com/heinekenkheskimidisplay418936584220/moatad.js#moatClientLevel1={campaign_id}&moatClientLevel2=

{site_id}&moatClientLevel3={creative_title}&moatClientLevel4={creative_size} 

 Practical validation: You can always Paste the URL from the Javascript into a browser to make sure it loads properly. The browser should fetch more information from the tag. If the browser doesn't bring any information, then you might be not using a JavaScript tag. 

 

 Keep in mind: 

 

 The tag should be implemented exactly as you got it from the 3rd party vendor. 

 There are supply limitations as there are publishers that will not support JS tags on their pages.

 

 

 Note: 

 Pixels could be implemented as pixels or as HTML/JavaScript tags . 

 In the provided example: 

 <img src="https://gdeua.hit.gemius.pl/_{CACHEBUSTER}/redot.gif?

id=nAE7_Yw7MDfkVxcFmlFmC2ZWDfXZJOdExNe22B4YXQz.U7/fastid=exkyeeteovzqevebeouudwxytsob/stparam=odcppjdoqy/nc=0/gdpr=0/gdpr_consent="

width="1" height="1" style="display: none"> 

 This code snippet is HTML/JavaScript code. However, it contains an HTML img tag, indicating that the URL within it serves as an image. 

 There are two options for implementation: 

 

 

 Extract the URL from the tag ( https://gdeua.hit.gemius.pl/_{CACHEBUSTER}/redot.gif?id=nAE7_Yw7MDfkVxcFmlFmC2ZWDfXZJOdExNe22B4YXQz.U7/fastid=exkyeeteovzqevebeouudwxytsob/stparam=odcppjdoqy/nc=0/gdpr=0/gdpr_consent= ) and set it up as a Pixel tracker. Ensure that your tracker is secure (HTTPS). 

 

 

 Take the entire code snippet ( <img src="https://gdeua.hit.gemius.pl/_{CACHEBUSTER}/redot.gif?id=nAE7_Yw7MDfkVxcFmlFmC2ZWDfXZJOdExNe22B4YXQz.U7/fastid=exkyeeteovzqevebeouudwxytsob/stparam=odcppjdoqy/nc=0/gdpr=0/gdpr_consent=" width="1" height="1" style="display: none"> ) and set it up as an HTML/JavaScript code tracker. 

 

 

 Important : 

 

 HTTPS impression trackers must always be secure SSL (HTTPS). For click URLs, it is possible to use a non-secure tracker. 

 The conventional approach for handling pixel tags of this type, which are image files, is to add them as pixel tracking tags  rather than HTML/JS tags. 

 

 

 How to implement & validate 3rd party trackers?  

 3rd party pixels (image): There are two ways how image pixels can be created: a) during campaign setup in the creative section; b) at the campaign approval level under Custom impression tracking .  

 1. Choose Pixel in the dropdown section under custom impression tracking . 

 2. Paste only the URL of the tag 1x1 pixel .  

 3. Save your campaign.  

 4. Go to the preview page of the campaign. 

 5. Click the right button of your mouse, navigate yourself to  Inspect section . 

 6. Search for your tag in the Network section. Paste the domain in the search bar.  

 The flow works the same for display and video advertising. 

 3rd party JavaScript:  There are two ways how image pixels can be created: a) during campaign setup in the creative section; b) at the campaign approval level under Custom impression tracking .  

 1. Choose JavaScript in the dropdown section under custom impression tracking . 2. JavaScript must be pasted in a <script><script>. If the prodided JavaScript isn't in a <script><script>, contact 3rd party tag owners to understand if the tag was properly provided and how it should be implemented.  

 3. Save your campaign.  

 2. Go to the preview page of the campaign. 

 3. Click the right button of your mouse, navigate yourself to  Inspect section . 

 4. Search for your tag in the Network section . Paste the domain in the search bar.  

 The flow works the same for display and video advertising. 

 The preview page can be shared with the 3rd party platform for both 1x1 pixels and JavaScript tags. So they would be able to verify that the tags are firing properly. 

 

 Macros 

 Most of the time both pixel and HTML/JS tags come with macros that allows Eskimi to send relevant parameters to another server. It is essential to make sure that all the macros in the tag are supported by Eskimi. Macros have to be changed to a corresponding Eskimi macros. For example the client shared DCM trackers which contains unsupported macros such as ${GDPR} and ${GDPR_CONSENT_755}: 

 <SCRIPT language='JavaScript1.1'

SRC="https://ad.doubleclick.net/ddm/trackimpj/N1106506.139142MADHOUSE/B29321130.358299170;dc_trk_aid=549422973;dc_trk_cid=186346309;ord=

{cachebuster};dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=${GDPR};gdpr_consent=${GDPR_CONSENT_755};ltd=?">

</SCRIPT> 

 By leaving these macros unchanged we might face discrepancies between two servers as the GDPR consent will not be sent to the 3rd party provider. Some 3rd party providers will not be able to render their tracker if the consent is not their. To avoid discrepancies these macros must be changed into corresponding Eskimi macros. See example below: 

 <SCRIPT language='JavaScript1.1'

SRC="https://ad.doubleclick.net/ddm/trackimpj/N1106506.139142MADHOUSE/B29321130.358299170;dc_trk_aid=549422973;dc_trk_cid=186346309;ord=

{cachebuster};dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr={gdpr};gdpr_consent={gdpr_consent};ltd=?">

</SCRIPT> 

 

 

 Why to use 3rd party trackers? 

 Ad Verification  Send live campaign data to your 3rd party tracking platform. Validate brand safety, numbers of impressions, viewable impressions and clicks.  

 Attribution Observe the whole user journey, not just the last click. Measure the effectiveness of Eskimi on users that have seen your ads (and have not necessarily clicked them).  

 Re-engagement Identify users that have engaged with your Eskimi ads and remarket them on other platforms.  

 

 

 Limitations 

 1. Majority of image pixels allow to track impressions only . They don't provide comprehensive information about brand safety, IVT, viewability like JavaScript tags. We recommend to check with 3rd party providers about limitations and capabilities of their tracking. 

 2. VAST video support both image and JavaScript trackers . However, the same image pixel limitations will be applied. Also, to enable JavaScript tracking for VAST video, the VAST URI will have to be wrapped into a JavaScript tag by the 3rd party provider (MOAT, IAS). 

 3. Some of the device browsers may fail to properly fire 3rd party trackers. One of them is Android WebView (Dalvik) . Adman trackers don't track this browser, while trackers like IAS may result in 3X higher discrepancy in comparison with the regular Android WebView. To reduce the possible discrepancy we recommend removing Android WebView (Dalvik) when 3rd party trackers are being used.