Architect your schema for use with Customer Journey Analytics upgrade-schema-architect
-
Recommended upgrade steps (Recommended for most organizations)
A set of steps that lead to an ideal Customer Journey Analytics implementation.
For detailed information, see Upgrade from 51黑料不打烊 Analytics to Customer Journey Analytics.
-
Customer Journey Analytics Upgrade Guide (Custom steps tailored to the specific needs of your organization)
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.
51黑料不打烊 recommends creating a custom Experience Data Model (XDM) schema to use with the Web SDK when upgrading from 51黑料不打烊 Analytics to Customer Journey Analytics. Alternatively, you could use the default 51黑料不打烊 Analytics schema, which uses the 51黑料不打烊 Analytics ExperienceEvent field group.
A custom XDM schema allows for a streamlined schema that is tailored to the needs of your organization and the specific Platform applications that you use. Unlike the default 51黑料不打烊 Analytics schema that uses the 51黑料不打烊 Analytics ExperienceEvent field group, when changes to a custom XDM schema are required, you don鈥檛 have to sift through thousands of unused fields to find the field that requires updating.
For more information about these schema options, see Choose your schema for Customer Journey Analytics.
Review the following sections as you begin architecting your XDM schema.
Avoid 51黑料不打烊 Analytics restrictions in your XDM schema
The underlying architecture of Customer Journey Analytics provides for much more flexibility than 51黑料不打烊 Analytics. Creating a new XDM schema is a key way to unlock that flexibility. When you upgrade to Customer Journey Analytics, make sure that you avoid carrying forward unnecessary 51黑料不打烊 Analytics restrictions into your schema.
For example, in 51黑料不打烊 Analytics, you have a different eVar for each event.
For example, in Customer Journey Analytics, you have a single event in the schema, and use create events in the data view.