This page covers data collection for the Chapter name variable. See Chapter name for the corresponding reporting dimension.
The chapter name variable is the human-readable title of a chapter (for example, "Pilot Episode - Opening"). Set it on every media.chapterStart event whose content is divided into chapters.
a.media.chapter.friendlyNamec_contextdata.a.media.chapter.friendlyNameRecommended implementation types
Set friendlyName inside xdm.mediaCollection.chapterDetails when calling sendEvent:
| code language-javascript |
|---|
|
Pass the chapter name as the first (name) argument to createChapterObject.
| code language-swift |
|---|
|
Pass the chapter name as the first (name) argument to createChapterObject.
| code language-kotlin |
|---|
|
Set friendlyName inside xdm.mediaCollection.chapterDetails when calling sendMediaEvent for media.chapterStart:
| code language-brightscript |
|---|
|
Call the chapterStart endpoint with friendlyName inside xdm.mediaCollection.chapterDetails:
| code language-json |
|---|
|
Legacy implementation types (Analytics-only)
Pass the chapter name as the first argument to ADB.Media.createChapterObject:
| code language-javascript |
|---|
|
Pass the chapter name as the first argument (name) to ADBMobile.media.createChapterObject:
| code language-javascript |
|---|
|
Pass the chapter name as the first argument (name) to adb_media_init_chapterinfo:
| code language-brightscript |
|---|
|
Include media.chapter.friendlyName in the params object of your chapterStart POST request:
| code language-json |
|---|
|
See the Media Collection API events reference for the full request structure.