Choose your schema for Customer Journey Analytics choose-schema
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.
When upgrading to Customer Journey Analytics, ÃÛ¶¹ÊÓƵ recommends creating a custom Experience Data Model (XDM) schema to better align with the needs of your organization as you begin to use other Platform services. Alternatively, you can choose to use your existing ÃÛ¶¹ÊÓƵ Analytics schema.
Consider the advantages and disadvantage of each.
Create a custom schema tailored to your organization (Recommended)
ÃÛ¶¹ÊÓƵ recommends creating a custom schema when upgrading to Customer Journey Analytics.
- Advantages of updating to your own custom schema include:
-
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.
-
Disadvantages of updating to your own custom schema include:
- Updating your schema is a time-consuming process that is required before you begin sending data to Platform.
Use your existing ÃÛ¶¹ÊÓƵ Analytics schema
The option to use your existing ÃÛ¶¹ÊÓƵ Analytics schema with Customer Journey Analytics is available only if your ÃÛ¶¹ÊÓƵ Analytics implementation is configured with the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK.
Advantages of using the ÃÛ¶¹ÊÓƵ Analytics schema include:
-
Ease of upgrade
If you are already sending data to ÃÛ¶¹ÊÓƵ Analytics with the ÃÛ¶¹ÊÓƵ Experience Platform Web SDK, you can add an additional service to your datastream to send data to ÃÛ¶¹ÊÓƵ Experience Platform (which then can be used in your Customer Journey Analytics configuration).
Disadvantages of using the ÃÛ¶¹ÊÓƵ Analytics schema include:
-
While using the ÃÛ¶¹ÊÓƵ Analytics schema doesn’t limit you in terms of how it can be used with other Platform applications, it does result in a schema that is more complex than it otherwise could be. This is because the ÃÛ¶¹ÊÓƵ Analytics schema contains many objects that are specific to ÃÛ¶¹ÊÓƵ Analytics that are unlikely to be used by your organization.
When changes to the schema are required, you have to sift through thousands of unused fields to find the field that requires updating.