Review Thresholds & Auto-Merge#
Every match rule has two thresholds: one that controls what you see in the review queue, and an optional second one that lets Dedupify merge pairs automatically when confidence is high enough.
A rule’s review-threshold presets and optional auto-merge settings.
The Review Threshold#
The review threshold sets the minimum confidence score a pair must reach before it appears in your review queue. Any pair scoring below it is ignored.
You choose from four presets:
| Preset | Score required | When to use |
|---|---|---|
| Conservative | ≥ 80% | Fewer candidates, higher precision |
| Standard (default) | ≥ 65% | Balanced starting point for most portals |
| Surface everything | ≥ 50% | Catch marginal pairs — expect more false positives |
| Custom | 40–90% | Set an exact cutoff that fits your data |
Start with Standard and adjust after reviewing your first batch of candidates. If you see too many near-misses, raise the threshold; if obvious duplicates are missing, lower it.
Auto-Merge (Optional)#
Auto-merge is off by default. When turned on for a rule, pairs scoring at or above the auto-merge threshold are merged automatically — no human approval needed.
Auto-Merge Presets#
| Preset | Score required |
|---|---|
| Near-identical | ≥ 97% |
| High confidence (default) | ≥ 93% |
| Custom | 90–100% |
The auto-merge threshold must always be greater than or equal to the review threshold. Dedupify enforces this automatically.
How to Enable Auto-Merge#
Open the match rule you want to configure and toggle Enable auto-merge for this match rule. Before saving, you will be asked to type “I accept the risk” to confirm the activation. This acknowledgement is required because merges are not trivially reversible — see the note on rollback below.
Auto-merge applies to both the initial background scan and to ongoing near-real-time duplicate detection.
Auto-Merge Availability#
Auto-merge is only available on active paid plans. It is disabled during the free trial and will not run if your subscription is not active.
Rule Strength Requirement#
A rule must be strong enough before auto-merge can be turned on. Specifically, the rule must include at least one strong identifier (email, phone, or LinkedIn URL) or at least two supporting matching properties. If your rule does not meet this bar, Dedupify explains what to add — either a strong identifier or a second matching property.
See Matching Rules for guidance on building strong rules.
Rollback#
Merges use HubSpot’s native merge. The losing record moves to HubSpot’s recycle bin and can be restored within 90 days. Plan and test your thresholds before enabling auto-merge on a large active dataset.