editor
725
edits
Changes
Jump to navigation
Jump to search
no edit summary
Description=The devices send events to the UNIAPI EventService to collect Playback events. They call to the addEventPlayback method to send this playback events.
This events are sent only in the Player so it's related to VoD and Live contents and related to the HeartBeat event. In case of VoD contents, two kinds of request are made to register events in the platform: AddEventPlayback (to register the analytics events ) and the events for the PlaybackHeartBeat control. In case of an OB has the PlaybackHeartBeat deactivated, and the device's play the Live content, the events for the Analytics won't be registered.
In case of an OB has the [[PlaybackHeartBeat]] deactivated, and the device plays the Live content, the events for the Analytics won't be registered, because the Live player use the contents sent to the PlaybackHeartBeat to register the Events about player.
In general, this method is used by the player used on "PC Client" and "Go Web". But it can be used by other devices only in the player component.
All events sent to the GVP is storage in the BI module and summarised by the BI team, who collect and analyse all data on the Mib tools.
This method can be used by logged or anonymous user.
|Parameters=
{{Api_Parameter|
ParamName=playbackEventType
|ParamType=String|ParamRequired=required
|ParamDescription=
}}
{{Api_Parameter|
ParamName=contentId
|ParamType=int|ParamRequired=required
|ParamDescription=
}}
{{Api_Parameter|
ParamName=contentType
|ParamType=int|ParamRequired=optional|ParamDescription=Used to set what kind of content the event occur. By default this parameter is set to [[MovieType]].Unknown.
}}
{{Api_Parameter|
ParamName=errorMessage
|ParamType=String|ParamRequired=optional|ParamDescription=A message to be storage in the event.
}}
