۶Ƶ

DocumentationCustomer Journey AnalyticsCustomer Journey Analytics Guide

Step 2: Choose your upgrade path

Last update: Tue Mar 11 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
Expand this section to see where the information on this page fits into the larger upgrade process. Make sure that all previous upgrade steps are complete.

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:

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 layout-auto
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 ۶Ƶ Analytics environment and long-term goals.
Step 3: Send data to ۶Ƶ Experience Platform The process for sending data to ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ Analytics as well as new Customer Journey Analytics implementations.

These tasks include:

  • Bringing other data into Experience Platform
  • Creating connections between Platform datasets and Customer Journey Analytics
  • Creating data views
  • Porting the reporting API usage
  • Accounting for Data Feeds and Data Warehouse
  • Migrating projects and components
  • Planning user onboarding

For more information, see Customer Journey Analytics Getting Started.
AVAILABILITY
The information on this page is being replaced with the following more comprehensive upgrade information:

  • Recommended upgrade steps

    For detailed information, see Recommended path when upgrading from ۶Ƶ Analytics to Customer Journey Analytics.

  • Customer Journey Analytics Upgrade Guide

    A new upgrade guide is available that dynamically generates upgrade steps that are tailored for your organization and your unique circumstances.

    To access the guide from Customer Journey Analytics, select the Workspace tab, then select Upgrade to Customer Journey Analytics in the left panel. Follow the on-screen instructions.

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 ۶Ƶ Analytics to Customer Journey Analytics depends on the following factors:

  • Your existing ۶Ƶ 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:

  1. First, understand the upgrade paths that are available.

  2. Then, assess which upgrade paths are available to you.

  3. And finally, weigh the advantages and disadvantages of each upgrade path.

Understand upgrade paths

Various upgrade paths exist for upgrading from ۶Ƶ 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 connector
You 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 ۶Ƶ 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:

  1. Create an XDM schema for your organization.
  2. Implement the Web SDK.
  3. Send data to Platform.
  4. Set up the Analytics source connector.
    The Analytics source connector is used to bring historical ۶Ƶ Analytics data into Customer Journey Analytics.
High
High

New implementation of the Experience Platform Web SDK
You 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 ۶Ƶ 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:

  1. Create an XDM schema for your organization.
  2. Implement the Web SDK.
  3. Send data to Platform.
High
High

Migrate your ۶Ƶ Analytics implementation to use the Web SDK
If your ۶Ƶ Analytics implementation is AppMeasurement or the Analytics extension, you can migrate it to use the ۶Ƶ Experience Platform Web SDK to begin sending data to Edge Network and ۶Ƶ 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 ۶Ƶ Analytics to Customer Journey Analytics, with more tangible milestones.

The basic steps are:

  1. Move your existing ۶Ƶ Analytics implementation to the Web SDK and validate that everything is working in ۶Ƶ Analytics.
  2. Create an XDM schema for your organization as you have time.
  3. Use Datastream mapping to map all of the fields in the data object to your XDM schema.
  4. Send data to Platform.
Moderate
High

Configure your existing ۶Ƶ Analytics Web SDK implementation
If your ۶Ƶ Analytics implementation is already using the ۶Ƶ 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 ۶Ƶ Analytics schema for the specific needs of your organization and any other Platform applications you use.

The basic steps are:

  1. Begin sending data to Platform.

    If you are already sending data to Platform with your ۶Ƶ Analytics implementation, this step is not required. You simply need to create a connection between Platform datasets and Customer Journey Analytics, as described later in this process.

  2. (Optional) Create an XDM schema for your organization as you have time.

  3. (Conditional) If you created an XDM schema, use datastream mapping to map all of the fields in the data object to your XDM schema.

Low
High

Use the Analytics Source Connector
If your ۶Ƶ 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:

cja upgrade paths

Assess the upgrade paths available to you based on your current ۶Ƶ Analytics implementation

Not all upgrade paths are available for each type of ۶Ƶ Analytics implementation.

Use the information below to help you understand which upgrade path is most appropriate for your organization.

Contact your ۶Ƶ representative if you need more specific advice, guidance, or support.

