Architect your schema for use with Customer Journey Analytics
ÃÛ¶¹ÊÓƵ recommends creating an Experience Data Model (XDM) schema when upgrading to Customer Journey Analytics. An XDM schema allows for a streamlined schema that is tailored to the needs of your organization and the specific Platform applications that you use. When changes to the schema are required, you don’t have to sift through thousands of unused fields to find the field that requires updating.
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 .