You are here:
Identity Resolution Match Methods
Match rule methods determine how source data is transformed for comparison during matching. Changing the match method on a field typically changes the consolidation rate based on that field.
Match methods describe the precision with which data is matched during identity resolution. The anticipated consolidation rate is lower when precision matching is required. Selecting a less precise match method typically raises the consolidation rate, but can result in undesirable matches.
Up to five match methods are available for use in creating criteria for custom match rules. The match methods available for each object and field vary. Fuzzy match methods aren’t available for fields from the Account object.
- Exact
- Exact Normalized
- Fuzzy - High Precision
- Fuzzy - Medium Precision
- Fuzzy - Low Precision
You can refine custom match criteria further by allowing matches to be made between blank fields.
Exact Match Method
The Exact match method is available for all objects and fields. If this match method is used, values match regardless of case.
Because exact match is case-insensitive, these four source data values are an exact match:
- Maryanne
- maryanne
- MARYANNE
- MaryAnne
Exact Normalized Match Method
The Exact Normalized match method is available for specific fields for the Contact Point Email, Phone, and Address objects.
When this match method is selected, source data is transformed to address issues like trailing spaces, inconsistent formatting, special characters, and more.
| Object | Fields with Exact Normalized Match Method Support | Normalization Process |
|---|---|---|
| Individual |
|
|
| Contact Point Email |
|
|
| Contact Point Phone |
|
For data sources with phone number country codes, map the Phone Country Code field. |
| Contact Point Address |
|
|
These source data values are an exact normalized match:
| Source Values | Exact Normalized Email Address Field Value |
|---|---|
|
michellenoris@gmail.com |
These source data values are an exact normalized match:
| Source Values | Exact Normalized Formatted E164 Phone Number Field Value |
|---|---|
|
+16502779500 |
These source data values are an exact normalized match:
| Source Values | Exact Normalized Address Line 1 and Address Line 2 Field Values | Exact Normalized State Province and Country Field Values |
|---|---|---|
Source 1
Source 2
|
220 Laurier Ave W Ste 1000 | Ontario Canada |
Source 1
Source 2
|
Calle De José Abascal 56 | Madrid Spain |
Fuzzy Match Methods
The Fuzzy match methods are available for most fields.
If any of these match methods are used, matches are based on an Artificial Intelligence (AI) model trained with data from over 150 countries, 3 billion English words, and 20 million names. The AI model is built with the Bidirectional Encoder Representations from Transformers (BERT) Language Model to match common misspellings, diacritical marks, synonyms, and more. The AI model has a 0.7 confidence threshold.
To allow more control over the granularity of matching, three levels of precision are available: high, medium, and low precision.
| Precision Level | Description | Matching Values |
|---|---|---|
| Low Precision | Matches values with loose similarities. |
|
| Medium Precision | Matches values with the same initials, gender variants, shuffled names, and similar subnames. |
|
| High Precision | Matches values across nicknames, punctuation, international abbreviations, international alphabet characters, and cross-cultural spellings. |
|

