Simplified SDK API: Difference between revisions

From Engineering Client Portal

No edit summary
No edit summary
Line 3: Line 3:
__NOTOC__
__NOTOC__


{{Simplified_API_Overview}}


== Implementation Guides ==
== Implementation Guides ==

Revision as of 17:53, 20 October 2022

Engineering Portal / Digital / DCR & DTVR / Simplified SDK API


Implementation Guides

Type OS Implementation Guides for Simplified SDK
SDKIcon.png
Video
iOS
Digital Measurement iOS Simplified API
Android
Digital Measurement Android Simplified API
Browser
Digital Measurement Browser Simplified API

Simplified Implementation

Only 4 events with the Simplified SDK. Order of calls no longer important.

Key Description
playhead

It is used to pass content, ad or static metadata, the current playhead value, UTC timestamp or id3 payload, ott information to the SDK.

pause

This event should be used to in the following cases: application enters background, any application interruptions, content playback is paused. (Pause is detected by SDK automatically only if time gap between commands in more than 30 minutes.)

complete

It is called when session is completed or ends.

adStop

Should be called at the end of each ad. This event type is required to handle the case when advertisements could not be distinguished, as its assetId is the same.

Single object holds all the data

All the data provided in the older API in separate calls will be provided in one single call. Format of input object is the following:

{ 
 "event": <event identifier>,
 "type": <type of metadata>,
 "metadata":{ 
   "content": <content metadata object>,
   "ad": <ad metadata object>,
   "static": <static metadata object>
 },
 "playheadPosition":<playhead value | UTC>,
 "id3Data": <id3 payload>,
}


SimplifiedAPI vs StandardAPI New.jpg Click here to zoom in on image