Existing ۶Ƶ Analytics implementation
Available upgrade paths
AppMeasurement
  • New implementation of the Experience Platform Web SDK
  • Migrate ۶Ƶ Analytics to the Web SDK
  • Analytics Source Connector
  • (Recommended) New implementation of the Experience Platform Web SDK with the Analytics Source Connector
۶Ƶ Analytics extension
  • New implementation of the Experience Platform Web SDK
  • Migrate ۶Ƶ Analytics to the Web SDK
  • Analytics Source Connector
  • (Recommended) New implementation of the Experience Platform Web SDK with the Analytics Source Connector
Web SDK
  • Configure the ۶Ƶ Analytics Web SDK implementation to send data to Platform
  • (Recommended) New implementation of the Experience Platform Web SDK with the Analytics Source Connector

Weigh the advantages and disadvantages of the upgrade paths available to you

The advantages and disadvantages of a given upgrade path differ depending on your existing ۶Ƶ 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.

NOTE
While each of the upgrade paths described in the following sections can be used independently, ۶Ƶ recommends a two-pronged upgrade approach when upgrading from ۶Ƶ Analytics to Customer Journey Analytics, regardless of your current ۶Ƶ Analytics implementation: the ۶Ƶ Analytics source connector and a new implementation of the Experience Platform WebSDK.

For ۶Ƶ Analytics implementations using: AppMeasurement and ۶Ƶ Analytics extension

Following are the upgrade paths available for organizations who have implemented ۶Ƶ Analytics with AppMeasurement or the ۶Ƶ Analytics extension. Expand each section to view the advantages and disadvantages of each upgrade path.

Upgrade paths

New implementation of the Experience Platform Web SDK
table 0-row-2 1-row-2 layout-auto
Advantages Disadvantages

  • Provides all the advantages of hosting data in Experience Edge Network:

    These advantages include:

    • 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)

  • Future-proof: Future implementation updates are easier.
  • Requires a new implementation from scratch: The requirement to do a new implementation from scratch means the following disadvantages:
    • Time consuming: This is the most time-consuming and demanding upgrade path because it requires that you start over with a new implementation.
    • Must re-create the full schema in XDM: Before you can start implementing the Web SDK, you have to re-create the full schema in XDM.
    • Must re-create rules and data elements: Before you can start implementing the Web SDK, you have to re-create any rule conditions and data elements from your ۶Ƶ Analytics implementation. Does not account for retaining historical data: ۶Ƶ recommends using the Analytics source connector in conjunction with a new implementation of the Experience Platform Web SDK in order to retain historical data after upgrading to Customer Journey Analytics.
  • Does not account for comparing data from your original implementation with that of your new implementation: ۶Ƶ recommends using the Analytics source connector in conjunction with a new implementation of the Experience Platform Web SDK in order to compare data after upgrading to Customer Journey Analytics.
Migrate ۶Ƶ Analytics to the Experience Platform Web SDK
table 0-row-2 1-row-2 layout-auto
Advantages Disadvantages

  • Provides all the advantages of hosting data in Experience Edge Network:

    These advantages include:

    • 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)

  • Uses your existing implementation: While this approach requires some implementation changes, it does not require a completely new implementation from scratch. You can use your existing data layer and code with minimal changes to implementation logic without impacting your existing ۶Ƶ Analytics reporting.

  • Provides flexibility to create an XDM schema for your organization at a later time: You can migrate your existing ۶Ƶ Analytics implementation to use the Web SDK and validate that everything is working in ۶Ƶ Analytics, then create the XDM schema. This flexibility allows for a more methodical and thoughtful upgrade to Customer Journey Analytics.
  • Requires mapping to send data to Platform: When your organization is ready to use Customer Journey Analytics, you must send data to a data set in ۶Ƶ Experience Platform. This action requires that every field in the data object be an entry in the datastream mapping tool that assigns it to an XDM schema field. Mapping only needs to be done once for this workflow, and it doesn’t involve making implementation changes. However, it is an extra step that is not required when sending data in an XDM object.
  • Technical debt: Because this approach uses a modified form of your existing implementation, it can be harder to track implementation logic and perform changes in the future when needed.
