For a schema's data to be ingested and used within the Real-Time Customer Profile, the schema must first be enabled for Profile. A mandatory requirement of this enablement process is to designate one of the identity fields within the schema as the primary identity. This primary identity serves as the main key that Adobe Experience Platform uses to stitch together different data fragments from various sources into a single, unified customer profile. Without a designated primary identity, the system cannot uniquely identify and merge records for an individual, making the data unusable for profile creation.

B. Secondary identity: While useful for profile stitching, designating a secondary identity is optional and not a mandatory requirement for enabling a schema for Profile.

C. Identity class: This is not a configurable setting on a schema. An identity field is defined by an identity namespace (e.g., Email, ECID), not an "identity class."

1. Adobe Experience Platform Documentation

Schemas User Guide

"Enable the schema for use in Real-Time Customer Profile." This official guide explicitly states: "To enable a schema for use in Profile

it must have a primary identity specified. The primary identity is a unique identifier that allows data from different sources to be stitched together to form a single profile view."

Source: Adobe Experience League

Schemas User Guide. Navigate to the section on creating and editing schemas in the UI.

2. Adobe Experience Platform Documentation

Real-Time Customer Profile Guide

"Profile overview." This document details the fundamentals of profile creation

explaining: "When data is ingested into Experience Platform

Real-Time Customer Profile checks to see if a profile fragment already exists for the primary identity provided in the record. If no fragment exists

it creates a new one." This highlights the foundational role of the primary identity.

Source: Adobe Experience League

Real-Time Customer Profile Guide.

3. Adobe Experience Platform Documentation

Identity Service Guide

"Identities." This resource clarifies the roles of different identities: "Each schema that is enabled for Profile must have one field designated as a primary identity. Real-Time Customer Profile uses this identity to stitch together data from different sources to create a single

unified profile for each individual."

Source: Adobe Experience League

Identity Service Guide.