This page covers data collection for the Content resumes variable. See Content resumes for the corresponding reporting metric.
The content resumes variable flags a session that resumes a previously interrupted playback. Set it on media.sessionStart so that the backend counts a Content resumes event for the session and excludes it from new-stream counts. For direct API and Edge API implementations, the client is responsible for detecting resumed sessions (for example, after a buffer, pause, or stall exceeding 30 minutes) and setting this flag accordingly.
a.media.resumeRecommended implementation types
Set hasResume to true inside xdm.mediaCollection.sessionDetails when calling sendEvent for the resumed session:
| code language-javascript |
|---|
|
Pass the resume flag as part of the media object’s optional config bundle on trackSessionStart. Use the MediaConstants.MediaObjectKey.RESUMED key.
| code language-swift |
|---|
|
Pass the resume flag as part of the media object’s optional config bundle on trackSessionStart. Use the MediaConstants.MediaObjectKey.RESUMED key.
| code language-kotlin |
|---|
|
Set hasResume to true inside xdm.mediaCollection.sessionDetails when calling createMediaSession for the resumed session:
| code language-brightscript |
|---|
|
Call the sessionStart endpoint with hasResume set to true inside xdm.mediaCollection.sessionDetails:
| code language-json |
|---|
|
Legacy implementation types (Analytics-only)
Set the RESUMED key on the media info object before calling trackSessionStart:
| code language-javascript |
|---|
|
Set MediaResumed on the media info object before calling trackSessionStart:
| code language-javascript |
|---|
|
Include media.resume in the params object of your sessionStart POST request:
| code language-json |
|---|
|
See the Media Collection API sessions reference for the full request structure.