Core concepts
- Identity namespace
- The context of an identifier, for example Email or CRM ID. Custom namespaces can be created.
- Primary identity
- The identifier used to store a record's profile fragment.
- Identity graph
- The set of linked identities for one person.
Designing an identity strategy step by step
- Inventory every identifier in each source and how reliably it identifies a person.
- Rank identifiers by uniqueness (for example CRM ID above email above device IDs).
- Decide which identifiers should link profiles and which should not.
- Exclude shared or low-quality values (shared devices, placeholder emails, test data).
- Test graphs with real sample data in a development sandbox before production.
Common identity problems
- Graph collapse: a shared identifier (such as a call-centre phone number) links many people into one graph.
- Missing links: authenticated events do not carry the CRM ID, so known and anonymous activity never join.
- Format mismatch: the same email arrives in different cases or hashing formats.
Review the current Adobe documentation for identity graph linking rules and limits before you design production graphs, as these capabilities evolve.
Who this guide is for
This guide is written for beginners, students and career switchers who want a clear mental model, and for developers, data engineers, implementation specialists, consultants, architects, marketers, agencies and enterprise teams who need practical, step-by-step detail they can apply on real projects.
Frequently asked questions
What is ECID?
The Experience Cloud ID is Adobe's device/browser identifier set by Web SDK and Mobile SDK. It is usually linked to known identifiers after login.
Can identity graphs merge the wrong people?
Yes, if shared or low-quality identifiers are allowed to link profiles. A deliberate identity strategy and testing prevent this.
Last updated: