DEV Community

Leo Qi
Leo Qi

Posted on

Test Contact Deduplication Without Merging Different Buyers

In a B2B list, identical company domains do not mean identical people. The purchasing manager and a service engineer may share a domain while owning different decisions. Deduplication that merges them can erase the very distinction the sales team needs.

Keep three separate outcomes: exact match, possible match, and separate contacts. An exact match can use an existing internal contact ID or the same verified email under your documented comparison rules. A possible match can use a shared domain and similar names, but should only enter a review queue. Do not remove plus tags or dots globally; address behavior differs across providers and organizations.

Use a tiny fixture set before importing a large list:

  • Same verified address, different name formatting: link the two observations without discarding either source timestamp.
  • Same domain, different people: retain both contacts.
  • Name match, different company domains: review; the person may have moved companies, or the records may refer to different people.
  • No usable identity evidence: leave the row unmerged.

Measure false merges separately from duplicates left for review. The second problem costs cleanup time. The first can change who receives a message. They should not share a single success metric.

Top comments (0)