As your organization evolves to use Customer Journey Analytics, explore these steps to prepare your data and to become aware of critical differences between the two technologies. This article is aimed at an administrator audience.
Preparing your Adobe Analytics data for a seamless move to Customer Journey Analytics is critical to data integrity and reporting consistency.
Perhaps the most critical component of understanding a customer journey is knowing who the customer is at each step. For Customer Journey Analytics, having an identifier that exists across all your channels and the corresponding data allows for stitching multiple sources together within Customer Journey Analytics.
Examples of identities might be a customer ID, account ID, or email ID. Whatever the identity (and there may be multiple), make sure you consider the following for each ID:
In datasets like Adobe Analytics, an identity may not exist on every row of data, but a secondary identity does. In this case, Cross-channel Analytics (formerly known as “Field-based Stitching”) can be used to bridge the gap between rows when a customer is only identified by their ECID and when an identity is collected (for example, when a customer authenticates). Learn more
The most straightforward method of transforming Adobe Analytics data into Customer Journey Analytics data is to ingest a global report suite into Experience Platform using the Analytics source connector. This connector maps your Adobe Analytics variables directly to an XDM schema and dataset in Experience Platform, which can in turn be easily connected to Customer Journey Analytics.
A full global report suite may not always be feasible for an implementation. If you are planning to bring multiple report suites into Customer Journey Analytics, you have 2 options:
Plan ahead to bring variables into alignment across those report suites. For example, eVar1 in report suite 1 may point to Page. In report suite 2, eVar1 may point to Internal Campaign. When brought into Customer Journey Analytics, these variables will mix into a single eVar1 dimension, leading to potentially confusing and inaccurate reporting.
Use the Data Prep feature to map variables. While it makes it easier if all report suites use the same common variable design, it’s not required if you use the new Experience Platform Data Prep feature. It allows you to reference a variable by its mapped value, which is at the datastream (or property) level.
If you have avoided moving to a global report suite due to issues with Uniques Exceeded or Low Traffic, know that Customer Journey Analytics has no cardinality limits on a dimension. It allows for any unique value to appear and be counted.
Here is a use case on combining report suites with different schemas.
Traditional Adobe Analytics Marketing Channel settings do not perform the same in Customer Journey Analytics. This is for two reasons:
The level of processing on the Adobe Analytics data ingested into Adobe Experience Platform, and
The report-time nature of Customer Journey Analytics
Adobe has published updated best practices for Marketing Channel implementation. These updated recommendations help you make the most of the capabilities already in Adobe Analytics with Attribution IQ. They will also set you up for success when transitioning to Customer Journey Analytics.
With the introduction of Derived fields as part of Customer Journey Analytics Data views, Marketing Channels are also supported in a non-destructive and retro-active manner using the Marketing Channel function template.
Adobe Analytics customers can easily leverage their report suites in the Adobe Experience Platform and Customer Journey Analytics using the Analytics source connector. For information on using the Analytics source connector, see the quick start guide on how to ingest data from Adobe Analytics and use it in Customer Journey Analytics. Also see Create an Adobe Analytics source connection in the UI for more information.
As Experience Edge data collection evolves, you will likely migrate to either the Adobe Experience Platform Web SDK or Adobe Experience Platform Mobile SDK with the Adobe Experience Platform Edge Network. While a typical implementation of the SDKs will send data into Adobe Analytics, a new opportunity presents itself for sending data directly to Adobe Experience Platform. It can then be ingested into Customer Journey Analytics, while also maintaining data sent to Adobe Analytics.
This method greatly expands possibilities for data collection: There is no longer a limitation on the number of fields or the need to map data elements to props, eVars, and events like in Analytics. You can use unlimited schema elements of different types and represent them in multiple ways using Customer Journey Analytics Data Views. Speed of data availability increases when sent directly to Adobe Experience Platform, as the time for data processing through Adobe Analytics is removed.
Advantages of using Experience Platform SDKs:
Drawbacks to using Experience Platform SDKs
The following Adobe Analytics features or components are not supported:
The reporting in Adobe Analytics relies on a significant amount of data pre-processing to generate results like the persistence that you see in eVars. By contrast, Customer Journey Analytics runs those calculations at report run time.
Report time processing opens the ability to apply settings that are retroactive and create multiple versions of variable persistence without needing to change how the underlying data is collected.
This shift will result in some differences in how data is reported, especially for any variables that may have a long expiration window. You can begin by evaluating how report-time processing may impact your reporting using a virtual report suite.
Adobe Analytics segments (called filters in Customer Journey Analytics) and calculated metrics are not compatible with Customer Journey Analytics. In many cases, these components can be rebuilt in Customer Journey Analytics using the new schemas and data available.
To make the transition as smooth as possible for users when they transition between the systems, plan ahead by
Identifying the most critical of these components.
Documenting their definitions, and
Here are a couple of videos to guide you:
Using the power of Customer Journey Analytics data views, you have a lot more flexibility in the definition of metrics and dimensions within Customer Journey Analytics. For example, you can use the value of a dimension to become the definition of a metric. Learn more
If you have defined a custom calendar in Adobe Analytics, you will have similar custom calendar capabilities within Customer Journey Analytics. You need to ensure that your calendar is properly defined.
In Customer Journey Analytics, you can define a custom visit/session timeout as well as define a metric that will start a new session. You can create data views with different session definitions to get insights above and beyond what was possible in Adobe Analytics. This capability may be particularly beneficial for mobile datasets.
Consider providing a data dictionary for your users – or extend the SDR to include the Experience Platform field name for schema elements.
After moving to Customer Journey Analytics, if you notice any data discrepancies, you can compare your original Adobe Analytics data with the Adobe Analytics data that is now in Customer Journey Analytics. Learn more