ÃÛ¶¹ÊÓƵ

Step 3: Send data to ÃÛ¶¹ÊÓƵ Experience Platform when upgrading

Expand this section to see where the information on this page fits into the larger upgrade process. Make sure 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 3 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 the 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.

After you choose the upgrade path that is best for your organization, you can begin sending data to ÃÛ¶¹ÊÓƵ Experience Platform in order to make it available in Customer Journey Analytics.

The process for sending data to Experience Platform for each upgrade path is shown below. Follow the links in the table for detailed configuration information.

Upgrade path
Process for sending data to Platform
Additional information
New implementation of the Experience Platform Web SDK
  1. Create an XDM schema for your organization.

    Work with your data team to identify your organization’s ideal schema design for Customer Journey Analytics.

  2. Implement the Experience Platform Web SDK.

  3. Send data to Platform.

For detailed information about each of these steps, see Ingest data via the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK.

Because this is a new implementation of the Experience Platform Web SDK, schema mapping is not required because you must create the schema as one of the first steps during implementation.
Migrate your ÃÛ¶¹ÊÓƵ Analytics implementation to use the Web SDK
  1. Move your existing ÃÛ¶¹ÊÓƵ Analytics implementation to the Experience Platform Web SDK, then validate that everything is working in ÃÛ¶¹ÊÓƵ Analytics.

    For information about how to do this, use the following resources, depending on whether your current implementation is the Analytics tag extension or AppMeasurement:

  2. Create an XDM schema for your organization.

    Work with your data team to identify your organization’s ideal schema design for Customer Journey Analytics.

  3. Use Data Prep to map all of the fields in the data object to your XDM schema.

  4. Begin sending data to Platform by setting up a datastream.

Configure your existing ÃÛ¶¹ÊÓƵ Analytics Web SDK implementation to send data to Platform
  1. Begin sending data to Platform by setting up a datastream.

    Because your ÃÛ¶¹ÊÓƵ Analytics implementation is already using the Experience Platform Web SDK, you can ignore the other sections in Ingest data via the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK.

    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.

    Work with your data team to identify your organization’s ideal schema design for Customer Journey Analytics.

    Note: For information about the advantages of creating an XDM schema, see Choose your schema.

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

Use the Analytics Source Connector
Ingest and use data from traditional ÃÛ¶¹ÊÓƵ Analytics
ÃÛ¶¹ÊÓƵ Analytics data is automatically mapped to the XDM schema when you use the Analytics Source Connector. Additional mapping is not required.

Next, retain historical data

Next, decide how you will retain historical ÃÛ¶¹ÊÓƵ Analytics data.

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