The Identity Backbone of Salesforce Data Cloud
- sfmcstories
- 6 days ago
- 5 min read
Understanding Party Identification, Individual, Unified Link Individual, and Unified Individual
Identity Resolution in Salesforce Data Cloud is often introduced through matching rules and reconciliation logic. These rules determine how records from different systems are connected to form unified customer profiles.
However, the identity resolution engine does not operate in isolation. It relies on a structured identity framework that organizes incoming records, standardizes identity attributes, and maintains traceability across systems.
Understanding this identity framework is essential for architects and practitioners implementing Salesforce Data Cloud. Once the underlying objects are understood, identity resolution becomes far easier to explain, troubleshoot, and design.
At the center of this framework are four important identity objects:
Party Identification
Individual
Unified Link Individual
Unified Individual
Together, these objects form the backbone of how Data Cloud creates a unified customer profile.
Why Identity Requires a Structured Model
Customer data rarely exists in a single system. Organizations typically manage identity data across CRM platforms, ecommerce systems, mobile applications, service tools, and marketing platforms.
Each system may store the same person in a slightly different way. Names may vary, identifiers may differ, and certain attributes may be missing in some systems.
Without a structured identity model, it becomes difficult to determine whether records across systems represent the same individual.
Salesforce Data Cloud addresses this challenge by organizing identity data into layered objects that separate:
raw identity inputs
normalized identity entities
unified customer profiles
This layered approach allows the platform to unify identities while still preserving traceability to the original source systems.
Party Identification – Capturing External Identity References
The identity journey in Data Cloud begins with Party Identification.
Party Identification objects store external identifiers associated with identity records coming from source systems. These identifiers may include:
CRM Contact IDs
Ecommerce Customer IDs
Loyalty Program Member IDs
External system identifiers
Instead of directly merging records, Data Cloud first stores these identifiers so that the platform can understand how different systems reference the same person.
It is important to understand that Party Identification does not represent every dataset in Data Cloud. It is specifically associated with identity-bearing records, such as:
contacts
customers
leads
account holders
Behavioral or interaction data, such as website clicks or mobile events, flows into other Data Model Objects rather than the Party Identification model.
To understand this in practice, consider a customer named Ananya Rao interacting with a retail company across multiple systems.
CRM System
Contact ID | Name | |
C1023 | Ananya Rao |
Ecommerce System
Customer ID | Name | |
EC455 | Ananya R. |
Mobile App
User ID | Name | |
APP998 | A. Rao |
When these records are ingested into Data Cloud, the system captures their identifiers through Party Identification records.
Party Identifier | Source System | Identifier |
P1 | CRM | C1023 |
P2 | Ecommerce | EC455 |
P3 | Mobile App | APP998 |
At this stage, the platform does not attempt to determine whether these records belong to the same person. Instead, it simply stores the identity references contributed by different systems.
Individual – The Canonical Person Entity
Once identity data enters the platform, the next layer of the identity model is the Individual object.
The Individual object represents a standardized person entity used during identity resolution. It aligns identity attributes so the platform can evaluate them consistently across systems.
Typical attributes used at this stage include:
first name and last name
email address
phone number
address information
In the Ananya Rao example, the system may create several Individual records representing each identity input.
Individual ID | Name | |
IND1 | Ananya Rao | |
IND2 | Ananya R. | |
IND3 | A. Rao |
These Individuals represent candidate identities that will be evaluated by the identity resolution engine.
Identity Resolution Rulesets determine whether these Individuals represent the same person.
Identity Resolution Rulesets – Determining Matches
Identity matching in Data Cloud is configured through Identity Resolution Rulesets.
These rulesets allow administrators to define how identities should be evaluated and unified. A ruleset typically includes two important components:
Matching Logic
Matching logic determines how the platform evaluates identifiers across records. Matching may rely on deterministic identifiers such as email or phone number, or it may evaluate combinations of attributes.
Reconciliation Rules
When multiple records contribute different attribute values, reconciliation rules determine which value should appear in the unified profile.
For example, the system may prioritize CRM values over ecommerce data, or select the most recent value across sources.
If the ruleset determines that the Individuals representing Ananya Rao belong to the same person, the system proceeds to create a unified identity.
Unified Individual – The Unified
Customer Profile
Once matching rules determine that multiple Individuals represent the same person, Data Cloud creates a Unified Individual.
The Unified Individual represents the consolidated customer identity created by the identity resolution process. Salesforce documentation often refers to this as the Unified Customer Profile.
For our example, the system would create a unified profile representing Ananya Rao.
Unified Individual ID | Name | |
U1001 | Ananya Rao |
This profile aggregates attributes from multiple contributing systems while applying reconciliation logic to determine which values appear in the final profile.
Unified Individuals become the primary customer identity used across Data Cloud capabilities such as segmentation, activation, analytics, and personalization.
Unified Link Individual – Maintaining Identity Traceability
While unified profiles provide a consolidated view of a customer, it is equally important to maintain transparency about how that profile was constructed.
This is the role of Unified Link Individual.
Unified Link Individual objects maintain the relationship between Individual records and the Unified Individual profile.
Link ID | Individual | Unified Individual |
L1 | IND1 | U1001 |
L2 | IND2 | U1001 |
L3 | IND3 | U1001 |
This structure preserves lineage back to the original identity records.
Importantly, Data Cloud does not physically merge records from different systems. Instead, it maintains links between identities while preserving their original structure.
This design provides several advantages:
identity decisions remain transparent
source records remain unchanged
identity rulesets can be reprocessed if needed
administrators can trace unified profiles back to source systems
This traceability is one of the key architectural principles of Data Cloud identity management.
Understanding the Identity Flow
When viewed together, these objects form a layered identity architecture.
The identity flow can be summarized as:
Source Records → Party Identification → Individual → Unified Link Individual → Unified Individual
Each layer has a specific purpose within the identity pipeline.
Party Identification stores external identifiers from source systems.
Individual represents the canonical person entity used during identity matching.
Identity Resolution Rulesets evaluate Individuals and determine which identities belong together.
Unified Individual represents the consolidated customer profile.
Unified Link Individual preserves the relationships between source records and unified profiles.
Final Thoughts
Identity resolution in Salesforce Data Cloud is built on a carefully designed identity architecture that separates raw identity inputs from unified customer profiles.
By organizing identity data through Party Identification, Individual, Unified Link Individual, and Unified Individual objects, the platform can unify identities while preserving transparency and traceability.
For architects and practitioners working with Data Cloud, understanding this identity backbone provides deeper insight into how unified customer profiles are constructed and how identity decisions can be explained, validated, and governed.
Comments