Clarification of OMSDK Integration with SIVIC

[ravivooda]

Should we jot down how the SIVIC ad (as a whole) should be handled by the publisher for OMSDK for verification purposes.

Suggestion:

1. Register the player as the ad View.
2. Register the SIVIC Interactive creative part (iFrame) as a friendly obstruction.

Questions:

1. Would there be any other views created in the ad's life span?

[ryanthompson591]

We think we need an interoperability section at the end of the doc that will specify that the publisher should have the OMSDK register the SIVIC iFrame as a friendly obstruction. Otherwise viewability metrics will be incorrect.

I will try and write that section.

[ryanthompson591]

I talked with our resident OMSDK expert and rather than registering it as a friendly obstruction we think the right API to use is setSlotElement(sivicIframe). He will talk with the OMSDK group.

For mobile apps this will probably technically require that the OMSDK be in the same web view as the SIVIC iframe.

The flow will look like this:

iOS/Android:

• The publisher/SDK starts an OMID ad session in iOS/Android code, calling registerAdView on the native view holding the native player and the webview.
• The publisher/SDK points the OMID ad session to the webview as part of the ad session context (iOS, Android).
• The publisher/SDK loads the SIVIC creative in an iframe.
• The publisher/SDK loads the OMSDK Service Script into the webview such that it can access the iframe element.
• The publisher/SDK uses the OMSDK Session Client in JS to call setSlotElement on the iframe element. (To be confirmed that setSlotElement will be used).

Web (still in development)

• The publisher/SDK starts OMID ad session in JS, calling registerAdView on the element containing the iframe and the video player.
• The publisher/SDK loads the SIVIC creative in an iframe.
• The publisher/SDK loads the OMSDK Service Script onto the page such that can access the SIVIC iframe.
• The publisher/SDK uses the OMSDK Session Client in JS to call setSlotElement on the iframe element. (To be confirmed that setSlotElement will be used).
• The publisher/SDK uses the OMSDK Session Client in JS to call setVideoElement on the underlying video element.

I think that this can just be simplified to say: If the player integrates with OMID, when a SIVIC ad plays it should call setSlotElement(sivic_iframe) to let OMID know about the SIVIC ad for viewability.

[ryanthompson591]

We discussed this in the meeting and can close this for now. OMID will need to figure this out.