Have a single consolidated view of customer behavior across various channels by unifying data from various web, mobile, and offline properties.
Create schemas for data to be ingested.
Create datasets for data to be ingested.
Ingest data into Experience Platform.
Data must be ingested into Platform before processing into Customer Journey Analytics.
Analyze cross-channel event datasets to be analyzed in union to make sure they have a common namespace ID or are rekeyed through the field-based stitching capability of Customer Journey Analytics.
Customer Journey Analytics does not currently use the Experience Platform Profile or Identity services for stitching.
Perform any custom data preparation or use of the field-based identity stitching on the data to ensure a common key across time series datasets to be ingested into Customer Journey Analytics.
Give lookup data a primary ID that can join to a field in the event data. Counts as rows in licensing.
Set the same primary ID for profile data as the primary ID of the event data.
Configure a data connection to ingest data from Experience Platform to Customer Journey Analytics. After data lands in the data lake, it processes into Customer Journey Analytics within 90 minutes.
Configure a data view on the connection to select the specific dimensions and metrics to be included in the view. Attribution and allocation settings are also configured in the data view. These settings are computed at report time.
Create a project to configure dashboards and reports within Analysis Workspace.
What are the downstream impacts of data models in Customer Journey Analytics?
Objects and attributes of the same XDM field merge into one dimension in Customer Journey Analytics. To merge multiple attributes from various datasets into the same Customer Journey Analytics dimension, the datasets should reference the same XDM field or schema.