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…
In a B2B list, identical company domains do not necessarily indicate identical individuals. A purchasing manager and a service engineer might share the same domain but hold distinct decision-making roles. Deduplication that merges them can unintentionally erase the crucial distinctions required by the sales team. It is essential to maintain three separate outcomes: an exact match, a possible match, and separate contacts.
An exact match can utilize an existing internal contact ID or employ the same verified email address, provided that the comparison rules are followed diligently. A possible match can be identified through a shared domain and similar names, but it should be flagged for review and only progress to the review queue if deemed necessary. It is crucial not to remove plus tags or dots globally, as address behavior varies across providers and organizations.
Before importing a large list, it is advisable to start with a small fixture set. If the verified address remains the same while the name formatting differs, the two observations should be linked together, and neither source timestamp should be discarded. When dealing with a shared domain but different people, both contacts should be retained.
When a name match occurs, but the companies have different domains, the situation requires review. The individual might have changed companies, or the records could be referring to different people altogether.
If there is no usable identity evidence, the row should be left unmerged. It is crucial to measure false merges separately from duplicates that require review. While false merges can lead to incorrect recipients, they should not be treated with the same success metric as duplicates left for review. They represent two distinct problems with different implications.
Rewritten by urgent.news; may contain errors — check the original.
Source: dev.to