Key Components

The key components here are:

• Parent Entity: This is the central entity representing the customer profile. It contains foundational information like demographic details (for example, name, age, address) and personal data. The parent entity serves as the core identifier for each customer, ensuring all related data is tied to the correct profile. This is the main record, like a customer’s profile. In Data Model, you can find a default Parent entity, which is Profile.

• Child Entity: These entities store specific transactional or interaction-based information linked to the parent (customer profile). Examples include purchase history, customer interactions, cases, and appointments. Each child entity focuses on a particular type of data and is associated with the parent entity through Identity Resolution, which ensures that all related activities and transactions are connected to the correct customer. In Data Model, the default child entity is Interaction. You can link multiple child records to a single parent record, creating a one-to-many relationship. Each child record is connected to only one parent, but one parent can have many child records.

• Unique Identifier: Unique identifiers act as the secret code that keeps the customer profiles distinct. Each unique identifier is a special trait that sets a profile apart from the rest, ensuring there are no mix-ups in the data. Each customer profile has its special identifier, ensuring no mix-ups in the data crowd. You can also designate a Custom Profile Attribute as a unique identifier. However, each custom entity can have only one unique ID.