Loading

Data 360: Overview of Identity Resolution Using Party Identification

Publiseringsdato: Aug 6, 2026
Beskrivelse

This article explains how identity resolution works when you use the Party Identification DMO in Data 360.
This mechanism applies to cases where you consolidate customer profiles using a custom identifier — such as a membership number — rather than a standard contact point field.

Løsning

Overview of Identity Resolution Using Party Identification

What Is Party Identification?

Party Identification lets you identify and link (unify) data as a single entity using a "custom identifier" other than standard fields such as Individual or Contact Point.

Data 360 identity resolution typically relies on email addresses and phone numbers. However, some business requirements call for unifying data that doesn't include those fields, or that requires a stricter identifier. Use the Party Identification DMO to unify profiles keyed on your own dataset. Examples include:

  • DUNS Number: an identifier assigned and managed by a business-code administration system
  • Membership ID: a fitness club membership number, a supermarket membership number, and similar identifiers
  • National ID: a passport number, driver's license number, My Number, and similar identifiers

Points to Consider When Using Party Identification for Identity Resolution

To perform accurate ID unification with the Party Identification DMO, understand the following technical points and constraints.

1. Exact Match on Three Fields (the Unification Key)

During identity resolution, records unify into the same entity (an individual, an organization, etc.) only when the values of the following three fields match exactly:

  • Identification Number: the actual identification number (for example, a passport number or a membership number)
  • Identification Name: the name of the identification information (for example, Passport or MemberCard)
  • Party Identification Type: the type of identification information (for example, National ID or Privately Issued ID)

2. Populate the Formula Fields

For Party Identification-based identity resolution to work correctly, the Identification Name and Party Identification Type fields — in addition to Identification Number — are required. However, most source data doesn't have columns that hold these values.

Important: You must create formula fields on the Data Lake Object (DLO) and output or map a fixed value for each data source.

3. Uniqueness of the Party Identification ID

The Party Identification ID uniquely identifies a record within the DMO. If this ID is duplicated, the identity resolution process excludes the record, and it may not unify correctly. Design your data preparation so this ID is always unique.

4. Duplicate Exclusion Logic

Among records from the same data source, any records where Party Identification Id, Data Source, and Data Source Object are all identical are treated as duplicates. In this case, only the first record processed is included in identity resolution — the rest are excluded.

Case Study: Identity Resolution Using the Party Identification DMO

Review the unification logic for Party Identification with concrete case studies.

Case 1: Unification by Matching All Three Fields
If you ingest the following four records, what unified profile (Unified Individual) results?

 

Record #PartyParty Identification TypeIdentification NameIdentification NumberParty Identification Id
1123PersonIdentifierPassportNumberP5555PassportNumber-123-P5555
2234PersonIdentifierPassportNumberP4444PassportNumber-234-P4444
3345PersonIdentifierPassportNumberP5555PassportNumber-345-P5555
4456P5555P5555P5555P5555-456-P5555

 

Result: 3 unified profiles

Records 1 and 3 unify into a single profile, because all three fields — Party Identification Type, Identification Name, and Identification Number — match exactly. So the final count is 3 profiles.

Case 2: Unification Across Multiple Sources, with Duplicate Exclusion
This more complex case ingests 5 records from different data sources.
 

Record #

Identification Number

Identification Name

Party Identification Type

Data Source Object

Data Source

Party Identification

Id

Party

1

DUNS001

D-U-N-S Number

Account Identifier

WebSDK_Identity_12345678

WebSDK_Identity_12345678

12345678

1a2b3c4d5e6f7g8h

2

123456781234

D-U-N-S Number

Account Identifier

Account

Salesforce_Home

001XXXXXXXXXXXXXXX

001XXXXXXXXXXXXXXX

3

123456781234

D-U-N-S Number

Account Identifier

s3://bucketeer-1234/DataCloud/sample.csv

Amazon S3

DG001

DG001

4

DUNS002

XXXXX Account Id

Account Identifier

s3://bucketeer-1234/DataCloud/sample.csv

Amazon S3

DG001

DG001

5

DUNS001

D-U-N-S Number

Account Identifier

WebSDK_Identity_1A2B3C4D

WebSDK_Identity_1A2B3C4D

1a2b3c4d

1a2b3c4d

 
Apply the unification logic:
  • Duplicate exclusion: Records 3 and 4 share the same data source (Amazon S3) and the same Party Identification Id (DG001), so record 4 is excluded from identity resolution.
  • Unification A: Records 1 and 5 unify because they match on all three fields (Party Identification Type, Identification Name, and Identification Number).
  • Unification B: Records 2 and 3 unify because they match on all three fields (Party Identification Type, Identification Name, and Identification Number).

Result: 2 unified profiles
In the end, the profiles consolidate into two unified profiles, "A" and "B."
Knowledge-artikkelnummer

005317085

 
Laster
Salesforce Help | Article