This page covers data collection for the Content name variable. See Content name for the corresponding reporting dimension.
The content name variable is the human-readable title of the content (for example, "Blinding Light"). It is optional but strongly recommended. In the XDM schema it maps to friendlyName (not name; name holds the Content ID).
a.media.friendlyNamec_contextdata.a.media.friendlyNameRecommended implementation types
Set friendlyName inside xdm.mediaCollection.sessionDetails when calling sendEvent:
| code language-javascript |
|---|
|
Pass the human-readable name as the first (name) argument to createMediaObject. The second argument is the Content ID.
| code language-swift |
|---|
|
Pass the human-readable name as the first (name) argument to createMediaObject. The second argument is the Content ID.
| code language-kotlin |
|---|
|
Set friendlyName inside xdm.mediaCollection.sessionDetails when calling createMediaSession:
| code language-brightscript |
|---|
|
Call the sessionStart endpoint with friendlyName inside xdm.mediaCollection.sessionDetails:
| code language-json |
|---|
|
Legacy implementation types (Analytics-only)
Pass the human-readable name as the first argument to ADB.Media.createMediaObject:
| code language-javascript |
|---|
|
Pass the human-readable name as the first argument to ADBMobile.media.createMediaObject:
| code language-javascript |
|---|
|
Include media.name in the params object of your sessionStart POST request:
| code language-json |
|---|
|
See the Media Collection API sessions reference for the full request structure.