First, confirm it is one message sent twice to one address
Ask for both copies, or find them in the send log, before changing anything. Several things look like a duplicate and are not. A person with a work and a personal address who forwards one to the other receives two messages, but the business sent each address one. A household where two people subscribed sees the newsletter twice in the same kitchen. A correction sent after a mistaken campaign can read as a repeat. And a mail app that groups messages into conversations can show one message twice.
| What the subscriber sees | How to tell | What it is |
|---|---|---|
| Two copies, each addressed to a different address of theirs | The To address on each copy | Two subscriptions, not a duplicate send |
| Two copies at one address, identical, close together | The send log for that address | A duplicate send: read the table below |
| Two copies at one address, days apart | The send log, and whether the campaign was rescheduled or reused | A repeated campaign, or a flow re-entry |
| Two similar messages, one from the newsletter and one from a flow | The sending flow or campaign named in the log | A flow and a campaign carrying the same message |
| A second message that changed one detail | The content of the two copies | A correction, handled as the mistake tutorial describes |
When the log shows two copies to one address, write down for each: the time it was sent, the system that sent it, and the campaign, flow or contact record it came from. Two copies from the same campaign and the same record point at a repeated send or a trigger firing twice. Two copies from the same campaign but different records point at a duplicate contact. Two copies from different systems point at two senders, and two copies from a flow and a campaign point at a missing priority rule. How a platform treats an address held on several lists or segments is in its own documentation; read the log rather than assume either way.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Both copies from the same send, each tied to a different contact record with the same address | Every record holding the address, and how each was created | The same person held as two contacts | Merge by written rules; set forms to update the matched record |
| Duplicates began after a list import or a new integration | The creation date and source of the records that were mailed twice | An import or integration that created new records instead of matching existing ones | Merge the new records into the originals; fix the matching rule |
| One copy from the email platform, one from the CRM, booking system or an old platform | Which systems sent a message to the address, and which owns that message | Two systems mailing the same people | Give each message one sending system and switch off the other |
| A flow message received twice, often a welcome or a reminder | The flow's entry history for the contact, and the trigger events received | A flow that lets a person enter twice, or a trigger that fires twice | Allow one entry per person or per event; stop the trigger firing twice |
| The same message from a flow and a campaign, or from two flows, on the same day | Which flows and campaigns reached the contact that day, and any priority rules | A flow and a campaign, or two flows, carrying the same message with no priority rule | Set priority and mutual exclusion; pause colliding flows on send days |
| Everyone on a send received it twice, or a whole segment did | The campaign list for a second copy, a reschedule or a resumed send | The same campaign sent twice | Stop any further copy; handle it as the mistake tutorial describes |
Fix, verify and prevent each cause
The same person held as two contacts
The CRM fundamentals guide lists where duplicate records come from: an import that did not match on email, a contact created by hand without searching first, and a form that creates a new record on every submission. Each duplicate splits a person's history, and workflows may fire for both records, so the person receives the newsletter twice and the welcome seriesThe automated sequence of emails sent to a new subscriber in the days after sign-up. twice. A duplicate also weakens an opt-out: a person who unsubscribes on one record can still be reachable on the other, which is one of the leaks traced in unsubscribed contacts still receiving email. Before merging, apply Chesterton's fence: find out what relies on each record, such as an open deal, a flow in progress or a booking, because the merge decides which value survives and in most systems cannot be undone.
Fix: write the merge rules first, keeping the most recent consent value and combining activities, then merge, and set every form to update an existing contact matched on email rather than create a new one.
Verify: the address appears once in the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. and the email platform, and a test submission of the form with an existing address updates that record.
Prevent: match on email at every entry point, as the guide recommends, and have a named person review the merge queue regularly.
An import or integration that did not match
A list import or a new integration can create a second record for everyone already on file when nobody decided what should happen on a match. The tutorial on importing contact lists cleans the file to one person per row, removes duplicates inside the file, and chooses the matching key and what a match may change before anything is loaded, testing that rule on a sample of rows that match existing customers.
Fix: find the records the import or integration created, using their creation date and source, and merge them into the originals by the same written rules. Then set the import or integration to match on email and update.
Verify: a small test load containing known existing contacts updates their records and creates none.
Prevent: run every import through that tutorial, and record each new integration and import in the change logA dated record of changes made to tracking, accounts, reports, lists or rules, with who made each and why, so later movements in the figures can be traced., so the next spike in duplicates can be traced to the day it began.
Two systems mailing the same people
A business with a CRM, an email platform and a booking or shop system has several tools able to send, and when two of them hold the same people and the same message, each sends its copy. The tutorial on migrating to a new email platform names the most common case: old and new platforms running side by side produce duplicate emails and two sets of flows with no shared exits, so the sending overlap in a move is kept as brief as possible. The guide to syncing the CRM and the marketing platform sets which system owns each field and each send. Apply Chesterton's fence again before switching anything off: the second system may also send messages nobody else does, such as service messages or sales follow-ups.
Fix: decide which system sends each message, switch that message off in the other system, and in a migration set a sending cutover date after which the old platform sends nothing.
Verify: the send logs of both systems for the next send show each message leaving only one of them.
Prevent: keep a written list of which system sends which message, and check it before any new tool or integration is allowed to send.
A flow that lets a person in twice
A flow sends twice when a person can enter it twice, or when the event that starts it arrives twice: a form submitted twice, an order event sent by both the site and an integration, or a contact removed from a list and added back. The email automation flow launch checklist asks for entry rules so contacts cannot enter a flow twice by mistake, and for the checklist to be run again whenever the trigger, the entry rules or the branches change.
Fix: set the flow to allow one entry per person, or one per order or booking where each one deserves its own message, and stop the trigger firing twice at its source.
Verify: a test contact who submits the form twice, or places a test order, receives one message.
Prevent: run the launch checklist after every change to a flow's trigger or entry rules. Tightening entry and priority rules too far is the opposite fault, and the diagnosis for a flow that is not sending treats priority rules and caps as one reason a flow goes quiet.
A flow and a campaign carrying the same message
A sale announced in the newsletter and in a browsing flow, or a reminder sent by two flows, reaches people who qualify for both. The automation governance guide sets a rule for which workflows cannot run concurrently for the same contact and which wins, and a frequency cap checked before every send, with service messages exempt. The automation hub adds the same priority rule for flows: when a person qualifies for two at once, decide which one wins and whether the other is delayed or dropped. For campaigns, the campaign send procedure schedules each send and pauses anything that would collide with it.
Fix: write a priority order and mutual exclusion rules for flows that carry similar messages, and pause colliding flows on campaign days.
Verify: a test contact in both a flow and the campaign audience receives one message about the subject that day.
Prevent: check which flows reach the same people as part of scheduling every campaign, and build audiences with the segmentation guide's lifecycle and behaviour segments so overlaps are visible before the send.
The same campaign sent twice
A campaign duplicated to make a new one and left scheduled, a send rescheduled without the original being cancelled, or a paused send resumed can put the same message in front of the same audience twice. Whether a resumed send continues or starts again is a question for the platform's documentation and the send log, not for memory.
Fix: stop any further copy at once, then follow the tutorial on fixing a mistake in a sent email: find out exactly what went out, list who received it twice, and decide whether anything more is needed. Its rule that most mistakes need less than a second email applies with force here, because an apology for a repeat is another repeat.
Verify: the campaign list shows one sent instance, and the send log shows one copy per address for the next send.
Prevent: follow the send procedure's scheduling step, cancel the original when rescheduling, and record duplicated or rescheduled campaigns in the change log.
Prevention: one record, one sender and one send for each message
Each cause breaks one of three rules, and the prevention is to make each rule someone's job.
| Rule | What keeps it | Owned by |
|---|---|---|
| One record per person | Matching on email at every form, import and integration; merges by written rules | CRM fundamentals and the import tutorial |
| One sender per message | A written list of which system sends which message; a short overlap in any platform move | The sync guide and the migration tutorial |
| One send per message per person | Entry rules, priority and mutual exclusion between flows, campaigns scheduled with colliding flows paused | The flow launch checklist, automation governance and the send procedure |
Then watch for duplicates as part of every send. After each campaign, read the send log for any address that received more than one copy, and sort the results by cause: two records, two systems, two entries or two sends. A small, steady number of duplicate records is the merge queue's work; a sudden jump points at the change made that day, which the change log should name.
Repeated mail shows up in the figures subscribers control. People who receive everything twice unsubscribe or report the mail as spam, so a rise in unsubscribesShare of delivered emails that led the recipient to opt out. or complaintsShare of delivered emails that recipients marked as spam. on one send, or across a segment that holds many duplicates, is worth reading against the send log; the unsubscribe spike diagnosis covers that reading. The spam complaint rate entry explains why complaints matter, and Google's email sender guidelines, as the deliverability guide summarises them, ask bulk senders to keep the spam rate below a documented threshold, which this page does not repeat. Duplicates also matter for consent. The mistake tutorial notes that the UK regulator's direct marketing guidance includes offering a way to opt out in every message; an opt-out that reaches one record and not its duplicate is not fully honoured, so keep the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints. matched on the address, not on the record. The email troubleshooting section holds the neighbouring diagnoses.
A dance school's double reminders (illustrative)
Druzzonet Dance School
Druzzonet Dance School, an invented dance school, hears from 14 parents in one week that the term newsletter and the weekly class reminders arrive twice. The send log for the newsletter shows 1,860 messages to 1,640 addresses: 220 addresses received two copies. Dating each copy shows two separate faults. A new integration added three weeks earlier lets the booking system and the email platform both send class reminders, so every family with a booking receives each reminder from both. And the enrolment form creates a new contact for every child enrolled, so families with two children hold two records and receive two newsletters. The school decides that the booking system alone sends reminders, as service messages, and switches them off in the email platform after checking that nothing else depended on them. It sets the form to update an existing contact matched on email, merges the 220 duplicate pairs by written rules that keep the most recent consent value, and logs both changes. The next newsletter's send log shows 1,640 messages to 1,640 addresses, and unsubscribes on that send fall from 31 to 9.
Common mistakes
- Assuming every report is a duplicate send. Two addresses, a household or a correction can look like one; confirm it is one message to one address first.
- Deleting the second record. The opt-out, the booking or the open deal may sit on it; merge by written rules instead.
- Switching off a second system without asking what it sends. It may carry service messages nobody else sends.
- Running two platforms side by side for weeks in a move. Every flow and campaign doubles; keep the overlap as brief as possible.
- Fixing the duplicate records but not the form that makes them. The next enrolment or sign-up creates more.
- Apologising by email. A message about a repeat is another message; fix the cause and check the next log.
