Does a primary identity need to be selected within a schema before it can be enabled for Real Time CDP?

The primary identity in a schema plays a critical role in enabling the schema for the Real-Time Customer Data Platform (CDP) in Adobe Experience Platform. A primary identity serves as the main identifier for a customer profile, ensuring that all related data sources and attributes can be accurately linked and associated with that specific customer.

Selecting a primary identity is essential because it establishes a cohesive and unified view of each customer, allowing for more effective personalization and engagement strategies within the Real-Time CDP. By choosing a primary identity, you ensure that the system can properly merge and manage multiple identities or data points that may exist for the same individual across various sources.

Without a selected primary identity, the schema would not function optimally within the CDP, leading to fragmented data views and inefficiencies in real-time data processing and customer engagement initiatives. Thus, a primary identity must be established prior to enabling the schema for Real-Time CDP to guarantee a robust and integrated customer view.