Before you continue with this section, first make sure you have completed all previous upgrade tasks.
The information on this page covers Step 2 of the upgrade process, as highlighted in the table below:
Upgrade task | Details |
---|---|
Step 1: Get started with upgrade | Learn the benefits of upgrading to Customer Journey Analytics and the basic upgrade process. |
Step 2: Choose the upgrade path | Various methods are available for upgrading to Customer Journey Analytics. Choose the method that is best for your organization, depending on your organization’s current Adobe Analytics environment and long-term goals. |
Step 3: Send data to Adobe Experience Platform | The process for sending data to Adobe Experience Platform differs depending on the upgrade path that you chose in Step 2. |
Step 4: Retain historical data | Most organizations need to retain their historical Adobe Analytics data for a certain amount of time. Various options are available to accomplish this. |
Step 5: Perform additional implementation tasks | At this point in the upgrade process, you need to perform various tasks before your Customer Journey Analytics environment is ready to use. These additional tasks apply to upgrades from Adobe Analytics as well as new Customer Journey Analytics implementations. These tasks include:
For more information, see Customer Journey Analytics Getting Started. |
After you decide to upgrade to Customer Journey Analytics, you need to determine the optimal upgrade path for your organization.
The path that you choose for upgrading from Adobe Analytics to Customer Journey Analytics depends on the following factors:
Your existing Adobe Analytics implementation
Your goals for the future
Use the information on this page to determine which Customer Journey Analytics upgrade path best aligns with your organization’s current implementation and future goals.
To determine the optimal upgrade path for your organization, the following sections should be read sequentially:
Various upgrade paths exist for upgrading from Adobe Analytics to Customer Journey Analytics.
In general, each upgrade path differs in the level of effort required to execute the upgrade, as well as in the long-term viability achieved after the upgrade completes.
The following table lists each upgrade path, its level of effort, and its long-term viability:
Upgrade path | Level of effort | Long-term viability |
---|---|---|
New implementation of the Experience Platform Web SDK with the Analytics source connectorYou can begin using Customer Journey Analytics by doing a new implementation of the Experience Platform Web SDK. This allows you to begin sending data to Adobe Experience Platform Edge Network and Customer Journey Analytics. In addition, you use the Analytics source connector to bring historical data into Customer Journey Analytics. For organizations not yet on the Web SDK, this upgrade path is perhaps the most straightforward in getting data to Edge Network because it requires the fewest number of steps; however, because all of the work is done up front (such as creating the XDM schema), it requires a larger initial effort. The basic steps are:
|
High | High |
New implementation of the Experience Platform Web SDKYou can begin using Customer Journey Analytics by doing a new implementation of the Experience Platform Web SDK. This allows you to begin sending data to Adobe Experience Platform Edge Network and Customer Journey Analytics. For organizations not yet on the Web SDK, this upgrade path is perhaps the most straightforward in getting data to Edge Network because it requires the fewest number of steps; however, because all of the work is done up front (such as creating the XDM schema), it requires a larger initial effort. The basic steps are:
|
High | High |
Migrate your Adobe Analytics implementation to use the Web SDKIf your Adobe Analytics implementation is AppMeasurement or the Analytics extension, you can migrate it to use the Adobe Experience Platform Web SDK to begin sending data to Edge Network and Adobe Analytics, prior to sending it to Customer Journey Analytics. For organizations not yet on the Web SDK, this is the easiest and smoothest way to get data to Edge Network; it requires more steps, but offers a more methodical transition from Adobe Analytics to Customer Journey Analytics, with more tangible milestones. The basic steps are:
|
Moderate | High |
Configure your existing Adobe Analytics Web SDK implementationIf your Adobe Analytics implementation is already using the Adobe Experience Platform Web SDK, you can begin sending data to Platform by setting up a datastream. Or, if you are already sending data to Platform, you simply need to create a connection between Platform datasets and Customer Journey Analytics. Before you send data to Platform for use in Customer Journey Analytics, consider updating your Adobe Analytics schema for the specific needs of your organization and any other Platform applications you use. The basic steps are:
|
Low | High |
Use the Analytics Source ConnectorIf your Adobe Analytics implementation is AppMeasurement or the Analytics extension, you can begin sending data to a data view in Customer Journey Analytics. This is the easiest way to get data to Customer Journey Analytics, but is the least viable method in the long term. Note: This upgrade path can be used independently. However, for best results, we recommended using this upgrade path in conjunction with a new implementation of the Experience Platform WebSDK. |
Low | Low |
Use the following diagram to help visualize where each upgrade path falls on the spectrum in terms of level of effort and long-term viability:
Not all upgrade paths are available for each type of Adobe Analytics implementation.
Use the information below to help you understand which upgrade path is most appropriate for your organization.
Contact your Adobe representative if you need more specific advice, guidance, or support.
Existing Adobe Analytics implementation | Available upgrade paths |
---|---|
AppMeasurement |
|
Adobe Analytics extension |
|
Web SDK |
|
The advantages and disadvantages of a given upgrade path differ depending on your existing Adobe Analytics implementation.
Before you use the information below to determine which upgrade path is right for you, review the information in Understand upgrade paths if you haven’t already.
While each of the upgrade paths described in the following sections can be used independently, Adobe recommends a two-pronged upgrade approach when upgrading from Adobe Analytics to Customer Journey Analytics, regardless of your current Adobe Analytics implementation: the Adobe Analytics source connector and a new implementation of the Experience Platform WebSDK.
Following are the upgrade paths available for organizations who have implemented Adobe Analytics with AppMeasurement or the Adobe Analytics extension. Expand each section to view the advantages and disadvantages of each upgrade path.
Advantages | Disadvantages |
---|---|
|
|
Advantages | Disadvantages |
---|---|
|
|
Advantages | Disadvantages |
---|---|
|
Because of these disadvantages, Adobe recommends using the Analytics source connector in conjunction with a new implementation of the Experience Platform Web SDK. |
The following upgrade path is available for organizations who have implemented Adobe Analytics with the Experience Platform Web SDK.
When choosing this upgrade path, you also need to choose your schema.
Advantages | Disadvantages |
---|---|
This is the preferred upgrade path if your Adobe Analytics implementation is already using the Web SDK.
|
None |
If you chose the upgrade path that allows you to configure the Adobe Analytics Web SDK implementation to send data to Platform, you can choose the schema that you want to use.
You can choose whether to use your existing Adobe Analytics schema, or you can update to your own XDM schema to better align with the needs of your organization as you begin to use other Platform services.
Advantages | Disadvantages |
---|---|
Advantages of using the Adobe Analytics schema include:
|
Disadvantages of using the Adobe Analytics schema include:
|
Advantages | Disadvantages |
---|---|
Advantages of updating to your own XDM schema include: When changes to the schema are required, you don’t have to sift through thousands of unused fields to find the field that requires updating. |
Disadvantages of updating to your own XDM schema include:
|
After you use the information above to choose a upgrade path, learn how to send data to Adobe Experience Platform depending on the upgrade path that you chose.