You are here:
Configure Identity Resolution Match Rules
Specify how identity resolution identifies matching records in Data 360.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| Permission Sets Needed | |
|---|---|
| To configure match rules | Permission set:
|
To create or edit match rules:
- Go to the record homepage of your identity resolution ruleset.
- In Match Rules, click Configure or Edit.
-
Click Add Match Rule.
Select a default match rule or click Custom Rule to create your own. To create a match rule based on party identifier or an external identity link, create a custom rule.
- Click Next.
-
Edit, add, or delete criteria for your match rule. To create a match rule based on
party identifier, select the Party Identification data model object and the Identification
Number field. To create a match rule based on an external identity link, select the
Identity Match data model object and the Identity Match Type field.
Tip Matching on a single contact point isn’t recommended to avoid over grouping, except for unique external identifiers like a party identifier. Matching on single data point, such as phone number or email alone, could mix household members with a shared contact point into a single unified profile. By adding more match criteria, like name or email, you’re less likely to mix household members into a single unified profile.
Note Each ruleset must have at least one match rule. You can't delete the last match rule from a ruleset. To stop a ruleset from running, delete it. - To set up cross-object matching, case sensitive matching, or allow blank values to match, click Configure to access the advanced criteria settings. For cross-object matching, the object you want to match to must be modeled properly.
- Name your match rule with 80 characters or less.
- Click Save.
- Configure Real-Time Matching in Data 360
You can configure any ruleset for real-time matching after its first ruleset run is completed by creating a real-time data graph based on the ruleset’s output unified profile data model object.
Did this article solve your issue?
Let us know so we can improve!