Use the Analytics Source Connector
table 0-row-2 1-row-2 layout-auto
Advantages Disadvantages

  • Least time-consuming and demanding upgrade path.

    Data is migrated to Customer Journey Analytics quickly with minimal investment

  • Data is not sent to Edge Network:

    This results in the following disadvantages:

    • Highest level of latency in reporting across all upgrade paths; not optimized for real-time personalization use cases.
    • Data cannot be shared with other ۶Ƶ Experience Platform applications; it is constrained to Customer Journey Analytics only
    • Reliant on ۶Ƶ Analytics nomenclature (prop, eVar, event, and so forth)

  • Difficult to move to the Web SDK in the future: Eventually, you will likely want access to the advantages provided by the Experience Platform Web SDK. In order to start using the Experience Platform Web SDK, you must do a new implementation.

  • Uses the Analytics Experience Event field group in your schema: This field group adds many ۶Ƶ Analytics events that are not needed in your Customer Journey Analytics schema. This can lead to a more cluttered, complex schema than what is otherwise needed for Customer Journey Analytics.

Because of these disadvantages, ۶Ƶ recommends using the Analytics source connector in conjunction with a new implementation of the Experience Platform Web SDK.

For ۶Ƶ Analytics implementations using: Web SDK

The following upgrade path is available for organizations who have implemented ۶Ƶ Analytics with the Experience Platform Web SDK.

When choosing this upgrade path, you also need to choose your schema.

Upgrade path

Configure the ۶Ƶ Analytics Web SDK implementation to send data to Platform
table 0-row-2 1-row-2 layout-auto
Advantages Disadvantages

This is the preferred upgrade path if your ۶Ƶ Analytics implementation is already using the Web SDK.

  • Provides all the advantages of hosting data in Experience Edge Network:

    These advantages include:

    • 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)

  • Uses your existing implementation: While this approach requires some implementation changes, it does not require a completely new implementation from scratch. You can use your existing data layer and code with minimal changes to implementation logic without impacting your existing ۶Ƶ Analytics reporting.

  • Provides an option to use an XDM schema: You can choose to use your existing ۶Ƶ Analytics schema or create an XDM schema and map fields in the data object to your XDM schema. XDM schemas are a flexible schema to define any fields you need, and only those fields that are relevant.

    See “Using your own XDM schema” below for more information about the advantages of using your own XDM schema.

  • Retains rules and data elements: While it does require new rule actions, you can reuse your existing data elements and rule conditions with minimal changes.

  • Future-proof: If you choose to use your own XDM schema, then future implementation updates are easier.

 None

Choose your schema

If you chose the upgrade path that allows you to configure the ۶Ƶ 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 ۶Ƶ 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.

Use the ۶Ƶ Analytics schema with the ۶Ƶ Analytics Web SDK implementation
table 0-row-2 1-row-2
Advantages Disadvantages

Advantages of using the ۶Ƶ Analytics schema include:

  • Ease of upgrade

    If you are already sending data to ۶Ƶ Analytics with the ۶Ƶ Experience Platform Web SDK, you can add an additional service to your datastream to send data to ۶Ƶ Experience Platform (which then can be used in your Customer Journey Analytics configuration).

Disadvantages of using the ۶Ƶ Analytics schema include:

  • While using the ۶Ƶ Analytics schema doesn’t limit you in terms of how it can be used with other Platform applications, it does result in a schema that is more complex than it otherwise could be. This is because the ۶Ƶ Analytics schema contains many objects that are specific to ۶Ƶ Analytics that are unlikely to be used by your organization.

    When changes to the schema are required, you have to sift through thousands of unused fields to find the field that requires updating.
Use your own XDM schema with the ۶Ƶ Analytics Web SDK implementation
table 0-row-2 1-row-2
Advantages Disadvantages
  • Advantages of updating to your own XDM schema include:

    • A streamlined schema that is tailored to the needs of your organization and the specific Platform applications that you use.

      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:

  • Updating your schema is a time-consuming process that is required before you begin sending data to Platform.

Next, send data to ۶Ƶ Experience Platform

After you use the information above to choose a upgrade path, learn how to send data to ۶Ƶ Experience Platform depending on the upgrade path that you chose.

recommendation-more-help
080e5213-7aa2-40d6-9dba-18945e892f79