The following entity relationship diagram (ERD) represents a standardized data model for the retail industry. The ERD is intentionally presented in a de-normalized fashion and with consideration for how data is stored in Adobe Experience Platform.
The ERD as described is a recommendation for how you should model your data for this industry use case. To make use of this data model in Platform, you must construct the recommended schemas and their relationships yourself. See the guides on managing schemas and relationships in the UI for more information.
Use the following legend to interpret this ERD:
The Experience Event entity includes an “_ID” field, which represents the unique identifier (
_id) attribute provided by the XDM ExperienceEvent class. See the reference document on XDM ExperienceEvent for more details on what is expected for this value.
The following table outlines the recommended classes and schema field groups for several common retail use cases.
|Use case||Recommended classes and field groups|
|Combine online and offline data sources and resolve cross-device and online/offline identity to provide holistic cross-channel and cross device attribution reporting.|
|Provide targeted and personalized experiences for various segments to increase revenue and help augment the platform in omnichannel orchestration.|
|Analyze multi-touch attribution to improve marketing efficiency.|
|Improve email relevance through improved men & women’s segmentation.|
|Ingest loyalty (partner) data to increase relevant product information across web, email, and digital marketing channels.|
|Retarget cart abandoners through automated and personalized emails.|
*While a standard product class is planned for a future release, product schemas must currently be built using a custom class instead. You must therefore manually build the structure of the schema’s class, as well as that of any field groups you add to it. See the section on creating a custom class in the XDM UI guide for more information.