Lead Deduplication
Lead deduplication is the process of identifying and merging duplicate records that represent the same person or company into a single canonical lead. It keeps the database accurate and uncluttered.
In depth
Deduplication works by comparing records on matching keys such as email, phone, normalized name, and domain, then applying survivorship rules to decide which field values survive the merge. Fuzzy matching handles near-duplicates like 'Jon Smith' versus 'Jonathan Smith' or differing email casing, while exact matching catches obvious collisions. The reason it matters is that duplicates inflate reporting, waste sales outreach, and split a single buyer's history across fragments, making scoring and follow-up unreliable.
A common pitfall is over-merging, where an aggressive rule collapses two genuinely different people who share a generic inbox into one record and loses real data. In a quiz-funnel workflow, the same person may complete a scorecard twice from different devices or revisit after weeks, so deduplication must reconcile multiple result submissions into one lead while preserving the most recent and highest score. Done well, it ensures each contact is counted once toward plan lead limits and routed without duplicate alerts to sales.
Example in practice
Frequently asked questions
Which fields are best for matching duplicates?
Email is the strongest single key, followed by phone and company domain, with normalized names used for fuzzy matching. Combining two or more keys reduces both false merges and missed duplicates.
What is survivorship in deduplication?
Survivorship is the set of rules that decides which field values win when records merge, such as keeping the most recent quiz score or the earliest acquisition source. Clear survivorship rules prevent good data from being overwritten during a merge.
Why does deduplication matter for billing?
Many plans count unique leads against a monthly limit, so duplicates can inflate usage and skew cost-per-lead. Deduplicating ensures each real person is counted once and your reporting stays accurate.