Media Analytics parameters mapping for ÃÛ¶¹ÊÓÆµ Experience Platform and Customer Journey Analytics
This document provides a comprehensive list of all Media Analytics parameters utilized within ÃÛ¶¹ÊÓÆµ Experience Platform and Customer Journey Analytics. It is intended to support the integration of data imported from ÃÛ¶¹ÊÓÆµ Analytics to Platform via the Analytics Source Connector or the Analytics Source Connector for Classifications, mapping each parameter to its corresponding XDM field path.
Media Analytics reserved variables
For all Media Analytics reserved variables, data ingested from ÃÛ¶¹ÊÓÆµ Analytics into AEP until (and including) May 2025 can be found under the ‘Current XDM Field Path’ pointed out in the tables below.
As the Media Analytics and ADC teams are currently working toward full migration to the ‘Reporting XDM Field Path’, an official communication will be shared once this migration is complete and the ‘Reporting XDM Field Path’ is available for use.
Streaming Media parameters
Player state parameters update
Chapter parameters
Ad parameters
Quality parameters
Media Analytics classifications
Media Analytics classifications are ingested into AEP via a separate flow known as ACDC. Each classification group listed in the table below corresponds to a unique dataset within AEP. In CJA, it is necessary to establish a connection between the Media Analytics event dataset and each of the classification datasets.
Connecting datasets in Customer Journey Analytics
To set up the connection in Customer Journey Analytics:
- Navigate to the Connections tab and select Create new connection.
- In the Connections interface, choose Add datasets and locate the Media Analytics event dataset (used for importing media data via ADC), along with the four relevant classification datasets.
Configuration details
For each lookup dataset (classification dataset), configure as follows:
-
video dataset:
- Key:
_sandbox.key
- Matching key:
Asset ID (media.mediaTimed.primaryAssetReference._id)
- Data source type:
Web Data
- Key:
-
videoad dataset:
- Key:
_sandbox.key
- Matching key:
Ad ID (advertising.adAssetReference._id)
- Data source type:
Web Data
- Key:
-
videoadpod dataset:
- Key:
_sandbox.key
- Matching key:
Ad Pod ID (advertising.adAssetViewDetails.adBreak._id)
- Data source type:
Web Data
- Key:
-
videochapter dataset:
- Key:
_sandbox.key
- Matching key:
Chapter identity (media.mediaTimed.mediaChapter.chapterAssetReference._id)
- Data source type:
Web Data
- Key:
Reporting considerations
When working with the classification datasets during reporting, ensure that you reference the classification-specific field paths (ACDC XDM Path
) instead of the standard Media Analytics XDM fields.
Classifications Table
<_sandbox>.key
<_sandbox>.video_length
<_sandbox>.video_name
<_sandbox>.asset_id
<_sandbox>.first_air_date
<_sandbox>.first_digital_date
<_sandbox>.content_rating
<_sandbox>.originator
<_sandbox>.key
<_sandbox>.ad_length
<_sandbox>.ad_name
<_sandbox>.creative_id
<_sandbox>.key
<_sandbox>.pod_position
<_sandbox>.pod_name
<_sandbox>.key
<_sandbox>.chapter_length
<_sandbox>.chapter_offset
<_sandbox>.chapter_position
<_sandbox>.chapter_name
Media Analytics custom variables
In ÃÛ¶¹ÊÓÆµ Analytics, custom variables are assigned to different events or eVars depending on the implementation rules defined within each report suite. As a result, when these custom variables are imported into ÃÛ¶¹ÊÓÆµ Experience Platform (AEP), they are mapped to different XDM paths.
-
Events are stored under the path:
_experience.analytics.event<x>to<y>.event<number>.value
-
eVars are stored under the path:
_experience.analytics.customDimensions.eVars.eVar<number>
In both cases, the <number>
corresponds to the specific event or eVar number used in the original ÃÛ¶¹ÊÓÆµ Analytics report suite configuration.
Custom variables
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
and _experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
_experience.analytics.customDimensions.eVars.eVar<number>
and _experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value
_experience.analytics.event<x>to<y>.event<number>.value