Open Measurement SDK

The Open Measurement SDK (OMSDK) allows you to measure viewability for advertisers working with measurement vendors (see supported vendors). 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.

Supported platforms

Currently, Open Measurement is supported for app ads (in both Google Ad Manager and Google AdMob) in-stream web, and non-instream video. App publishers will need to upgrade to a new SDK version to benefit from Open Measurement. 

Read the Open Measurement developer documentation for Android, iOS, and HTML5 video.

Expand all  Collapse all

Supported transaction types

• Private deals, Programmatic Guaranteed, Private auction, and Open Auction

Supported formats

• App: Video, Display (Banner/Interstitial), Rewarded, and Native
• Web: In-stream web and non-instream video

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 api field in Banner and Video objects is used. This is very similar to how MRAID and VPAID are indicated.
• For OpenRTB Native (2.5+), we include the standard EventTrackers request which indicates support for JavaScript:

  request_native {
     eventtrackers {
        event: IMPRESSION  //JavaScript executes on impression event
        methods: JS        //OpenRTB can specify support for “JS” and/or “IMG”
     }
  }

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.

OMID supported versions

Learn about supported OMID versions in the IMA SDK.

<Extensions>
   <Extension type="AdVerifications">;
      <AdVerifications>;
         <Verification vendor="my_3p_vendor.com-omid">;
             <JavaScriptResource apiFramework="omid"
                browserOptional="true">;
                  <![CDATA[ https://my_3p_vendor.com/omid.js ]]>;
             </JavaScriptResource>;
             <TrackingEvents>;
                <Tracking event="verificationNotExecuted">;
                   <![CDATA[https://my_3p_vendor.com/visit.jpg?ctx=818052;]]>;
                </Tracking>;
             </TrackingEvents>;
             <VerificationParameters>;
                  <![CDATA[;
                      //customParamsGoHere...;
                  ]]>;
            </VerificationParameters>;
         </Verification>;
      </AdVerifications>;
   </Extension>;
</Extensions>