2020-06-29 Release

Open Measurement SDK (OM SDK) integration with Pulse iOS SDK and deprecation of Segment identification document.

Open Measurement SDK integration with Pulse iOS SDK

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. See Open Measurement SDK (OM SDK) for more information.

We have integrated the OM SDK with the Pulse iOS SDK to make this communication possible when a third-party ad from Pulse is displayed in your native iOS 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.

Note: This integration applies only to Pulse iOS SDK and does not include Pulse tvOS SDK.

This means that you can now provide required measurement data to all measurement providers and advertisers by accessing multiple measurement provider 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.6.0 or later of the Pulse iOS SDK.
  • You must call one of the below methods to initialize the OM SDK integration in Pulse iOS 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:
      [INOmidAdSession createOmidAdSessionWithView:pulseVideoAd:contentUrl:friendlyObstructions:];
    • Create OMID ad session without friendly obstructions:
      [INOmidAdSession createOmidAdSessionWithView:pulseVideoAd:contentUrl:];

    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 three new events related to viewability calculations.

    When calling adStarted, report the player volume, with a range between 0 and 1 (default value is 1):

    adStarted:

    The native video player volume has changed:

    playerVolumeChanged:

    The native video player state has changed:

    playerStateChanged:
  • Third-party ads must be configured to include the measurement provider 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.

Deprecation of Segment identification document

From today, 29 June 2020, the Segment identification document, a CSV file you had to provide us with to set up audience targeting for your Pulse account, is deprecated and superseded by the Audience Management API. If you are still using the Segment identification document, you can now start migrating to the Audience Management API.

Our Customer Solutions team will work with you to determine a migration timeline, and an end of life date will be announced at a later point.

When initiating the Pulse Audience Management integration project, our Customer Solutions team configures the audience provider information, however you can manipulate the audience segmentations and corresponding audience segments using the Audience Management API.

The API enables you to:

For more information, contact your Account Manager.

Documentation releases

This release includes the following documentation updates: