IAS JS Tag Implementation Instructions

Step 1 . IAS Append vs Write issue

All IAS JS tags need to be generated as .append and not .write to track campaigns correctly. If the tag is in the incorrect format, it will negatively impact campaigns created in both the NAG and trafficked through a DSP. 

IAS is working a long-term solution to ensure STR tags are always built with append.

You are able to QA your tags when you receive them by putting the JS tag in a browser and searching for ‘forceAppend’. If you see forceAppend : “false”, then the tags WILL NOT track correctly. You’ll need all IAS JS tags we run to be forceAppend : “true”.

Step 2. Implementing the JS pixel 

A) Sharethrough can support IAS viewability JS tags directly on the platforms of AppNexus, Oath, Adobe, The Trade Desk, Mediamath and DV360. Make sure to add your pixel in the JS field. 

For DataXu and Basis by Centro you must use the NAG JS tracker field, do not implement your JS tag in the DSP  

 ------------------

For DataXu and Basis by Centro:

Enter the DoubleVerify tag within the Third Party JS field on the appropriate Native Ad Generator.

-----------------------------------------------------------------------------------------------------------

For other DSPs that are not supporting JS for Native, please use our tag converter. 

Before tags can be implemented, they must be modified using the STX Tag Converter.

To modify your tags, go to stx.sharethrough.com/viewability_tag_converter.

NOTE: If you are using an ad blocker, you must turn it off to use the Tag Converter.

 1. Select DoubleVerify as the viewability vendor.

2. Select the DSP where you will use this tag.

3. Paste the DoubleVerify javascript tag exactly as you received it from DoubleVerify. Ensure there are no extra punctuation, spaces, or incorrectly capitalized letters.

4. Click Get Tracker URL to generate the tracking tag.

5. Follow the directions for implementing the tag for each DSP. (Instructions vary depending on DSP selected.)