IAS OMID for Web for VAST Providers Implementation

Overview

This document guides you through the steps to implement IAS Open Measurement Display (OMID) for Web for VAST providers.

Appending <AdVerifications> node to VAST

VAST versions 1.0 - 3.0

1) Include script in <Extensions> node as shown:

2) Don't include <VerificationParameters>

VAST versions 4.0 or Later

1. Include script directly as <AdVerifications>

2. Don’t include <VerificationParameters>

Additional Requirements

• vendor attribute in node should always be "ias".

• browserOptional attribute is always "false" for the web OMID script (VANS adapter), so IAS isn't loaded by mistake into DOMless environments where IAS isn't able to measure.

Verification Script URL

This is the URL in the CDATA in the <JavascriptResource> node.

Note: For QA/test tags, notice that "adsafeprotected.com" and "test-adsafeprotected.com" are different hostnames.

Note: After implementing the IAS OMID for web integration, give IAS a test server/test tags to add to IAS's regression testing.

Parameters

• All parameters to be passed to IAS for reporting should be passed to the OMID VANS adapter by appending it to the end of the adapter script as query parameters - including, but not limited to:

  • IDs like advEntityId/pubEntityId

  • Debug parameters for troubleshooting

  • Additional IDs

• If these IDs are not appended correctly, clients will not receive reporting.

• IAS recommends implementing this in as flexible a fashion as possible, especially given the need for CM macro support in FW.

• For test/QA tags, automatically append debug=true to the adapter script if it is not provided already.

• Implement some way for IAS to pass parameters to the adapter for testing - whether it's in the URL, or some cookie IAS can set.

Appendix

Sample VAST tags, FW

Example of the IAS OMID script being included correctly:

Sample VAST tags, CM

Example of the IAS OMID script being included correctly: