---
schema_version: "1"
id: 2fd6114938cb84ef4484f27f831b18d2263b5a5a9cb85c1994f373e58cedf0eb
title: Define Match Rules for Identity Resolution and Relate Separate Individuals
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_omni_match.md
canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_omni_match.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 22c4d235664cfab1004ce36eeac75eca3806ace8c866b250a9e910dd8a85398b
description: Let’s review the steps for defining match rules for Identity Resolution and relating separate Individuals in Data 360.
products:
  - Data 360
release: "264"
---
# Define Match Rules for Identity Resolution and Relate Separate Individuals

Let’s review the steps for defining match rules for Identity Resolution and relating separate Individuals in Data 360.

Relate your separate Individuals to a Unified Individual using [Identity Resolution](https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution.htm&release=264.0.0&type=5 "Identity resolution is the processing engine that generates unified profiles from source profile data stored in Data 360. Unified profiles act as a system of reference to unlock our source data. Understand how and when source profiles are processed and what you can do with unified profile output."). This example assumes that you can externally collect FirstName, LastName, EmailAddress, and/or PhoneNumber for each channel SubscriberKey. You then import the external data from three different systems, one for each channel, and map it accordingly. The imported SubscriberKey is linked to the Individual ID in Data 360. Using these match rules, Identity Resolution relates the separate Individuals, representing a person’s various Marketing Cloud Engagement SubscriberKeys, to a single Unified Individual.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)

Note Your company’s data mapping, identity resolution strategy, and rules can differ. Learn more about [match rules](https://help.salesforce.com/s/articleView?id=data.c360_a_match_rules_criteria.htm&release=264.0.0&type=5 "Identity resolution provides out-of-the-box, default match rules for different types of matching. Use custom match rules to resolve use cases that aren’t covered by default rules. Developing balanced, effective sets of match rules across different types of criteria improves consolidation rates for individuals and accounts.") and Unified Individual [Considerations and Best Practices](https://help.salesforce.com/s/articleView?id=data.c360_a_omni_best_practices.htm&release=264.0.0&type=5 "There are important aspects and trade-offs to consider before implementing this solution. This guide is just one example of how to enable an omnichannel experience for your customers. For example, instead of separate single-channel journeys, users can create seamless customer experiences by using Data Cloud to orchestrate one journey with all Email, SMS, and MobilePush activities together.").

1. In Data 360, go to the Identity Resolution app.
2. Click **New**.
3. Set the Primary Data Model Object to Individual and enter a Ruleset ID.
4. Click **Next**.
5. Enter a ruleset name and the description.
6. Click **Save**.
7. In the Match Rules section, click **Configure**.
8. For Match Rule 1, click **Configure**.
9. Select **Fuzzy Name and Normalized Phone** and click **Next**.
10. Review the default rules.
11. Click **Add Match Rule**.
12. Select **Fuzzy Name and Normalized Email** and click **Next**.
13. Select **Custom Rule** and click **Next**.
14. [Match on Mobile SDK Shared Identifier](https://help.salesforce.com/s/articleView?id=data.c360_a_identity_resolution_unify_partyidentifier.htm&release=264.0.0&type=5 "Party identifier refers to the exact match of the Identification Number, Identification Name, and Party Identification Type fields in the Party Identification object. This type of match is useful for matching unique identifiers, such as government ID, first-party cookies, external MDM systems, and vendor-specific IDs.").
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png)
    
    Note Customers must implement Mobile SDK to include both Data 360 and MobilePush modules.
15. Enter a name for the Match Rule and click **Next**.
16. Read the overview and click **Save**.