Stay organized with collections
Save and categorize content based on your preferences.
The IMA SDK for HTML5 includes the
Open Measurement (OM) SDK,
an industry standard developed by the
Interactive Advertising Bureau (IAB) to enable third-party
viewability and verification measurement. When using the IMA SDK for HTML5, the
included OM SDK automatically parses the <AdVerifications> tag within VAST ad
tags and sends viewability data to the specified measurement vendors using the
OMID API. You can optionally set access mode rules for each request to control
what content the verification script can access.
The IMA SDK supports OM SDK v1.4.
Prerequisites
If using VAST 4.1 or higher, ads must be configured to supply verification
using <AdVerifications>. If using previous VAST versions, ads must use
<Extension type="AdVerifications">.
If your ads are trafficked through Ad Manager, configure a viewability
provider for your Ad Manager network and assign that viewability provider to
your line item. For more information, see
Configure a viewability provider for your Ad Manager network.
Access modes
The OM SDK supports running verification scripts in four different access modes
which controls how much the verification script can access:
FULL: The verification script has direct access to the creative and the
publisher page.
CREATIVE: The verification script and creative are sandboxed from the
publisher page. However, the script has direct access to the creative.
LIMITED: The verification script is sandboxed and cannot access the creative
or publisher page, and cannot directly confirm what publisher domain it is on.
Some viewability providers might not support all access modes. Contact your
viewability providers to verify which modes are supported. Previously, IMA
supported a DOMAIN access mode, which now defaults to LIMITED mode.
Set the access mode rules for a request
Access mode rules must be set at the
AdsRequest
level. To set different access modes for different verification script
providers, pass a dictionary that maps each
OmidVerificationVendor
to one of the access modes listed above. The OmidVerificationVendor.OTHER
field is used to set the default access mode for all vendors not explicitly
included in the dictionary. If no access mode rules are specified, verification
scripts run in LIMITED access mode for vendors.
See the following example which sets GOOGLE to
google.ima.OmidAccessMode.FULL. All other providers, including those
listed in
OmidVerificationVendor,
default to how OmidVerificationVendor.OTHER is set.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThe IMA SDK for HTML5 utilizes the Open Measurement (OM) SDK for third-party viewability and verification measurement, automatically sending data to specified vendors.\u003c/p\u003e\n"],["\u003cp\u003eAds must be configured to supply verification using \u003ccode\u003e<AdVerifications>\u003c/code\u003e (VAST 4.1+) or \u003ccode\u003e<Extension type="AdVerifications">\u003c/code\u003e (previous VAST versions).\u003c/p\u003e\n"],["\u003cp\u003eFour access modes (FULL, CREATIVE, DOMAIN, LIMITED) control verification script access to the creative and publisher page, impacting the level of data access.\u003c/p\u003e\n"],["\u003cp\u003eAccess mode rules are set at the \u003ccode\u003eAdsRequest\u003c/code\u003e level, allowing customized access for different verification vendors, with \u003ccode\u003eLIMITED\u003c/code\u003e as the default.\u003c/p\u003e\n"],["\u003cp\u003eImplementing \u003ccode\u003eCREATIVE\u003c/code\u003e access mode requires sandboxing the video player in a secure iframe and setting the \u003ccode\u003eOmidAccessMode\u003c/code\u003e to \u003ccode\u003eFULL\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Enable Open Measurement\n\nThe IMA SDK for HTML5 includes the\n[Open Measurement (OM) SDK](//iabtechlab.com/standards/open-measurement-sdk/),\nan industry standard developed by the\n[Interactive Advertising Bureau (IAB)](//www.iab.com/) to enable third-party\nviewability and verification measurement. When using the IMA SDK for HTML5, the\nincluded OM SDK automatically parses the `\u003cAdVerifications\u003e` tag within VAST ad\ntags and sends viewability data to the specified measurement vendors using the\nOMID API. You can optionally set access mode rules for each request to control\nwhat content the verification script can access.\n\nThe IMA SDK supports OM SDK v1.4.\n\nPrerequisites\n-------------\n\n- If using VAST 4.1 or higher, ads must be configured to supply verification\n using `\u003cAdVerifications\u003e`. If using previous VAST versions, ads must use\n `\u003cExtension type=\"AdVerifications\"\u003e`.\n\n- If your ads are trafficked through Ad Manager, configure a viewability\n provider for your Ad Manager network and assign that viewability provider to\n your line item. For more information, see\n [Configure a viewability provider for your Ad Manager network](//support.google.com/admanager/answer/9025968#configure-a-viewability-provider).\n\nAccess modes\n------------\n\nThe OM SDK supports running verification scripts in four different access modes\nwhich controls how much the verification script can access:\n\n- `FULL`: The verification script has direct access to the creative and the\n publisher page.\n\n- `CREATIVE`: The verification script and creative are sandboxed from the\n publisher page. However, the script has direct access to the creative.\n\n- `LIMITED`: The verification script is sandboxed and cannot access the creative\n or publisher page, and cannot directly confirm what publisher domain it is on.\n\nSome viewability providers might not support all access modes. Contact your\nviewability providers to verify which modes are supported. Previously, IMA\nsupported a `DOMAIN` access mode, which now defaults to `LIMITED` mode.\n\nSet the access mode rules for a request\n---------------------------------------\n\nAccess mode rules must be set at the [`AdsRequest`](/interactive-media-ads/docs/sdks/html5/client-side/reference/js/google.ima.AdsRequest#omidAccessModeRules) level. To set different access modes for different verification script providers, pass a dictionary that maps each [`OmidVerificationVendor`](/interactive-media-ads/docs/sdks/html5/client-side/reference/js/google.ima#.OmidVerificationVendor) to one of the access modes listed above. The `OmidVerificationVendor.OTHER` field is used to set the default access mode for all vendors not explicitly included in the dictionary. If no access mode rules are specified, verification scripts run in `LIMITED` access mode for vendors.\n\n\u003cbr /\u003e\n\nSee the following example which sets `GOOGLE` to\n`google.ima.OmidAccessMode.FULL`. All other providers, including those\nlisted in\n[`OmidVerificationVendor`](/interactive-media-ads/docs/sdks/html5/client-side/reference/js/google.ima#.OmidVerificationVendor),\ndefault to how `OmidVerificationVendor.OTHER` is set. \n\n request.omidAccessModeRules = {};\n request.omidAccessModeRules[google.ima.OmidVerificationVendor.GOOGLE]\n = google.ima.OmidAccessMode.FULL;\n request.omidAccessModeRules[google.ima.OmidVerificationVendor.OTHER]\n = google.ima.OmidAccessMode.LIMITED;\n\n\nTo implement `CREATIVE` access mode, you must follow both of the following\nsteps:\n\n1. Sandbox your video player in a secure iframe, isolated from the rest of your\n site.\n\n2. Set the `OmidAccessMode` for your viewability partner to `FULL`."]]