The following entity relationship diagram (ERD) represents a standardized data model for the banking, financial services, and insurance (BFSI) industry. The ERD is intentionally presented in a de-normalized fashion and with consideration for how data is stored in Adobe Experience Platform.
NOTA
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. 🔗🔗
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.
The following table outlines the recommended classes and schema field groups for several common financial use cases.
Caso de uso
Recommended classes and field groups
Drive personalization at scale for preferred segments through omnichannel reporting insights and automating journeys to increase enrollment to a preferred rewards program.
Drive new revenue opportunities by using insights gained from cross-channel behavior analysis, identifying patterns of product usage that could lead to new product offers.
