A company is looking to model their data architecture in Adobe Real-Time CDP that includes customer transactions across multiple platforms. What is the approach to define identity graph for a customer in Adobe Real-Time CDP to track a customer's activities across multiple platforms?

To create a unified customer profile across multiple platforms, a common identity must be used to link the disparate data. Defining common identity namespaces (e.g., a hashed email address, a loyalty ID) that are used across these platforms allows the Adobe Experience Platform Identity Service to recognize that the activities belong to the same individual. This process stitches the identities together into a single identity graph, forming the basis of the real-time customer profile.

A. Merge policies resolve attribute conflicts within a single profile; they do not define how different identities are linked together in the first place.
B. Using unique identity namespaces for each platform would keep the profiles separate and prevent the system from understanding they belong to the same person.

1. Adobe Experience Platform Documentation. (2023). Identity Service overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/identity/home.html?lang=en. The overview states, "Identity Service helps you gain a better view of your customers and their behavior by bridging identities across devices and systems".

2. Adobe Experience Platform Documentation. (2023). Identity namespaces overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/identity/namespaces.html?lang=en. This document explains that namespaces are a component of an identity and are used to provide context. Using a common namespace across sources is fundamental to stitching.