Architect your schema for use with Customer Journey Analytics upgrade-schema-architect
ÃÛ¶¹ÊÓƵ recommends creating a custom Experience Data Model (XDM) schema to use with the Web SDK when upgrading from ÃÛ¶¹ÊÓƵ Analytics to Customer Journey Analytics. Alternatively, you could use the default ÃÛ¶¹ÊÓƵ Analytics schema, which uses the ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Analytics schema that uses the ÃÛ¶¹ÊÓƵ Analytics ExperienceEvent field group, when changes to a custom XDM schema are required, you don’t 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 ÃÛ¶¹ÊÓƵ Analytics restrictions in your XDM schema
The underlying architecture of Customer Journey Analytics provides for much more flexibility than ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Analytics restrictions into your schema.
For example, in ÃÛ¶¹ÊÓƵ 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.
Identify your data team and other stakeholders throughout your organization
Consider other ÃÛ¶¹ÊÓƵ Experience Platform applications used in your organization
- Continue following the recommended upgrade steps or the .