The following entity relationship diagram (ERD) represents a standardized data model for the travel and hospitality industry. The ERD is intentionally presented in a de-normalized fashion and with consideration for how data is stored in Adobe Experience Platform.
NOTE
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.
Fields indented under a parent field represent a child field, or sub-field, that belongs to the parent’s field group.
The most important fields for a given entity are highlighted in red.
All the properties that could be used to identify individual customers are marked as “identity”, with one of these properties marked as a “primary identity”.
Entity relationships are marked as non-dependent, since cookie-based events often cannot determine the person or individual who did the transaction.
NOTE
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.
Travel and hospitality use cases
The following table outlines the recommended classes and schema field groups for several common use cases for the travel and hospitality industry.
Use case
Recommended classes and field groups
Cross-sell dining and other resident attractions to in-market guests and guests with upcoming hotel reservations.
