2020-02-18 Release

Open Measurement SDK (OM SDK) integration with Pulse Android SDK.

Open Measurement SDK integration with Pulse Android SDK

Previously, you had to integrate multiple measurement providers' code with your app to give them access to the required ad verification and viewability measurements. Interactive Advertising Bureau (IAB) has designed the Open Measurement standard to facilitate the measurement of mobile in-app ads by third-party viewability and measurement providers without requiring their own SDK. The IAB Open Measurement SDK (OM SDK) consists of two components:
  • Native libraries for mobile (iOS and Android): The native libraries collect various signals regarding ad impressions and performance using direct communication with the mobile device’s native operating system and media players, and publish these signals using the Open Measurement Interface Definition (OMID) JavaScript API.
  • OMID JavaScript API: The OMID API signals the events to measurement providers using their JavaScript resources.

We have integrated the OM SDK with the Pulse Android SDK to make this communication possible when a third-party ad from Pulse is displayed in your native Android application. Collection and surfacing of impressions and viewability information is supported for normal and sponsor standard third-party ads (pre-rolls, mid-rolls, and post-rolls), which are VAST 2.0, 3.0, 4.0, and 4.1 compliant.

This means that you can now provide required measurement data to all measurement providers and advertisers by accessing multiple measurement providers' SDKs collapsed into a single integration, simplifying maintenance without sacrificing functionality. Allowing such transparency can bring more demand for your inventory.

To benefit from the OM SDK, keep the following in mind:
  • You must upgrade to version 2.5.20.2.0 or later of the Pulse Android SDK.
  • You must call one of the below methods to initialize the OM SDK integration in Pulse Android SDK. The corresponding method should be called for each ad just before playing ad content otherwise ad session events will not be recorded.
    • Create OMID ad session with friendly obstructions:
      OmidAdSession.createOmidAdSession(pulseVideoAd, context, adView, friendlyObstructions);
    • Create OMID ad session without friendly obstructions:
      OmidAdSession.createOmidAdSession(pulseVideoAd, context, adView);

    Additional methods are available to update the ad view and friendly obstructions during ad playback, see documentation for more details.

  • You must notify us of two new events related to viewability calculations.

    The native video player volume has changed:

    volumeChanged(videoPlayerVolume);

    The native video player state has changed:

    playerStateChanged(playerState);
  • Third-party ads must be configured to include the measurement providers' JavaScript resources in the <AdVerifications> element if using VAST 4.1, otherwise <Extension type="AdVerifications"> should be used in the Extensions element for earlier VAST versions.
  • The collection, processing, analysis, and reporting of information surfaced by the OM SDK is the responsibility of each measurement provider and requires them to collect additional information with their respective JavaScript resource that is served with the ad creative. Advertisers/agencies should run tests with each measurement provider to ensure that the provided verification scripts run as expected.

Documentation releases

This release includes the following documentation updates: