# Multi-field Matching – Definition, FAQs & How Dedupely Helps

> Multi-field matching explained: how combining fields in one rule cuts false matches, why it misses more duplicates, and how to mix methods across fields.

- URL: https://dedupe.ly/glossary/multi-field-matching
- Section: glossary
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

[Glossary](https://dedupe.ly/glossary)
Multi-field Matching

## Multi-field Matching

Multi-field matching is a way of finding duplicate records by combining several fields in one matching rule, so two records count as duplicates only when every field in the rule meets its criteria. A rule on first name + last name + company, for example, pairs two contacts only when all three agree.
Each field can use its own comparison method, such as exact matching on email and similar matching on name. Adding fields makes a rule more precise, because a value shared in one field no longer pairs unrelated records on its own. It also makes the rule stricter, because one field that differs breaks the match. That trade-off between false matches and missed duplicates is why multi-field matching often relies on a few strong fields, with several rules side by side to cover different combinations.
See how Dedupely matches on multiple fields in your CRM
[Try for free](https://v2.app.dedupe.ly/signup)
[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)
Overview
Multi-field matching compares several fields in one rule, such as first name, last name and company, and pairs two records only when every field agrees. Each field added cuts false matches but misses more duplicates, so rules often combine a few strong fields and mix strict and looser methods.
On this page
- What Is Multi-field Matching?
- How Multi-field Matching Works
-
Why Multi-field Matching Matters for CRM Teams
-
Getting Started With Multi-field Matching
- Key Takeaways: Multi-field Matching
-
Frequently Asked Questions About Multi-field Matching
- Related Terms and Concepts
See how Dedupely matches on multiple fields in your CRM
[Try for free](https://v2.app.dedupe.ly/signup)
[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)

### What Is Multi-field Matching?

Multi-field matching, also called multi-field rules, combined matching rules or matching on multiple matching criteria, is the part of record matching that decides which fields have to agree before two records are paired. One field is rarely enough on its own. Last name alone pairs every Smith in the database, and even an email address can be shared, such as a front-desk inbox used by a whole office.
Take three contacts: "Jon Smith, Acme, jon@acme.com," "Jon Smith, Globex, jsmith@globex.com" and "Jonathan Smith, Acme, jon@acme.com." A rule on first name + last name pairs the first two, which are different people, and misses the third. A rule on last name + company + email pairs the first and third, and leaves the Globex contact alone. Adding first name to that rule would break the pair again, because "Jon" and "Jonathan" differ, unless first name is compared with a method that allows for nicknames.
There are two common ways to combine fields. In rule-based matching, every field in a rule has to meet its criteria. Its strength is that each rule is easy to read, and its results are easy to predict. In weighted scoring, each field adds points, and records pair when the total passes a threshold. Its strength is that a strong field can make up for a weak one. Both apply to every object a CRM stores: contacts in HubSpot and Google Contacts, accounts in Salesforce, organizations in Pipedrive and leads in Close.
Resources:
-
[Match Options](https://dedupe.ly/knowledge-base/match-options) (KB)
- [What is a duplicate?](https://dedupe.ly/blog/what-is-a-duplicate)

### How Multi-field Matching Works

Multi-field matching turns a description of a duplicate into a matching rule with multiple fields that a system can run, one field at a time:
- **Pick an anchor field.** Start from a field that points to one person or company, such as an email address, a phone number or a customer ID. It carries most of the rule's precision.
- **Add supporting fields.** Fields such as last name, company or city narrow the match. Each one removes some false matches, and each one is another place where a real duplicate can fail to match.
- **Choose a method for each field.** Fields in a rule don't have to share a method. A rule can use exact matching on email and similar matching on name, so a typo in the name doesn't break a pair the email already supports.
- **Compare and group.** Records that meet the criteria on every field in the rule are grouped into duplicate sets. In many tools, a blank value doesn't count as a match, so a field that's empty in many records can block pairs.
- **Add rules for other combinations.** One rule can't describe every way two records point to the same customer. Separate rules, such as name + email and name + phone, each find duplicates the other one misses.
The same trade-off runs through every step of multi-field matching. More fields and stricter methods mean fewer false matches and more missed duplicates. Fewer fields and looser methods find more duplicates, along with more pairs that aren't the same record. A balanced rule keeps a strong field strict and lets the supporting fields vary a little.
Resources:
-
[Finding Duplicates](https://dedupe.ly/knowledge-base/find-duplicates)
(KB)

### Why Multi-field Matching Matters for CRM Teams

The fields a rule combines decide which records end up merged together. A rule with too few fields pairs records that only share one value: two people with the same name, or every contact behind a shared company inbox. If those sets are merged, different customers end up on one record, with their owners, activity and contact details mixed together. In many systems a merge is hard or impossible to reverse, so a loose rule causes problems that show up later in routing, reporting and billing.
A rule with too many fields fails the other way. Each extra field is another chance for a typo, a missing value or a different format to break the pair, so real duplicates stay in the CRM. They keep inflating contact and account counts, splitting activity history and putting the same customer in front of two reps. In CRMs that bill by record count, each one is also a record paid for twice.
Getting the combination right also decides how much review the work needs. A rule built on a strong anchor field and a few supporting fields produces sets that are safe to merge in bulk or on a schedule. A rule that sometimes pairs the wrong records needs a person to check each set, and that review time grows with the size of the database.
Resources:
- [How to correctly identify all duplicates in your CRM](https://dedupe.ly/blog/merge-with-confidence)

### Getting Started With Multi-field Matching

Begin with a short rule built on a strong field, such as email plus last name, and check a sample of what it finds before merging anything. Two or three well-chosen fields often do more than a long list, because each field added is one more way for a real duplicate to slip through.
When you deduplicate by multiple fields, give each field the method that fits how its values vary. Keep identifiers like email or customer ID on exact matching, and use a looser method on names, phone numbers or company names, where typos and formats differ. If a rule misses pairs you can see, compare the two records field by field and loosen or remove the one that breaks the match, changing one field at a time.
Then cover the other combinations with separate rules instead of making one rule longer. A rule on name + email and another on name + phone each catch duplicates the other misses, and each one stays easy to check. Before relying on a field, look at how often it's blank or filled with placeholders, since those values can block real pairs or tie unrelated records together.
In Dedupely, each field in a Duplicate Search gets its own Match Option, so email can stay on Exact while name uses Similar, and if a search compares three fields, all three must meet their criteria. You can clone a Duplicate Search to try a different combination of fields without changing the active one, then click "Scan" to see the results.
Resources:
-
[Duplicate Searches](https://dedupe.ly/knowledge-base/search-pads) (KB)
-
[How to Approach CRM Deduplication](https://dedupe.ly/knowledge-base/how-to-approach-crm-deduplication)
(KB)

### Key Takeaways: Multi-field Matching

Multi-field matching combines several fields in one matching rule, so two records pair only when every field meets its criteria. Each field added cuts false matches and misses more duplicates, so strong rules pair one anchor field, such as email, with a few supporting fields, and mix exact and looser methods across them. Separate rules cover the other field combinations. In Dedupely, each field in a Duplicate Search gets its own Match Option, from Exact to Similar, Fuzzy, Similar Words and Domain Root, and the Match Options guide recommends combining 2 to 4 key fields. Typo allowance keeps small differences from blocking a match on stricter options. Merge Rules decide what each merge keeps, and Auto Match and Auto Merge keep trusted searches running.
Resources:
- [Dedupely product overview](https://dedupe.ly/product)

### Frequently Asked Questions About Multi-field Matching

#### How many fields should a multi-field matching rule use?

Two to four fields work well for most rules: enough to rule out records that only share one value, and few enough that small differences don't break real pairs. One field on its own is rarely safe unless it's a true identifier, such as a customer ID. Past four or so, each extra field adds little precision and more ways for a typo, a blank or a different format to stop a match. The quality of the fields matters more than the count. Email + last name is often stronger than first name + last name + city, because email points to one person and a city is shared by many records. In Dedupely, the Match Options guide recommends combining 2 to 4 key fields. If a search compares three fields, all three must meet their criteria, and a field you don't trust can be set to None to leave it out of the match.

#### Which fields work best together when matching customer records?

The best combinations pair one field that identifies a person or company with one or two fields that confirm it. For contacts, email address, phone number or a customer ID make strong anchors, and last name or company confirms them. For companies, the website or email domain is a strong anchor, with company name, city or phone as support. Fields that many records share, such as first name, city or job title, work only as support, never as the base of a rule. Placeholder values like "N/A" or "none" weaken a field, because they match across unrelated records. In Dedupely, Domain Root compares the core domain of an email or website and ignores www, .com and country variants, which makes it a useful anchor for company searches. Safety Settings are on by default and hold back matches built on poor or example data, such as "John Doe," in an Excluded tab.

#### Why does adding more fields to a matching rule find fewer duplicates?

Because every field added is one more condition a pair has to meet. In rule-based matching, all the fields in a rule must agree, so a single difference in any one of them breaks the match. A nickname, a typo, a phone number saved in another format or a blank value is enough. That's the price of precision: a longer rule pairs fewer records by mistake, and also misses more real duplicates. To find the field that's causing it, compare two records you know are duplicates field by field. Then loosen that field's method, remove it or move it to a separate rule. In Dedupely, if a search compares three fields, all three must meet their criteria. Typo allowance, one of the search's Enhancements, keeps small differences from blocking matches when stricter options are used, and Similar strips formatting and country codes from phone numbers before it compares the last seven digits.

#### When should you mix exact and looser methods in one matching rule?

Mix methods when the fields in a rule vary in different ways. Identifiers such as email addresses and customer IDs are either the same or not, so exact matching suits them. Names, phone numbers and company names are often written several ways, so a looser method keeps a typo or a nickname from breaking a pair. The exact field anchors the rule and keeps false matches low, while the looser field confirms it. A rule with exact matching on email and similar matching on name, for example, finds a name with a typo at the same email address, without pairing every contact who shares that name. Avoid putting loose methods on every field at once, which brings false matches back. In Dedupely, each field in a Duplicate Search gets its own Match Option, so Exact, Similar, Fuzzy, Similar Words and Domain Root can sit in one search. On first-name fields, "Match nicknames" pairs names such as Robert and Bob with whichever Match Option the field uses.

#### How do you cover different field combinations, such as name + email and name + phone?

Give each combination its own rule instead of adding every field to one. A contact can appear once with an email and no phone, and again with a phone and no email. A single rule that needs both fields misses that pair, while two shorter rules each catch one version. Keep each rule built on its own strong field, check what it finds before merging, and give it a clear name so it's easy to tell which rule found which sets. Rules that overlap often surface the same duplicates, which is a sign they agree, not a problem. In Dedupely, an account can have up to 50 Duplicate Searches, and preset searches for common combinations are ready the first time you log in. You can clone a search to try a new combination without changing the active one. One Duplicate Search can hold several match groups, to combine different criteria.

### Related Terms and Concepts

#### [Visible fields](https://dedupe.ly/glossary/visible-fields)

Visible fields are the fields a search shows and compares. Multi-field matching is about how several of them work together, and which ones should anchor the match.

#### [Exact matching](https://dedupe.ly/glossary/exact-matching)

Exact matching is the most common anchor in a multi-field rule, often on email or an ID. It keeps false matches low while other fields use looser methods.

#### [Similar matching](https://dedupe.ly/glossary/similar-matching)

Similar matching is a common choice for the supporting fields in a multi-field rule. It lets a typo or a phone format differ without breaking a pair the anchor field already supports.

#### [Cross-field matching](https://dedupe.ly/glossary/cross-field-matching)

Cross-field matching compares values across the fields used in a match, so a value entered in the wrong field can still pair. It helps when a multi-field rule misses duplicates because data sits in different fields.

#### [False matches](https://dedupe.ly/glossary/false-matches)

False matches are what multi-field matching guards against. Each field added makes it less likely that two different records pair because they share one value.

#### [Duplicate search](https://dedupe.ly/glossary/duplicate-search)

A duplicate search is where a multi-field rule lives: the fields, the method for each one and the records it applies to. Several searches can cover different field combinations.
Skip to content