High-level recommended upgrade process

  1. 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 Adobe Experience Platform is built to power real-time personalization use cases

    • Consolidate implementation for Adobe Experience Cloud data collection between other Experience Cloud products (AJO, RTCDP, and so forth)

    • Not reliant on Adobe Analytics nomenclature (prop, eVar, event, and so forth)

  2. Set up the Adobe 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, Adobe also recommends using the Adobe Analytics source connector. This allows you to retain historical data and view data from your existing Adobe 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 Adobe Analytics report suite data into Adobe Experience Platform and Customer Journey Analytics.

      You can keep the Analytics source connector running for as long as you need to retain the historical Adobe Analytics data.

    • View the data collected with your original Adobe 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 Adobe Analytics nomenclature (prop, eVar, and so forth), and difficulty in eventually moving from the Analytics source connector to the recommended Web SDK implementation.