JavaScript Impression + Click Tracking Tags

Medialets Support -

Description: The Servo JavaScript Impression + Click Tracking Tag enables tracking for advertisements that are not served through Servo. Each tracking tag is comprised of an anchor tag (<a href=) element to track clicks and an image source (<img src=) to track impressions. It is common practice for a 1st party ad server to require that each component is tracked separately. This is acceptable, but the cachebuster value (RANDOM) must match across impression and click.

Campaign Reports include: Impressions, Clicks

Attribution Reporting Includes: View through, Click through

Inventory Partner Implementation Notes:

  • When copying and pasting Servo ad tags provided in an Excel document, please copy and paste the tag from within the cell. Copying and pasting the whole cell will result in double quotation marks, which will cause errors.
  • Each tag should be implemented in its entirety, from <div> to </div>. Only scheduling portions of the Servo ad tag will result in potential loss of functionality and reporting discrepancies.

  • JS tags will be generated as secure-only or as environment aware, where they will serve as secure when implemented into secure environments. Protocols within the tag should not be adjusted.

  • The “Click URL” should be copied in its entirety and implemented as the click through URL in your 1st party ad server.

EXAMPLE: JAVASCRIPT IMPRESSION + CLICK TRACKING TAG

 
impunique: All RANDOM instances must be replaced with your cachebuster macro. For Servo to properly track impressions and clicks, the value of RANDOM must be the same across impression and click. Failure to use matching values across each component of the tag will result in reporting discrepancies. A truly unique string is strongly preferred. (Timestamp based values are not supported.) If this value will not match, a separate impression and click tracker must be issued.
 
ex & site fields: These two fields are optional. This is where you can add your Inventory Partner exchange tracking macro and/or your Inventory Partner site tracking macro.
 
osdevid & osoptout fields: These two fields are where you add your Device ID (IDFA/AAID/GAID) and OptOut macros. If your device ID macro will not populate a device ID when a user opts out of being tracked, your opt out macro isn't necessary.
 
pubimpid: This is where you add your Inventory Partner impression ID macro.
 
imppx: This is where you add your Inventory Partner impression pixel macro.

 

*Do not overwrite double quotes of the editable fields

Have more questions? Submit a request

Comments

Powered by Zendesk