ChatGPTClaudePerplexityGoogle
View as Markdown

TL;DR

  • Duplicates often hold two emails for one person, and one of them may bounce.
  • A merge that keeps the oldest record's email can keep the dead address.
  • Use the bounce status, not the record's age, to decide which email wins.
  • Keep the dead address only where it helps, like an old-emails field for history.
  • In Dedupely, a Lose Rule can stop an email from winning based on another field, like a bounce flag.

A contact changed jobs, or mistyped their email once, and now they have two records: one with an address that bounces and one that works. When you merge them, only one email can be the main address.

If the merge keeps whichever record is oldest, it will often keep the dead one, because the older record is the one from before the job change. Every email you send after that bounces, and enough bounces hurt your sender reputation for everyone else.

This post covers how to make sure the working email wins, and what to do with the one that doesn't.

Why the wrong email wins

Most merges pick one record as the primary and keep its email. Common defaults pick that record by age:

  • Oldest record: often has the old address from a previous job.
  • Newest record: often has the right address, but not always. A form fill with a typo is new too.
  • Last updated record: may have been touched by an integration that didn't change the email.

None of these look at whether the email works. Your email tool knows that: it records hard bounces. That's the field to use.

Use the bounce status to decide

Most CRMs and email tools store bounce information on the contact: a hard bounce flag, a bounce reason or an "email invalid" status. When one duplicate has a bounce and the other doesn't, the email from the record without a bounce should win.

Record A Record B Email to keep
Bounced Not bounced B
Not bounced Not bounced Follow your usual rule, often the most recently engaged
Bounced Bounced Neither works; keep one and mark the contact for re-confirmation
Not bounced, typo domain Not bounced The correct one; check the domain

Keep the old address where it helps

The dead address isn't worthless. Replies to old threads, old list imports and past form fills may still reference it. If your CRM has an additional email or secondary email field, keeping the old address there means future imports with that address still find the right contact, instead of creating another duplicate.

Don't keep it as the main address, and don't let it rejoin your sending lists.

Check the opt-out status too

Bounces and unsubscribes are different things. When you merge, make sure that if either record unsubscribed or opted out, the merged record stays opted out. Losing an opt-out in a merge is worse than losing a working email.

How to make the working email win in Dedupely

In Dedupely, Merge Rules let you set which value wins for each field. A Lose Rule blocks a value from winning, and its condition can look at another synced field, so a rule like "the email loses when the bounce field is not blank" keeps a bounced address from becoming the main one. Lose Rules are checked before Win Rules. Best-email options also prefer a work email over a free provider, and Append keeps every unique value in your CRM's multi-value email fields.

You can preview the result before merging, so you can check the rule on a few real pairs first.

Keep the email that works

Let deliverability decide

When duplicates hold two emails and one bounces, the record's age is a poor guide. Use the bounce status to pick the working address, keep the dead one only where it helps future matching and make sure opt-outs survive the merge.

That keeps every merged contact reachable, and keeps bounces from coming back through the next import.

Frequently asked questions

Which email should I keep when one duplicate's email bounced?

The one that doesn't bounce. Use the hard bounce status from your CRM or email tool, not the age of the record.

Should I delete the bounced address?

Not necessarily. Keeping it in a secondary email field helps future imports find the right contact. Just don't use it as the main address.

What if both emails bounce?

Keep one, mark the contact as needing a new email and don't send to it until it's confirmed.

Do soft bounces count?

Base the rule on hard bounces only. A soft bounce, like a full inbox, is often temporary.

What happens to an unsubscribe when duplicates merge?

Make sure it's kept. If either record opted out, the merged record should stay opted out.