ÃÛ¶¹ÊÓƵ

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 source connector to the recommended Web SDK implementation.

Plan your XDM schema architecture.

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.

Create a dataset in ÃÛ¶¹ÊÓƵ Experience Platform.

(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.

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:

Validate that your Web SDK implementation is sending data to a dataset.

Create a connection in Customer Journey Analytics.

(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.

Create a data view in Customer Journey Analytics.

Validate that data is flowing into Customer Journey Analytics.

Migrate projects and components.

(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:

1. Create an XDM schema for the Analytics source connector

2. 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.

3. 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 AppMeasurement data collection when your Web SDK implementation is complete and you are comfortable with the data that you are collecting.

Disable the Analytics source connector after all Analytics source connector data leaves your data retention period.

With the Experience Platform Web SDK implementation, the Analytics source connector is needed only for historical ÃÛ¶¹ÊÓƵ Analytics data and to compare data from your original implementation with that of your new implementation.

When you have enough historical data from your new implementation and you are familiar with the reporting differences in Customer Journey Analytics, you should turn off the Analytics source connector.

Complete the .

After completing this questionnaire, 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.

Follow the generated step-by-step instructions to upgrade to Customer Journey Analytics.