Migrate Customer Journey Analytics to use the new Streaming Media fields
This document describes how a Customer Journey Analytics setup that uses the 蜜豆视频 Streaming Media Collection data type called 鈥淢edia鈥 should be updated to use the new corresponding data type called 鈥Media Reporting Details.鈥
Migrate Customer Journey Analytics
To migrate a Customer Journey Analytics setup from the old data type called 鈥淢edia鈥 to the new data type called 鈥Media Reporting Details,鈥 you must update the following setups that are using the old data type:
-
Data views
-
Derived fields
Migrate data views
To migrate the data views to the new data type:
-
Locate all the data views using the deprecated 鈥淢edia鈥 data type. This is all fields for which the path begins with
media.mediaTimed. -
Do either of the following:
-
In those data views, insert the fields from the new 鈥淢edia Reporting Details鈥 data type.
-
Create a derived field that uses the new 鈥淢edia Reporting Details鈥 data type if it is set, or that falls back to the old 鈥淢edia鈥 data type if the 鈥淢edia Reporting Details鈥 data type is not set.
-
Migrate derived fields
To migrate derived fields to the new data type:
-
Locate all the derived fields using the deprecated 鈥淢edia鈥 data type. This is all derived fields that contain fields for which the path begins with
media.mediaTimed. -
Replace all the old fields in the derived field with the new corresponding field from 鈥淢edia Reporting Details.鈥
See the Content ID parameter on the Audio and video parameters page to map between the old fields and the new fields. The old field path is found under the 鈥淴DM Field Path鈥 property while the new field path is found under the 鈥淩eporting XDM Field Path鈥 property.
Example
To make it easier to follow the migration guidelines, consider the following example that contains a data view with fields from the old deprecated 鈥淢edia鈥 data type. In this data view, you need to add the new corresponding fields.
Update the data view
You can use either of the following options to update the data view:
Option 1
-
Locate a metric or a dimension that is using the old field from the deprecated data type.
-
Check the corresponding new field in the Chapter offset section in the Chapter parameters article.
-
Locate the new corresponding field in the data view.
-
Drag the new field to the metric or dimension.
-
Repeat this process for all metrics and dimensions that use fields from the deprecated 鈥淢edia鈥 data type.
Option 2
This option creates a derived field that selects the value from the old field or the value from the new field based on which one exists for a specific event. This derived field replaces the old 鈥淢edia鈥 data type in any projects where it is being used.
If you want to create a derived field for the 鈥淐hapter Name鈥 that uses the new 鈥淢edia Reporting Details鈥 data type if it is set, or that falls back to the old 鈥淢edia鈥 data type if the 鈥淢edia Reporting Details鈥 data type is not set:
-
Drag a 鈥淐ase When鈥 clause into the derived fields.
-
Populate the If clause using the value of the Reporting XDM Field Path, as shown in the Chapter name parameter on the Chapter parameters page.
-
Populate the fallback value using the old field from the deprecated 鈥淢edia鈥 data type.
This is the final definition of the derived field.
-
To update the derived fields, locate a derived field that is using the old deprecated fields (path starting with
media.mediaTimed).
-
Mouse over the derived field that you want to update, then select the Edit icon.
-
Locate all the fields from the old data type (path starting with
media.mediaTimed) and replace them with the new corresponding field.
-
Check the corresponding new field in the Content Name (variable) section in the Streaming Media parameters article.
-
Replace the old field with the new field.
-
Repeat this process for all the derived fields using fields from the old deprecated 鈥淢edia鈥 data type.
The migration of the CJA setup is completed.