Upgrade from ÃÛ¶¹ÊÓÆµ Analytics to Customer Journey Analytics
When upgrading from ÃÛ¶¹ÊÓÆµ Analytics to Customer Journey Analytics, you can follow the recommended upgrade steps. Or you can dynamically generate upgrade steps for your organization’s unique circumstances.
Recommended upgrade steps for most organizations upgrade-process
The recommended process of upgrading from ÃÛ¶¹ÊÓÆµ Analytics to Customer Journey Analytics is a new implementation of the Experience Platform Web SDK, which is the preferred data collection method for Customer Journey Analytics. In conjunction with the Web SDK, ÃÛ¶¹ÊÓÆµ also recommends using the Analytics source connector to help with your transition to Customer Journey Analytics. Use the Analytics source connector to retain historical ÃÛ¶¹ÊÓÆµ Analytics data and to perform side-by-side data comparison.
After you have enough historical data using the Experience Platform Web SDK and you have fully transitioned to Customer Journey Analytics, the Analytics source connector can be turned off and the Web SDK can be used exclusively.
High-level recommended upgrade process high-level-upgade-process
-
Implement the Experience Platform Web SDK (for ongoing data collection)
A new implementation of the Experience Platform Web SDK is the best way to collect data for Customer Journey Analytics. It provides the best foundation to get the most out of Customer Journey Analytics because it is the most performant, straightforward, and future-proof method for implementing Customer Journey Analytics.
-
Highly performant reporting and data availability because ÃÛ¶¹ÊÓÆµ Experience Platform is built to power real-time personalization use cases
-
Consolidate implementation for ÃÛ¶¹ÊÓÆµ Experience Cloud data collection between other Experience Cloud products (AJO, RTCDP, and so forth)
-
Not reliant on ÃÛ¶¹ÊÓÆµ Analytics nomenclature (prop, eVar, event, and so forth)
-
-
Set up the ÃÛ¶¹ÊÓÆµ Analytics source connector (for bringing over historical data)
To help with a smooth transition to using the Experience Platform Web SDK with Customer Journey Analytics, ÃÛ¶¹ÊÓÆµ also recommends using the ÃÛ¶¹ÊÓÆµ Analytics source connector. This allows you to retain historical data and view data from your existing ÃÛ¶¹ÊÓÆµ Analytics implementation in Customer Journey Analytics, side by side with the data from your new Experience Platform Web SDK implementation.
The Analytics source connector allows you to:
-
Bring your historical ÃÛ¶¹ÊÓÆµ Analytics report suite data into ÃÛ¶¹ÊÓÆµ Experience Platform and Customer Journey Analytics.
You can keep the Analytics source connector running for as long as you need to retain the historical ÃÛ¶¹ÊÓÆµ Analytics data.
-
View the data collected with your original ÃÛ¶¹ÊÓÆµ Analytics implementation (either AppMeasurement, the Analytics Extension, or the Web SDK Extension) within Customer Journey Analytics. You can compare this data side-by-side with that of your new Web SDK implementation.
You can keep the Analytics source connector running until you are familiar and comfortable with the differences.
The Analytics source connector as a stand-alone implementation is not a recommended long-term method for using Customer Journey Analytics. This is because of high latency, cluttered and complex schemas, reliance on ÃÛ¶¹ÊÓÆµ Analytics nomenclature (prop, eVar, and so forth), and difficulty in eventually moving from the Analytics source connector to the recommended Web SDK implementation.
-
Detailed recommended upgrade steps
The following steps outline the recommended process for upgrading from ÃÛ¶¹ÊÓÆµ Analytics to Customer Journey Analytics.
Each step provides a high-level explanation of a more detailed process. Follow the link for each step and complete its associated tasks, then return to this page and continue to the next step in the process.
-
Create your desired custom schema in ÃÛ¶¹ÊÓÆµ Experience Platform.
Consider the following options when creating your schema:
-
If you want to integrate Customer Journey Analytics with RTCDP, you must enable the Profile option on your schema, as described in Create an XDM schema to use with Customer Journey Analytics. With this option enabled, when data is ingested into datasets based on this schema, that data is merged into the Real-Time Customer Profile.
-
If you want to include streaming media data, you must configure your schema to ingest and use streaming data.
-
-
(Optional) If you use classification data in ÃÛ¶¹ÊÓÆµ Analytics, you can add classification data to your dataset in Customer Journey Analytics.
To do this, create a lookup dataset for each dimension containing classification data.
-
For ÃÛ¶¹ÊÓÆµ Analytics implementations using AppMeasurement or the Analytics extension (tags), create a datastream in ÃÛ¶¹ÊÓÆµ Experience Platform.
For ÃÛ¶¹ÊÓÆµ Analytics implementations using the Web SDK, a datastream already exists. For more information, see Configure your existing ÃÛ¶¹ÊÓÆµ Analytics Web SDK implementation to send data to Platform.
-
Add ÃÛ¶¹ÊÓÆµ Experience Platform as a service to your datastream.
-
(Optional) If you want to integrate Customer Journey Analytics with ÃÛ¶¹ÊÓÆµ Journey Optimizer, use the personalization object in your implementation for use in ÃÛ¶¹ÊÓÆµ Journey Optimizer.
-
Expand the section that describes how you want to implement the Experience Platform Web SDK for your Customer Journey Analytics implementation, then complete the associated steps:
accordion Manual implementation (JS file) -
Populate an XDM object and send it to the datastream.
accordion Tags accordion API - Use the Edge Network API to send data to the desired datastream.
-
Validate that your Web SDK implementation is sending data to a dataset.
-
(Optional) Tie web data with data from other channels, such as call center data.
You accomplish this by adding additional datasets to your Customer Journey Analytics connection, as described in Import call center and web data.
-
Validate that data is flowing into the data view in Customer Journey Analytics.
-
In your ÃÛ¶¹ÊÓÆµ Analytics environment, use the Analytics Inventory to see a comprehensive overview of your ÃÛ¶¹ÊÓÆµ Analytics environment, including the number of projects and components, report suites, users, and more.
-
(Optional) If you use marketing channels in ÃÛ¶¹ÊÓÆµ Analytics, you can create a marketing channel derived field in Customer Journey Analytics.
Derived fields are an important aspect of the real-time reporting in Customer Journey Analytics. A derived field allows you to define (often complex) data manipulations on the fly, through a customizable rule builder.
One use for derived fields is to define a derived Marketing Channel field that determines the proper marketing channel based on one or more conditions (for example, URL parameter, page URL, or page name).
Use the marketing channels function template in derived fields to quickly create a derived field for marketing channels.
-
Compare data in ÃÛ¶¹ÊÓÆµ Analytics from your old implementation to data in Customer Journey Analytics from your new implementation and make sure you understand any differences and why they exist.
-
Bring historical data from ÃÛ¶¹ÊÓÆµ Analytics using the Analytics source connector:
note note NOTE Use the following steps if you have not previously created an Analytics source connector. If you are already using the Analytics source connector with Customer Journey Analytics, follow the steps in Transition from the Analytics source connector to the Web SDK for Customer Journey Analytics. -
If you don’t already have an Analytics source connector, create the Analytics source connector and map fields to your XDM schema.
Or
If you already have an Analytics source connector, map fields from the source connector to your XDM schema.
-
Add the Analytics source connector dataset to the connection.
-
Plan user onboarding.
Like in ÃÛ¶¹ÊÓÆµ Analytics, Analysis Workspace is the main user-facing tool in Customer Journey Analytics. However, there are some key differences when using Analysis Workspace in Customer Journey Analytics that users need to be aware of.
You should give your users ample time (3 - 6 months) to become familiar with the key differences of Analysis Workspace in Customer Journey Analytics.
For information about some of the key differences between ÃÛ¶¹ÊÓÆµ Analytics and Customer Journey Analytics, see User Guide for ÃÛ¶¹ÊÓÆµ Analytics users.
-
Learn about feature support in Customer Journey Analytics. Most ÃÛ¶¹ÊÓÆµ Analytics features are supported in Customer Journey Analytics, and many additional features are available in Customer Journey Analytics.
-
Disable ÃÛ¶¹ÊÓÆµ Analytics when your Customer Journey Analytics Web SDK implementation is complete and you are comfortable with the data that you are collecting.
ÃÛ¶¹ÊÓÆµ recommends that you keep your ÃÛ¶¹ÊÓÆµ Analytics environment running for a period of time after implementing Customer Journey Analytics.
For more information about the uses of ÃÛ¶¹ÊÓÆµ Analytics during and after an upgrade, as well as the suggested timing of disabling ÃÛ¶¹ÊÓÆµ Analytics, see Evaluate how long you need ÃÛ¶¹ÊÓÆµ Analytics after upgrading to Customer Journey Analytics.
Dynamically generate upgrade steps for your organization
Depending on several factors, such as timeline and resource constraints, the recommended upgrade steps described in Understand the recommended upgrade steps might not be practical for your organization. In this case, you can dynamically generate upgrade steps for your organization’s unique circumstances. The process of generating these steps differs depending on whether you already have access to Customer Journey Analytics.
For customers who have access to Customer Journey Analytics
To dynamically generate upgrade steps for your organization’s unique circumstances:
-
Complete the Customer Journey Analytics Upgrade Guide.
In Customer Journey Analytics, select the Workspace tab, then select Upgrade to Customer Journey Analytics in the left panel. Follow the on-screen instructions.
After completing this upgrade guide, step-by-step instructions are provided to you, outlining the optimal upgrade steps that are unique to your organization requirements. These are the upgrade steps that best align with your existing ÃÛ¶¹ÊÓÆµ Analytics environment and your goals for Customer Journey Analytics. The upgrade steps are available as a shareable link or as a downloadable .csv file.
-
Follow the generated step-by-step instructions to upgrade to Customer Journey Analytics.
For customers who do not yet have access to Customer Journey Analytics
To dynamically generate upgrade steps for your organization’s unique circumstances:
-
Contact your ÃÛ¶¹ÊÓÆµ Account Team to complete the Customer Journey Analytics Upgrade Guide.
Your ÃÛ¶¹ÊÓÆµ Account Team can take you through the upgrade guide and provide you with a .csv file that contains the questions, your answers, and the dynamically generated upgrade steps that are unique to your organization.
Prior to contacting your ÃÛ¶¹ÊÓÆµ Account Team, familiarize yourself with the questions that are included in the Customer Journey Analytics Upgrade Guide and determine your answers. The Customer Journey Analytics Upgrade Guide contains the following questions and possible answers:
table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3 6-row-3 7-row-3 Question Available answers Additional information Select the option that describes your current ÃÛ¶¹ÊÓÆµ Analytics implementation. This information can affect alternative upgrade options that might be available to you when upgrading to Customer Journey Analytics. Select one:
- AppMeasurement:
A JavaScript implementation that loads AppMeasurement.js on a page, and sends data to ÃÛ¶¹ÊÓÆµ using the s object (for example, s.eVar1). - ÃÛ¶¹ÊÓÆµ Analytics extension (tags):
A tags implementation that loads ÃÛ¶¹ÊÓÆµ Experience Platform Data Collection (formerly known as Launch). The tag has the ÃÛ¶¹ÊÓÆµ Analytics extension installed. - Experience Platform Web SDK extension (tags):
A tags implementation that loads ÃÛ¶¹ÊÓÆµ Experience Platform Data Collection (formerly known as Launch). The tag has the Web SDK extension installed. - Experience Platform Web SDK (alloy.js): A JavaScript implementation that loads the Web SDK library (alloy.js) on a page, and sends data to ÃÛ¶¹ÊÓÆµ using a JSON payload.
- Bulk Data Insertion API:
An implementation that uses the data insertion API or bulk data insertion API. - Experience Platform Mobile SDK:
An implementation that uses the ÃÛ¶¹ÊÓÆµ Experience Platform Mobile SDK. - AppMeasurement using a third-party tag management tool:
An implementation that uses a third-party tag management tool. - A non-ÃÛ¶¹ÊÓÆµ Analytics product:
An implementation that collects data for a product other than ÃÛ¶¹ÊÓÆµ Analytics, such as Google Analytics.
- AppMeasurement: