The Open Measurement SDK (OMSDK) allows you to measure viewability for advertisers working with measurement vendors (see the supported vendors, below). Open Measurement allows you to include third-party viewability and measurement vendors, either within bid response fields, or within the creative itself. Google already provides viewability measurement based on Active View; Open Measurement gives you an additional IAB industry-standard option when it comes to measuring viewability by third-party standards on Google Ad Manager and Google AdMob impressions.
Currently, the OMSDK is only supported for mApp (in both Google Ad Manager and Google AdMob). App publishers will need to upgrade to a new SDK version to benefit from Open Measurement.
Supported transaction types
- Private deals, Programmatic guaranteed, Private auction, and Open auction
Supported measurement vendor domains
- Integral Ad Science
- Protected Media
Domains (from companies not already listed) that are part of the Open Measurement Working Group are also eligible. Contact your account manager with the domains in question if you work with a Working Group member and are seeing creative disapprovals.
- Video, Display (Banner/Interstitial), and Rewarded
- Native is currently not supported. Contact your account manager for more information.
RTB request - When is Open Measurement Interface Definition (OMID) supported?
- In Authorized Buyers Protocol, a new excluded attribute will be sent when the OMSDK is not supported: BidRequest.ad_slot.excluded_attribute:
CREATIVE_ATTRIBUTE_VALUE_OMSDK_N = 114;
- In OpenRTB, the standardized approach of the
apifield in Banner and Video objects are used. This is very similar to how MRAID and VPAID are indicated.
RTB request - Which vendors are allowed?
- Viewability measurement vendors that are allowed for each impression will be passed in the allowed_vendor_type field in the bid request for Authorized Buyers Proto and OpenRTB. Bid responses that include technologies that are certified but not in allowed_vendor_type will be filtered.
- There are 2 types of disapproval reasons (AWPCs) for the misuse of the OMSDK by third-party vendors:
- 721: Misuse by OMID SDK script
- Creatives containing Open Measurement (OMID) scripts should only interact with the public API as defined by omidsdk-v1.js, and will otherwise be disapproved.
- 752: OMID vendor not on approved list
- Creatives using Open Measurement (OMID) scripts are only allowed to use domains from the approved vendors noted above. If you experience this disapproval for a creative from a Working Group company, contact your account manager.
- 721: Misuse by OMID SDK script
For Banner ads
For Video ads
Sample VAST using OMID in the <AdVerifications> extension
<![CDATA[ https://my_3p_vendor.com/omid.js ]]>;
The Open Measurement SDK is a solution for mobile app inventory only. 3rd party viewability vendors on web are not supported. Not all publishers will support the OMSDK from the beginning, but more and more publishers are expected to adopt newer versions of the GMA SDK.
Native is currently not supported. Contact your account manager for more information.
Frequently asked questions
How is the Open Measurement SDK different from the existing viewability reporting in Query Tool and Viewability bid request signal in Authorized Buyers?
What is the difference between "viewability" and "invalid traffic"? How does OMID help with this?
Why is there an approved list of allowed OMID vendor domains?
In addition to the approved list, domains (from companies not already listed) that are part of the Open Measurement Working Group are also eligible. Contact your account manager with the domains in question if you work with a working group member and are seeing creative disapprovals.