Can I Use fuzzy comparisons in my Tiebreakers?
Whenever LeanData finds more than one possible Account match, tiebreaker rules are used to determine the one best match.
While LeanData provides default tiebreaker rules, some customers may opt to use custom rules to meet their business requirements and may need to use more advanced fuzzy logic that the default tiebreakers do not incorporate.
This FAQ will describe some advanced operator logic that you can use to make fuzzy comparisons between domain and company name fields.
LeanData utilizes standard email and website fields to determine which domains to associate with a Lead and an Account. If you would like to create a tiebreaker rule that prioritizes Accounts where the Account domains match the Lead domains, you can use the condition: Website EQUALS Website.
This condition will implicitly compare domains from the Account with domains from the Lead. This includes any domains that are associated with either record via email fields.
Example: Mike is the LeanData admin for EdenPoint Development. Since his Salesforce instance includes many Accounts with very similar names, he needs to ensure that LeanData prioritizes Lead-to-Account matches with the same email or website domains. In his Tagging Tiebreakers, he includes the condition Website EQUALS Website as the first tiebreaker rule to ensure LeanData first prioritizes Accounts with the same domain as the incoming Lead.
If you would like the tiebreaker condition to strictly compare the Lead Website field with the Account Website field, without considering email domains, you can instead use the condition Website STARTS WITH Website. This will ensure that LeanData looks for a strict match between the Lead and Account website fields. This comparison may be used in both your filter rules and your tiebreaker rules.
Company Name Comparisons
If you would like to use a close match between the Account Name field and the Company field on the Lead as a tiebreaker condition, you can use the condition Account Name EQUALS Company. This specific condition will not require exact match between these fields, but instead allows for a degree of fuzzy matching to determine the best match.
Example: Lucas is the LeanData admin for OpenLane Software. Since they frequently sell into multiple subsidiaries of large multinational companies, they have many Accounts with identical domains but represent different Accounts. He would like to ensure that LeanData prioritizes Lead-to-Account matches with the closest Company-to-Account Name match, but allow for some variance in how Company names might be entered. In his Tagging Tiebreakers, he includes the condition Account Name EQUALS Company as the first tiebreaker rule to ensure LeanData first prioritizes Accounts with a fuzzy Account Name match.
If you would like the condition to look for an exact match between the Lead Company field and the Account Name field, you can instead use the condition Account Name STARTS WITH Company. This will ensure that LeanData looks for an exact (non-fuzzy) match between the Lead Company field and Account Name field. This comparison may be used in both your filter rules and in your tiebreaker rules.
Street Address Comparisons
If you would like to use a close match between the Account Billing Street Address field and the Street Address field on the Lead as a tiebreaker condition, you can use the condition Billing Street Address EQUALS Street. Using Equals will cause LeanData to perform fuzzy matching on street address fields.
Example: Kevin is the LeanData Admin for DEI Inc. Kevin frequently sees records not matched because of small issues like a street address that have Drive versus Dr. Although the two address fields represent the same location, but are not the same fields character-for-character (“Dr.” versus “Drive”), the equals operator will consider them a match for the tiebreaker.