What is address deduplication for direct mail?
Address deduplication is the workflow step that finds records likely to represent the same mailable destination or household decision before a campaign is approved for print.
It is not the same as address standardization. Standardization reviews address format and fields. Deduplication compares records and decides whether one, many, or none should move forward. For the address-format layer, see the address standardization guide.
What should a dedupe record store?
A dedupe record should store the match inputs, match rule, duplicate group, survivor decision, held records, owner, and audit timestamp.
| Field | Why it matters |
|---|---|
| Match key | Shows whether matching used address, name, source ID, household key, or another field group. |
| Duplicate group | Keeps all candidate records visible before one record is selected. |
| Survivor record | Shows which record remains eligible for mail and why. |
| Held records | Explains which records were paused or removed from this batch. |
| Exception reason | Preserves cases where similar records should still mail separately. |
| Audit timestamp | Connects the dedupe decision to approval and batch release. |
How do householding and merge-purge fit?
Householding and merge-purge are related but broader decisions. Householding can apply a campaign rule at the household level. Merge-purge combines lists, removes duplicate candidates, and chooses the surviving record before print.
Because householding is now part of the list hygiene hub, keep household decisions connected to list hygiene and merge-purge records instead of treating them as a separate page.
How should dedupe connect to suppression?
Deduplication decides which similar record should represent a mailing decision. Suppression decides whether a record should be held back because of an exclusion rule, returned-mail feedback, do-not-mail status, or another reason.
Keep both decisions visible. A dedupe survivor can still be suppressed. A suppressed duplicate should still be recorded so the audit trail explains why it was not mailed. For exclusion records, see the suppression-list guide.
What should dedupe not decide?
Dedupe should not decide that an address is deliverable, current, or ready for release by itself. It only evaluates record overlap. Address readiness, move-update context, proof approval, and send rules need their own records.
Use the mailable address guide, NCOA guide, and send-rule guide for those adjacent decisions.
FAQ
What should address deduplication for direct mail include?
It should include match keys, duplicate groups, survivor rules, held records, exception reasons, suppression context, approval owner, and audit timestamps.
Is address deduplication the same as address standardization?
No. Standardization reviews address format and fields. Deduplication compares records and decides whether one, many, or none should move forward.
Sources
Keep duplicate decisions reviewable.
Sendvo is a beta direct-mail platform for teams connecting audience data, address checks, postcard design, triggered sends, USPS tracking, and audit records.