To successfully track a customer across multiple platforms (e.g., Web, Mobile App, and POS), theIdentity Servicemust be able to recognize that a value in one system refers to the same person as a value in another. This is achieved by definingcommon identity namespaces.
For example, if the Web platform uses an email address to identify a user and the Mobile App also uses an email address, both should map to the standard "Email" namespace. If the platforms used different namespaces for the same data type (e.g., "Web_Email" vs "App_Email"), the Identity Service would treat them as unrelated entities, and theIdentity Graphwould fail to "stitch" the profiles together.
Using common namespaces allows the platform to build a comprehensive graph where various IDs (like a CRM ID, an Email, and an ECID) act as bridge points. When a user logs in on the web with an email and later logs into the app with that same email, the common namespace enables the Real-Time Customer Profile to merge their web browsing behavior with their app activity. Option B would result in fragmented, siloed profiles, defeating the purpose of a CDP. Option A refers toMerge Policies, which govern how data is prioritized during conflicts, but does not define how identities are linked in the graph.
