How to Reduce False Positives in Dedupe Matching (Without Losing Real Duplicates)

Start Tight, Not Loose

The most common mistake is starting with broad fuzzy matching across every field. It feels thorough, but it creates enormous noise. A record for "John Smith at Acme Corp" and "Jonathan Smithfield at Acme Construction" might score as a probable duplicate when they clearly aren't the same person.

A better approach: start with exact-match filters on your most reliable fields. Email address is the gold standard. If two leads share the same email, they are almost certainly duplicates. Phone number is a solid second. The Company domain works well for Account deduplication.

Once you have caught all the obvious matches, then introduce fuzzy logic to handle variations like typos and nickname differences. Build from certainty outward. Don't start fuzzy and try to tighten things up after the fact.

Fix the Empty Field Rule First

This one is responsible for more false positives than anything else, and it is almost always overlooked.

By default, the Empty Field Rule in a Plauti Deduplicate scenario is set to Disregard. That sounds harmless, but what it actually means is this: if a field is empty, it gets ignored completely when calculating the matching score. So, if a contact has no phone number on file, that blank field doesn't lower their score at all.

The result? A record with just a first name and a postal code can match at 100% against another record with the same first name and postal code, even if they are completely different people.

The fix is simple. Go into your scenario settings and change the Empty Field Rule from Disregard to Score 0%. Now empty fields actively bring the score down. That single change will often cut your false positive count significantly on the very next job run.

Choose the Right Matching Method for Each Field

Not every field should use the same matching method. This is where a lot of configurations go wrong.

Email addresses should use Exact matching. If you apply fuzzy logic to an email field, you will start flagging records that share the same domain as potential duplicates. That's technically "similar," but it is not a meaningful match signal at all.

The same logic applies to external IDs, EINs, or any unique identifier your organization uses. Use Exact matching there. Assign those fields a high weight. If two records have different values in a field that is meant to be unique, they are almost certainly not the same record.

For names, fuzzy matching makes sense. A "First Name" field benefits from synonym matching so that Bob and Robert get caught. A "Last Name" field works well with a partial fuzzy approach to handle minor typos. Company names are trickier. "IBM" and "International Business Machines" are the same company, but a loose fuzzy match might also connect "IBM" to "IB Medical." The Company Name matching method in Plauti Deduplicate is specifically built for this kind of comparison and handles it far better than plain fuzzy text.

Matching the algorithm to what the field actually contains. That single habit removes a large share of false positives before you even touch your threshold settings.

The Plauti Deduplicate matching methods guide covers which methods apply to which field types in detail.

Raise Your Threshold

If your scenario threshold is sitting at 60% or 70%, you are going to see a lot of noise. That range is broad enough to catch real duplicates, but also broad enough to pull in plenty of records that just happen to share a few common values.

Tightening your threshold to 80–85% is a good starting point for most scenarios. It requires a closer overall match before a pair gets surfaced for review. Combine this with the Empty Field Rule fix above, and you will see a meaningful drop in false positives right away.

For automated merging without manual review (Direct Processing), set your threshold higher still. 99–100% is recommended. You only want to auto-merge records when you are very confident. A wrong merge is much harder to undo than a missed duplicate.

Use Secondary Fields to Break Ties

A scenario built on two or three fields is fragile. Two records matching on Name and Record Type alone is not enough signal to call them duplicates with confidence.

Add more discriminating fields. Postcode, email, phone, city, street, job title. The more concrete identifiers you include, the harder it becomes for two unrelated records to score above your threshold. When primary fields are close but not conclusive, secondary fields like State or Department can be the deciding factor.

Weight your most unique fields the highest. Email and phone should outweigh first name. Postcode should outweigh city. The hierarchy of your field weights is just as important as which fields you include.

Add a Frequent Words List

Some words show up in nearly every record of a certain type. Legal entities like "Inc," "LLC," and "Ltd." Common industry terms like "Consulting," "Restaurant," or "Services." These words don't help distinguish one record from another, but if they're included in your matching logic, they push scores up and create false matches.

In Plauti Deduplicate, you can configure a Frequent Words list per field. Words on that list get excluded from the matching calculation. So "Willson Architects" compares against "Willson & Son" as "Willson" vs. "Willson & Son," which gives you a much more honest score.

One thing to verify: check that Activate Improved Frequent Words Handling is switched on. You'll find it in DC Setup > Settings > Critical Updates. Without it, frequent words may not be excluded correctly in all matching scenarios, even if you have already set up the list.

Use Match Scores as a Gate, Not a Guarantee

Most deduplication tools give you a similarity score for each record pair. The temptation is to auto-merge everything above a certain threshold. That's where false positives turn into false merges, which is a much bigger problem.

A tiered workflow works far better:

• Auto-merge only records that hit a very high confidence threshold on high-certainty fields, like an identical email address.
• Queue for review everything in the middle range, so a human can confirm before any merge happens.
• Auto-dismiss pairs that fall below your minimum threshold.

The records your team reviews should be genuinely ambiguous, not obvious non-duplicates. If your review queue is full of clearly different records, your lower threshold is too low.

Let AI Handle the Gray Zone

Even with well-tuned scenarios, some record pairs will sit in that uncertain middle range. Not obvious duplicates, not obviously distinct either. That gray zone is where review time piles up fast.

AI Match Recommendation in Plauti Deduplicate is built specifically for this problem. After running a job, you can apply AI Match Recommendation to the results. It analyzes each duplicate pair across all fields in context and labels it as Duplicate, Not Duplicate, or Uncertain, with a confidence score and a reason.

Your team then focuses only on the pairs the AI flags as genuinely uncertain. Everything the AI calls clearly duplicate or clearly not a duplicate gets handled automatically. It doesn't replace human judgment. It focuses on where it actually matters.

AI Match Recommendation is available in the Premium and PDM editions. When used alongside Auto Merge, it lets you safely lower your auto-merge threshold slightly (to around 97–98%) because the AI recommendation adds an extra layer of confidence.

When You Still Get False Positives, Use the Discard Feature

Even after tuning your scenario, some false positives will come through. That's normal.

When you come across a pair that clearly isn't a duplicate, mark it as False Positive in the DC Job results or DC Live. That specific pair won't appear in any future job results. Each discard is specific to that pair, so both records remain eligible to match with other records going forward.

If your matching criteria changes later and you want to reconsider previously discarded pairs, you can remove them from the DC Discards tab. They'll re-enter the matching pool on the next job run.

Review, Adjust, Repeat

Deduplication configuration is not a one-time project. Your data changes. Your processes change. What worked six months ago might generate more noise today.

Build a habit of reviewing your false positive rate after each job run and adjusting one variable at a time. Change one field's matching method, or raise the threshold by five points, then run the job again and compare. If you change too many things at once, you won't know what actually helped.

The Plauti Deduplicate scenario setup guide is a useful reference to keep open while you're tuning. And if you're starting from scratch, doing a record analysis first, listing your objects, identifying your most discriminating fields, and planning your weight hierarchy before you build anything, saves a lot of back-and-forth later.

Quick Reference: Common Causes and Fixes