Sent with the sessions
call. When the response returns, you extract the Session ID from the Location header and use it for subsequent event calls to the Collection server.
Sent when the player changes state to “playing” from another state (i.e., the on('Playing')
callback is triggered by the player). Other states from which the player moves to “playing” include “buffering”, the user resumed from “paused”, the player recovered from an error, autoplay, and so on.
Ping events should not include the params
map in the request body.
Sent when the bitrage changes.
Sent when buffering starts. There is no bufferResume
event type. A bufferResume
is inferred when you send a play
event after bufferStart
.
Sent when the user presses Pause. There is no resume
event type. A resume
is inferred when you send a play
event after a pauseStart
.
Signals the start of an ad break
Signals the start of an ad
Signals the completion of an ad break
Signals an ad skip
Signals the completion of an ad break
Signals the start of a chapter segment
Signals a chapter skip
Signals the completion of a chapter
Signals an error occurred.
This is used to notify the Media Analytics backend to immediately close the session when the user has abandoned their viewing of the content and they are unlikely to return.
If a sessionEnd
is not sent, an abandoned session will time-out normally (either after no events are received for 10 minutes, or when no playhead movement occurs for 30 minutes). Additionally, all subsequent Media Calls made with that Session ID will be dropped.
Sent when the end of the main content is reached
You should refer to the JSON validation schemas for each event type, to verify correct event parameter types and requirements.
Signals the start of player state tracking.
For more information, see Implementation and reporting.
Signals the end of player state tracking.
For more information, see Implementation and reporting.