Open Measurement SDK

Open Measurement SDK
Name	Open Measurement SDK
Developer	IAB Tech Lab
Initial release	2018
Programming language	Java, Objective-C, C++
Platform	Android, iOS, Web
License	Open-source

Open Measurement SDK

The Open Measurement SDK provides a standardized interface for measuring viewability, verification, and attribution in digital advertising across mobile apps and web environments. It was developed to enable interoperability between measurement vendors, ad platforms, and publishers, aligning with industry initiatives and technical specifications to deliver consistent metrics. The SDK operates as a mediation layer that harmonizes signals for third-party verification while minimizing fragmentation among IAB Tech Lab, Google, Facebook, Amazon (company), and other ecosystem participants.

Overview

The Open Measurement SDK emerged from collaborative efforts among IAB Tech Lab, verification vendors, sell-side platforms, and buy-side platforms to address inconsistent measurement practices that affected campaigns on Android, iOS, and web browsers like Google Chrome and Safari (web browser). It standardizes APIs for measurement partners such as Nielsen ( company), comScore, Moat, and Integral Ad Science to collect viewability and verification signals without bespoke integrations per publisher or ad network. The initiative aligns with reporting and technical guidance referenced by institutions like Interactive Advertising Bureau stakeholders and builds upon prior work in ad measurement standards promoted at events such as Advertising Week.

Architecture and Components

The SDK architecture separates responsibilities among host apps, measurement partners, and ad renderers. Core components include a host API implemented in languages such as Java (programming language), Objective-C, and C++ to support platforms like Android, iOS, and web runtime environments in Google Chrome and Mozilla Firefox. A central arbitration mechanism grants measurement access to registered verification vendors via standardized session objects and impression lifecycle callbacks. Key modules mirror concepts used by players including AdMob, MoPub, AppLovin, and The Trade Desk: session management, visibility tracking, event logging, and secure communication channels. The design references cross-industry specifications promulgated by IAB Tech Lab working groups and integrates with ad formats standardized by entities such as MRAID and initiatives discussed at conferences like DMEXCO.

Integration and Usage

Developers integrate the SDK into mobile apps, SDK wrappers, and web pages by adding the provided libraries and exposing ad view references or DOM nodes to measurement sessions. Typical flows resemble integration practices used by Google Ad Manager, Meta Audience Network, and ad SDK aggregators like ironSource: initialize the SDK, register verification vendors, create impression sessions, and notify lifecycle events (impression start, viewability changes, impression end). The SDK supports multiple measurement vendors concurrently, aligning with publisher configurations from companies such as The New York Times digital advertising teams, programmatic platforms like Magnite, and supply-side platforms including PubMatic. Tooling and debugging practices parallel those in mobile development ecosystems like Android Studio and Xcode.

Privacy, Security, and Compliance

Privacy and security are addressed by minimizing data exposure, defining allowed signals, and enforcing permissions consistent with regulations and industry codes such as General Data Protection Regulation and California Consumer Privacy Act. The SDK can be configured to limit personally identifiable information and to honor user consent frameworks like the IAB Europe Transparency and Consent Framework. Secure transport of measurement payloads typically uses TLS as recommended by standards adopted by IAB Tech Lab and security guidance from organizations like OWASP. Vendors often incorporate techniques similar to those employed by App Tracking Transparency and mobile platform privacy controls on iOS to respect user choices and platform policies set by Apple Inc. and Google LLC.

Industry Adoption and Implementations

Major ad tech companies, verification vendors, and publishers implemented the SDK to standardize viewability and fraud detection. Measurement vendors such as Integral Ad Science, DoubleVerify (formerly AdSafe Media), Nielsen (company), and comScore adopted the APIs to provide cross-platform reporting. Programmatic platforms including The Trade Desk, Index Exchange, and OpenX integrated support to enable buyers to receive standardized verification signals. Publisher technology stacks at companies like Condenast and Vox Media used the SDK to simplify vendor management. Mobile monetization and mediation platforms—AdMob, MoPub (before acquisition), ironSource, and AppLovin—exposed ad view context to measurement sessions to comply with advertiser and platform demands.

Limitations and Criticisms

Critics note that while the SDK reduces fragmentation, it does not fully eliminate variance in measurement methodologies among verification vendors like Integral Ad Science and DoubleVerify, because signal interpretation and reporting thresholds can differ. Limitations include potential performance overhead on resource-constrained devices, challenges with cross-origin iframe contexts prevalent in web ecosystems like those handled by Google Ad Manager, and incomplete coverage for emerging formats such as interactive AR/VR ads promoted at CES. Privacy advocates point to residual signal leakage and reliance on vendor-side processing, prompting calls for stricter controls from bodies like IAB Tech Lab and regulators such as European Commission. Adoption disparities remain across smaller publishers and bespoke SDKs used by niche apps distributed via stores like Google Play and Apple App Store.

Category:Advertising technology