This page contains information for MoPub SDK v.5.14.0 and higher. OM SDK is currently in Open Beta, and only supports measurement on:
- Banner HTML/MRAID
- MREC HTML/MRAID
- Fullscreen HTML/MRAID/VAST
This page will be updated when OM SDK is GA and supports all formats.
MoPub SDK v.5.14 and higher have integrated IAB tech lab certified technology, the Open Measurement (OM) SDK. The OM SDK enables publishers to support demand partners across a variety of viewability partners in one SDK, including IAS, MOAT, DV, and many others. MoPub is also IAB Tech Lab Standards compliant; refer to IAB documentation for details.. To learn more about transacting on inventory where OM SDK is integrated, refer to the MoPub OpenRTB spec for OpenRTB 2.3 or OpenRTB 2.5.
Supported Ad Formats, Tags, Regions, and Apps
Ad formats: MoPub’s OM SDK integration supports all formats for DSPs. Please note that each third-party vendor has their own guidelines for supporting formats, and we recommend contacting your third-party partner account representative for more information.
Tags: There are no known issues with any third-party vendor tags, and all should be supported, including wrapper tags. However, we recommend contacting your viewability partner account representative for more information on how to set up your ad tags. Please note that we do not support VPAID tags; more information below.
Regions: All regions are supported for Open Measurement Viewability. Contact your third-party partners for more information.
Apps: All apps on MoPub SDK v.5.14 and higher are automatically integrated and opted in to OM SDK. You can review which apps are on compatible MoPub SDK versions in MoPub Analytics.
Video measurement is supported via VAST, not VPAID. On desktop, third-party viewability partners typically include VPAID in buyer VAST tags in order to measure viewability. But for in-app, VPAID support is less common across multiple supply sources; therefore, our partners have developed solutions to measure viewability through VAST.
VAST video measurement in-app requires buyers to add either an
<AdVerifications> node to their VAST tag.
For each third-party viewability vendor, DSPs should work directly with their account representative on the specific way each vendor recommends integrating the VAST
<AdVerifications> node. For most verification vendors, the following steps outline how to implement the verification nodes:
For VAST versions pre-4.1, DSPs must include an extension node below the VAST XML, with the
<AdVerification>node nested inside, as shown:
For VAST 4.1, DSPs must include the
<AdVerifications.node directly below the VAST XML, as shown:
To help your viewability partner communicate with the MoPub SDK properly, you can include additional values in your bid response. For both OpenRTB versions 2.3 and 2.5, you can include the OMID-1 API (value = ‘7’) in the API array of your bid response (bidresponse.bid.ext.apis). Refer to the MoPub OpenRTB 2.5 spec or 2.3 spec for details.
Depending on how you transact, you can access reporting for your spend in MoPub Analytics Viewability Vendors Response dimension, or through third-party partner reporting.
Open Measurement License
We have partnered with the IAB to provide Viewability measurement via the Open Measurement SDK as of MoPub SDK v.5.14.0. To view the full license, visit https://www.mopub.com/en/omlv1.
How can we make this article better for you?
Last updated February 10, 2021
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2021 MoPub (a division of Twitter, Inc.)