You may notice that certain name variations are not detected when utilizing First Name with Fuzzy Logic in Salesforce Duplicate Management Matching Rules, even when they exceed the Jaro-Winkler threshold. Please see the examples below.
Matching Rule (Contact): (Contact: FirstName FUZZY: FIRST NAME MatchBlank = FALSE) AND (Contact: LastName FUZZY: LAST NAME MatchBlank = FALSE) AND (Contact: Email EXACT MatchBlank = FALSE)
Example records where the duplicate rule IS detected:
| First Name | Last Name | Jaro-Winkler Score (Fuzzy: First Name) | |
| Jon | Sputenberger | jsputen@gmail.com | Base record (no score) |
| Jonathan | Sputenberger | jsputen@gmail.com | 85 |
| Sam | Smith | ssmith@gmail.com | Base record (no score) |
| Samuel | Smith | ssmith@gmail.com | 88 |
| Dan | Steele | dsteele@gmail.com | Base record (no score) |
| Daniel | Steele | dsteele@gmail.com | 88 |
Example records where the duplicate rule is NOT detected:
| First Name | Last Name | Jaro-Winkler Score (Fuzzy: First Name) | |
| Raj | Perumal | r_perumal@ducks.ca | Base record (no score) |
| Rajesh | Perumal | r_perumal@ducks.ca | 88 |
| Jay | Aloclek | jaloclek@gmail.com | Base record (no score) |
| Jayson | Aloclek | jaloclek@gmail.com | 88 |
| Sal | Brenner | sbrenner@gmail.com | Base record (no score) |
| Salima | Brenner | sbrenner@gmail.com | 88 |
When using Fuzzy Logic with First Name in a Salesforce Duplicate Management Matching Rule, not all name variations that exceed the Jaro-Winkler threshold will trigger a duplicate match. This occurs because fuzzy logic relies on pre-captured name patterns on the matching server — the detection is not based solely on the numeric score.
As you can see in the examples above, all of these records exceed the Jaro-Winkler threshold. However, only half of these records will detect the duplicates based on the above matching rule. The reason for this is due to scenarios where expected matches will return a negative result if the name variation pattern was not already captured on the matching server. Fuzzy logic is not meant to be exact.
Ideally, additional matching criteria should be put in place, such as address fields. This ensures that duplicate matches are returned from the server when utilizing fuzzy logic.
000389625

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.