# How to choose which fields to match duplicates on in Pipedrive

> Choosing the right fields determines how duplicates are identified in Pipedrive. This guide explains how to configure field-based matching logic using search.

- URL: https://dedupe.ly/blog/pipedrive/choose-fields-to-match-in-pipedrive
- Section: blog
- Published: 2026-02-24
- Site index: https://dedupe.ly/llms.txt
- Any page: append `.md` to its URL for this plain-text form

---

Skip to content
[New Dedupely Intelligence Now on every paid plan, monthly or yearly.](https://dedupe.ly/ai-deduplication)
[Blog](https://dedupe.ly/blog)
[Pipedrive](https://dedupe.ly/blog/pipedrive)

## How to choose which fields to match duplicates on in Pipedrive

Choosing the right fields determines how duplicates are identified in Pipedrive. This guide explains how to configure field-based matching logic using search.
Published February 24, 2026
· Updated September 23, 2026
#
min read
Choosing which fields to match duplicates on in Pipedrive starts with defining what actually makes two records represent the same entity in your Pipedrive instance. Email may be enough in some cases. In others, identity depends on a combination of name, company, domain, or other fields.
Choose the Pipedrive record type you need to merge before setting your matching fields:
[duplicate contacts](https://dedupe.ly/integrations/pipedrive/duplicate-people),
[duplicate organizations](https://dedupe.ly/integrations/pipedrive/duplicate-organizations),
[duplicate deals](https://dedupe.ly/integrations/pipedrive/duplicate-deals).
Duplicate accuracy improves when field selection reflects how your data is structured. That decision determines whether matches are thorough, lenient, or inconsistent.

### How to configure matching in Pipedrive

- **Choose the object**
Open Pipedrive in Dedupely and select People or Organizations.
- **Choose the visible fields:**
Select the key identifiers you want Dedupely to compare, such as Email, First Name, or Phone Number.
- **Edit the match options per field:**
Decide how thorough or lenient the matching should be. Click the arrow under each field name to switch between Exact, Similar, Fuzzy, Similar Words, or Domain Root.
- **Add filters (optional):**
Narrow down your results to only scan relevant segments of your data.
- **Run a scan:**
Process your database to group the matching records.
- **Tweak the Duplicate Search:**
Adjust your match types or swap out fields to zero in on the precise duplicates you want to find.

### Why Pipedrive limits which fields are used to match duplicates

Pipedrive’s native duplicate detection relies on predefined comparison logic. Users cannot fully control which fields define a duplicate or how those fields are compared.
In practice, this means:
- Field selection is limited to system behavior
- Match strictness cannot be adjusted per field
- Different duplicate scenarios cannot be handled separately
- All matches follow the same comparison structure
When field control is limited, duplicate results often group records that should stay separate or miss records that clearly belong together. Reporting and segmentation depend on how duplicates are defined, so field selection directly impacts data clarity.
To gain full control over which fields define duplicates and how they are evaluated, additional match configuration is required.

### How Duplicate Searches work in Dedupely

In Dedupely, duplicate matching is built through Duplicate Searches. A Duplicate Search is a saved search where you choose:
- The object in Pipedrive
- The fields that define a duplicate
- The match option for each field
Each Duplicate Search runs independently and scans the entire synced object.
Inside a single Duplicate Search, you can add multiple fields. All selected fields must meet their configured match condition for records to be grouped together.
For example:
- Duplicate Search: Email and organization identity
- Email set to Exact match
- Organization set to Domain root match
Both conditions must be satisfied for the records to appear as duplicates.

> *Tip: The "Do not match" option can be applied to a field when testing configurations. It allows you to see how results change without including that field in the final comparison logic.*

### Matching options available in Dedupely

Each field inside a Duplicate Search can use a different matching option. This determines how values are compared.
Available options include:
- **Exact match:** Values must be identical character for character
- **Similar match:** Allows minor variations in spelling or formatting
- **Fuzzy match:** Uses broader similarity logic to detect close variations
- **Similar word match in any order:** Matches values containing the same words regardless of word order
- **Domain root match:** Compares only the base domain instead of the full URL or subdomain
[You can find a full explanation on how each match option works here :)](https://dedupe.ly/knowledge-base/match-options)
Choosing the correct matching option per field determines whether a search is thorough or lenient. Reliable identity fields such as primary emails usually work best with Exact or Domain root matching. Fields that naturally vary, such as company names, may require Similar or Fuzzy matching.

### How field selection and match options work together

Field selection and matching options define how identity is evaluated in your Pipedrive instance.
When multiple fields are added to a Duplicate Search:
- Every selected field must match
- Adding reliable fields increases precision
- Reducing fields makes the search more lenient
- Changing match options alters comparison strictness
A thorough search might include:
- Email with Exact match
- Organization with Domain root match
A more lenient search might include:
- First name with Similar word match
- Organization with Fuzzy match
These configurations serve different purposes: Thorough searches isolate high-confidence duplicates and lenient searches capture edge cases where identity is similar but not identical.

### How to create multiple Duplicate Searches for different duplicate scenarios

In Dedupely, you are not limited to a single duplicate matching logic, you can create multiple Duplicate Searches, each targeting a specific type of duplicate you recognize in your Pipedrive instance.
For example:
- One Duplicate Search for identical email duplicates
- One Duplicate Search for similar company name duplicates
- One Duplicate Search for domain-based organization duplicates
Each Duplicate Search:
- Uses its own field combination
- Uses its own matching options
- Runs independently
- Can be saved, cloned, and edited
This allows you to approach duplicate matching by scenario rather than by one general rule.

> *Tip: Create a dedicated Duplicate Search for each duplicate pattern you repeatedly encounter. Over time, this builds a repeatable duplicate governance structure. Some searches can later be automated, but that's a different conversation.*

### How choosing the right fields reduces false positives

False positives usually result from either overly lenient field selection or mismatched comparison behavior.
If selection is too thorough:
- Legitimate duplicates may not be grouped
- Records remain fragmented
If selection is too lenient:
- Different entities may be grouped together
- Manual corrections increase
Precision improves when:
- Reliable identity fields are prioritized
- Matching options reflect data variability
- Thorough and lenient searches are separated into different Duplicate Searches
Choosing fields intentionally ensures that duplicate matching reflects how identity actually exists in your Pipedrive instance.

### FAQ: choosing fields for duplicate matching in Pipedrive

#### Can I choose which fields define duplicates in Pipedrive?

Pipedrive’s native detection uses predefined logic. Using Dedupely, you can select which fields define duplicates within each object and configure how each field is compared.

#### How many matching options are available in Dedupely?

Dedupely provides multiple matching options including Exact, Similar, Fuzzy, Similar word (any order), and Domain root matching.
[A detailed breakdown is available here.](https://dedupe.ly/knowledge-base/match-options)

#### Can I run multiple duplicate searches with different fields?

Yes. Dedupely allows you to create multiple independent Duplicate Searches, each with different field combinations and matching options.

#### Does duplicate matching scan the entire Pipedrive object?

Yes. Once an object is synced, each Duplicate Search scans the entire dataset for that object.
Choosing which fields define duplicates determines how identity is structured in your Pipedrive instance. Field selection and matching options directly influence reporting clarity, segmentation accuracy, and overall data consistency.
If you want to see how field-based duplicate matching works in practice, you can review it live with our customer success team.
[You can book a Zoom session here to walk through Duplicate Search configuration and matching options step by step.](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)
Behind the article

### Gaby Salinas

Marketing Assistant at Dedupely
Gaby Salinas came to CRM data from marketing and advertising, so she looks at duplicates from two sides: the match and merge logic behind them, and what they do to the people using the CRM, like the rep who calls a customer twice, the admin who gets blamed and the cleanup nobody wants to start.
As Marketing Assistant at Dedupely, she follows how RevOps teams, end users, consultants and technical teams actually work with their data: the records they stop trusting, the workarounds they build and the moment they finally decide to clean up. What she finds shapes most of what Dedupely publishes.
[Connect with Gaby on LinkedIn](https://www.linkedin.com/in/gbyslns)

### Contact us

We’d be happy to help you get this set up.

#### Write us a message

We probably know the answer to your question already
help@dedupe.ly
Email copied to your clipboard!
[Book a Zoom Whether you’re getting started or getting intense. Get in touch! Book a zoom](https://meetings.dedupe.ly/meetings/gaby-salinas/dedupely-zoom-scheduler)

### Discover Related Blog Posts

Stay updated with our latest articles and insights.
- [Pipedrive How to choose which fields to match duplicates on in Pipedrive Choosing the right fields determines how duplicates are identified in Pipedrive. This guide explains how to configure field-based matching logic using search. Gaby Salinas February 24, 2026](https://dedupe.ly/blog/pipedrive/choose-fields-to-match-in-pipedrive)
- [Pipedrive Protect fields when merging duplicates in Pipedrive with Dedupely Control which fields survive a merge in Pipedrive using Dedupely's merge rules. Gaby Salinas October 1, 2025](https://dedupe.ly/blog/pipedrive/protect-fields-in-pipedrive-with-dedupely)
- [Pipedrive What happens when you merge in Dedupely for Pipedrive What a Dedupely merge does in Pipedrive: which values win, how emails and phones combine, what moves to the surviving record and what can't merge. Gaby Salinas October 28, 2026](https://dedupe.ly/blog/pipedrive/deduping-pipedrive-with-dedupely)
[See all](https://dedupe.ly/blog)

### Get started for free

20 free trial merges and as much free support as you need to get your duplicates under control.
[Try for free](https://v2.app.dedupe.ly/signup)[Talk to sales](https://meetings.dedupe.ly/meetings/gaby-salinas/talk-to-sales)
[Or sign up with Google](https://v2.app.dedupe.ly/signup/google)
Running CRM cleanup for clients? [See the Partner Program](https://dedupe.ly/become-a-partner)
