Activity, Scans & Audit#

The Dedupify settings page includes an Activity tab where you can review everything that has happened — merges, rule changes, and scans. The Dedupify home app also surfaces an Activity Dashboard tab alongside the Manage Duplicates tab.

The Activity tab’s merge and scan history.

Merge History#

The Merges sub-tab lists every merge that has been executed and every time a rule was turned on or off. Each entry shows:

• Whether the merge was performed manually by a user or automatically by a rule.
• For manual decisions: the HubSpot user who acted, the timestamp, the match rule involved, and the confidence score at the time of the decision.

Use this history to confirm what was merged, by whom, and under which rule — helpful when auditing data changes or investigating unexpected results.

Scan History#

The Scans sub-tab lists every scan that has run, with detail including:

• The number of records scanned.
• The number of candidate pairs found.
• Total duration and per-phase timing.

Use this to understand how long scans take, how many candidates a rule is generating, and whether a rule change had the expected effect on candidate volume.

Understanding Why a Pair Was Matched#

When you open a candidate pair or a merge history entry, the activity detail can show the normalization steps Dedupify applied to each field during scoring — for example, lowercasing a name, stripping plus-tags from an email, or reducing a phone number to its digit sequence. This lets you see exactly why two values were considered equivalent, which is useful when investigating a potential false positive.

To dig deeper into why a specific rule fires, use the Test pair feature in the rule editor. See Matching Rules for details.

Investigating False Positives#

If Dedupify is surfacing pairs that shouldn’t be duplicates:

1. Check which rule fired and its confidence score relative to your review threshold. A score just above the threshold suggests the rule may be too broad.
2. Review per-field contributions using Test pair in the rule editor. This shows exactly how much each field contributed to the score.
3. Assess the matching properties. If a field has low discriminating power (for example, a common job title), remove it from the rule or pair it with a stronger identifier.
4. Tighten the rule by raising the review threshold or adding a hard-match requirement on a strong identifier.
5. Add a Never Merge rule to protect specific records from ever being merged. See Object Settings for details on Never Merge rules.

After dismissing a pair in the review queue, Dedupify will not resurface it unless the records are updated in a way that would re-evaluate them.

Reversing a Merge#

Dedupify does not provide a native undo. To reverse a merge:

1. Open the recycle bin for the relevant object type in HubSpot (Contacts, Companies, Deals, or Tickets).
2. Restore the losing record. HubSpot retains deleted records in the recycle bin for 90 days; after that they are permanently removed by HubSpot and cannot be recovered.
3. Return to Dedupify and dismiss the pair so it is not surfaced again.

If 90 days have passed, the record cannot be recovered from HubSpot’s recycle bin and the merge cannot be reversed.