You are here:
Standard Matching Rule for Leads on Accounts
The standard matching rule for leads on accounts is activated with the purchase of Account Engagement Advanced or Premium edition. The rule populates the content of the Matched Leads component using a matching equation and matching criteria. By reducing redundant data, the rule and the component help you work toward complying with data protection and privacy regulations.
Matching Equation
(Company AND Street)
OR (Company AND City AND State)
OR (Company AND ZIP/Postal Code)
OR (Company AND Phone)
OR (Website)
Matching Criteria
| Account Field | Lead Field | Matching Algorithms | Scoring Method | Threshold | Blank Fields | Special Handling |
|---|---|---|---|---|---|---|
| Account Name | Company | Acronym Edit Distance Exact |
Maximum | 70 | Don’t match | Removes words such as Inc and Corp before comparing fields. Also, company names are normalized. For example, 1st National Bank is normalized to First National Bank. |
| Phone | Phone | Exact | Weighted Average | 80 | Don’t match on all sections except Area Code, which ignores blank fields | Phone numbers are broken into sections and compared by those sections. Each section has its own matching method and match score. The section scores are weighted to come up with one score for the field. This process works best with North American data.
For example, suppose that these two phone numbers are being compared: 1-415-555-1234 and 1-415-555-5678. All sections match exactly except the last 4 digits, so the field has a match score of 90. The field is considered a match because the score exceeds the threshold of 80. |
| Billing Street | Street | Edit Distance Exact |
Weighted Average | 80 | Don’t match | Addresses are broken into sections and compared by those sections. Each section has its own matching method and match score. The section scores are weighted to come up with one score for the field. This process works best with North American data.
For example, suppose that these two billing streets are being compared: 123 Market Street, Suite 100, and 123 Market Drive, Suite 300. Because only the street number and street name match, the field has a match score of 70. The field isn’t considered a match because the score is below the threshold of 80. |
| Billing ZIP/Postal Code | ZIP/Postal Code | Exact | Weighted Average | 80 | Don’t match | ZIP codes are broken into sections and compared by those sections. Each section has its own matching method and match score. The section scores are weighted to come up with one score for the field.
For example, suppose that these two ZIP codes are being compared: 94104-1001 and 94104. Because only the first five digits match, the field has a match score of 90. The field is considered a match because the score exceeds the threshold of 80. |
| Billing City | City | Edit Distance Exact |
Maximum | 85 | Don’t match | |
| Website | Exact | Maximum | 100 | Don’t match | The domain in the email suffix in the lead record is extracted and compared to the website field in the account record. Email addresses ending in widely used domains such as gmail.com and yahoo.com are ignored. |
If the account Website field has no value, and at least one contact is related to the account, the following matching criteria are also applied.
| Related Contact Field | Lead Field | Matching Algorithms | Scoring Method | Threshold | Blank Fields | Special Handling |
|---|---|---|---|---|---|---|
| Exact | Maximum | 100 | Don’t match | The domain in the lead’s email suffix is extracted and compared to email suffixes in the contact records with the 20 most recent system timestamps. Among those 20 records, the rule then identifies the 5 most frequently occurring email suffixes. Finally, the rule identifies as possible matches any leads that share those suffixes. Email addresses ending in widely used domains such as gmail.com and yahoo.com are ignored. |

