Loading

Fuzzy match on First Name doesn't detect the expected duplicate

Data pubblicazione: Oct 13, 2022
Descrizione
You may notice that certain name variations are not detected when utilizing First Name with Fuzzy Logic, even when they exceed the Jaro-Winkler threshold. Please see example 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 rule is detected:
First NameLast NameEmailJaro-Winkler Score (Fuzzy: First Name)
JonSputenbergerjsputen@gmail.com 
JonathanSputenbergerjsputen@gmail.com85
 
SamSmithssmith@gmail.com 
SamuelSmithssmith@gmail.com88
 
DanSteeledsteele@gmail.com 
DanielSteeledsteele@gmail.com88
 
Example records where the rule is NOT detected:
First NameLast NameEmailJaro-Winkler Score (Fuzzy: First Name)
RajPerumalr_perumal@ducks.ca 
RajeshPerumalr_perumal@ducks.ca88
 
JayAloclekjaloclek@gmail.com 
JaysonAloclekjaloclek@gmail.com88
 
SalBrennersbrenner@gmail.com 
SalimaBrennersbrenner@gmail.com88
Risoluzione
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; If it isn't a pattern that was 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. This ensures that duplicate matches are returned from the server when utilizing fuzzy logic.

Related Documentation: Matching Methods Used in Matching Rules
Numero articolo Knowledge

000389625

 
Caricamento
Salesforce Help | Article