---
schema_version: "1"
id: 31acb957cbf932679b913fb1825e5f4c41c4b75431bab6d5e76da2683c268ac4
title: Standard Matching Rule for Leads on Accounts
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/matching_rules_standard_leads_on_accounts_rule.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.matching_rules_standard_leads_on_accounts_rule.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 60bde2e6390ee3a8c3217cd961395f1cb11be7d411857a700b0eca0ce6e3152b
description: 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.
products:
  - Sales
  - Sales Enablement
release: "264"
---
# 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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-data_quality-264-0-0-production-enus/abf88105-66d5-422e-983e-0592556338d7/images/icon_note.png)

Note The standard matching rule for leads on accounts works best on accounts with values in the Website field or the Account Name, Phone, Address, and City fields.

## 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:8.416547788873038%">
          <col style="width:14.265335235378032%">
          <col style="width:9.843081312410842%">
          <col style="width:10.271041369472183%">
          <col style="width:7.417974322396577%">
          <col style="width:8.416547788873038%">
          <col style="width:41.36947218259629%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e100">Account Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e102">Lead Field</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e104">Matching Algorithms</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e106">Scoring Method</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e108">Threshold</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e110">Blank Fields </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d5302e112">Special Handling</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Account Name</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">Company</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">
              <p>Acronym </p>
              <p>Edit Distance</p>
              <p style="margin-bottom:0;">Exact</p>
            </td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Maximum</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">70</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">Removes words such as <samp>Inc</samp> and
              <samp>Corp</samp> before comparing fields. Also, company names are
              normalized. For example, <samp>1st National Bank</samp> is normalized to
              <samp>First National Bank</samp>.
            </td>
          </tr>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Phone</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">Phone</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">Exact</td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Weighted Average</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">80</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match on all sections except Area Code, which ignores blank
              fields</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">
              <p>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.</p>
              <ul>
                <li>International code (Exact, 10% of field’s match score)</li>
                <li>Area code (Exact, 50% of field’s match score)</li>
                <li>Next 3 digits (Exact, 30% of field’s match score</li>
                <li>Last 4 digits (Exact, 10% of field’s match score)</li>
              </ul>
              <p>For example, suppose that these two phone numbers are being compared:
                <samp>1-415-555-1234</samp> and
                <samp>1-415-555-5678</samp>.
              </p>
              <p style="margin-bottom:0;">All sections match exactly
                <em>except</em> 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.
              </p>
            </td>
          </tr>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Billing Street</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">Street</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">
              <p>Edit Distance</p>
              <p style="margin-bottom:0;">Exact</p>
            </td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Weighted Average</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">80</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">
              <p>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.</p>
              <ul>
                <li>Street Number (Exact, 20% of field’s match score)</li>
                <li>Street Name (Edit Distance, 50% of field’s match score)</li>
                <li>Street Suffix (Exact, 15% of field’s match score)</li>
                <li>Suite Number (Exact, 15% of field’s match score)</li>
              </ul>
              <p>For example, suppose that these two billing streets are being compared:
                <samp>123 Market Street, Suite 100</samp>, and <samp>123 Market
                  Drive, Suite 300</samp>.
              </p>
              <p style="margin-bottom:0;">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.</p>
            </td>
          </tr>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Billing ZIP/Postal Code</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">ZIP/Postal Code</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">Exact</td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Weighted Average</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">80</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">
              <p>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. </p>
              <ul>
                <li>First 5 digits (Exact, 90% of field’s match score)</li>
                <li>Next 4 digits (Exact, 10% of field’s match score)</li>
              </ul>
              <p>For example, suppose that these two ZIP codes are being compared: 94104-1001 and
                94104.</p>
              <p style="margin-bottom:0;">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.</p>
            </td>
          </tr>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Billing City</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">City</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">
              <p>Edit Distance</p>
              <p style="margin-bottom:0;">Exact</p>
            </td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Maximum</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">85</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">&nbsp;</td>
          </tr>
          <tr class="">
            <td data-label="Account Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e100 ">Website</td>
            <td data-label="Lead Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e102 ">Email</td>
            <td data-label="Matching Algorithms" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e104 ">Exact</td>
            <td data-label="Scoring Method" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e106 ">Maximum</td>
            <td data-label="Threshold" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e108 ">100</td>
            <td data-label="Blank Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e110 ">Don’t match</td>
            <td data-label="Special Handling" class="slds-cell-wrap" style="vertical-align:top;" headers="d5302e112 ">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.</td>
          </tr>
        </tbody>
      </table>

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 |
| --- | --- | --- | --- | --- | --- | --- |
| Email | Email | 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. |

#### See Also

- [Account Engagement Pricing](https://www.pardot.com/pricing/)
- [View and Convert Leads on an Account](https://help.salesforce.com/s/articleView?id=sales.accounts_matched_leads_view.htm&type=5&language=en_US)
- [Matching Criteria in Matching Rules](https://help.salesforce.com/s/articleView?id=sales.matching_rule_matching_criteria.htm&release=264.0.0&type=5 "A matching rule applies criteria to determine how closely a field on a new or edited record matches the same field on an existing record. Standard matching rules include predefined criteria. When you create a custom matching rule, you define the criteria.")
- [How Match Keys Are Generated and Used in Matching Rules](https://help.salesforce.com/s/articleView?id=sales.matching_rules_match_key_process.htm&release=264.0.0&type=5 "When a matching rule runs, it applies one or more match key formulas before applying a comprehensive matching equation. Match keys help to increase the performance of duplicate rules through a preliminary comparison that narrows the matches to the 100 most likely duplicate records. Then the rule applies the matching equation only to those likely matches.")