Error Library / AEP

Can't enable a schema for Real-Time Customer Profile: no primary identity

What you seeThe Profile toggle is unavailable, or enabling it is refused, for a schema without a primary identity

Real-Time Customer Profile has to know which field identifies a person before it can build profiles from a schema. A record-based (individual profile) schema needs a primary identity field before it can be enabled for Profile.

Why it happens

  • The schema has fields like email or CRM id, but none of them is marked as an identity with a namespace.
  • An identity exists but none is set as primary.

How to fix it

  1. Pick the field that most reliably identifies a person in this source (often a CRM id or email).
  2. Mark it as an identity, choose its namespace (Email, CRMID, or a custom one) and set it as primary.
  3. Enable the schema for Profile, then enable each dataset that should feed Profile.

Before and after

Fails
Schema with personalEmail.address as a plain string field
Works
personalEmail.address marked as identity, namespace Email, primary = true

Common questions

Can I change the primary identity later?

Changes to Profile-enabled schemas are restricted, so choose carefully before enabling Profile.

Practise the fix

Build the Customer Profile

Reproduce this error in your own AEP practice workspace, fix it, and earn a verifiable credential for the skills involved: XDM schema design, Identity descriptors, Real-Time Customer Profile enablement, Dataset configuration.

See the Lab plan

Related errors

Data ingested but not in Real-Time Customer Profile: dataset not enabled for Profile

Identity resolution: the same customer shows up as separate profiles

AdsBot is an independent training provider, not affiliated with Adobe. Behaviour can differ between ingestion methods and product versions; always test with a small batch first.