One SDK now lets every app measurement vendor read the same signal

The revenue mechanism

On the open web, a browser lets outside verification companies inspect a page directly, so a publisher's viewability and fraud numbers can be checked by more than one vendor at once. Inside a mobile app or a connected-TV app, there is no equivalent open window: each verification company historically had to build its own proprietary code into an app, one integration per vendor, which the Open Measurement SDK page, last updated 4 November 2025 by IAB Tech Lab's own account, describes as forcing basic signals like "placement on screen, transparency of overlays, quartile measurement" to be "collected using different methodologies" depending on which vendor's code ran. The Open Measurement SDK replaces that patchwork with a single library an app developer embeds once, letting any compliant verification vendor read the same measurement signals through one interface, which is the mechanism that determines how in-app and CTV ad inventory gets independently verified at all.

What the documents show

The OM SDK page states it offers "three core capabilities": impression measurement confirming when and how much of an ad appeared on screen and for how long, verification that "facilitates third party verification of invalid traffic and brand requirements," and universal integration standardizing signals across mobile apps, web and connected TV. Technically, the page explains that apps integrating OM SDK "send measurement signals to an API, the Open Measurement Interface Definition (OMID)," which measurement providers then read via placed tags. The compliance program page, as retrieved on 16 September 2026, confirms IAB Tech Lab runs a separate OM SDK Compliance certification, verifying that a given app's or SDK's integration was implemented correctly, across HTML display, native display and video creative types.

The assumptions exposed

OM SDK standardizes how measurement signals are collected and delivered; it does not itself decide what counts as a valid impression or block invalid traffic, those judgments still belong to whichever verification vendor reads the signals. A publisher whose app is "OM SDK compliant" has confirmed the plumbing is implemented to specification, not that any particular verification vendor's fraud or viewability numbers are independently accredited; that is a separate claim requiring its own accreditation, such as MRC's. The standard also depends on the app developer choosing to integrate it in the first place, since nothing in an app store requires OM SDK support.

What to check before you rely on it

This is an editorial checklist. A publisher with an app should confirm OM SDK is actually integrated and current, not merely available from an ad SDK vendor as an optional feature.

• Is OM SDK integrated in your current app build, and for which creative types (display, native, video)?
• Is the integration itself certified compliant, and by which compliance program listing?
• Which verification vendor reads the OMID signals, and is that vendor's own accreditation current?

OM SDK answers a plumbing problem that had left in-app measurement fragmented for years; it is a precondition for trustworthy in-app verification, not a substitute for checking the accreditation of whichever vendor sits on top of it.