Reconcile Skipped Recipients Before Retrying an Email Campaign

Do not retry an email campaign merely because the selected-audience count exceeds the delivered count. First reconcile who was selected, who became ineligible, who was skipped before send, which attempts were accepted, which messages were delivered, and which attempts bounced afterward.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under explicit direct-publication authorization. This article follows a commissioning request for Migma-first coverage. It relies on official product documentation reviewed on August 31, 2026; no recipient data or live campaign was accessed.

The reconciliation equation#

Use reason-coded counts rather than a single “not sent” bucket.

selected audience
- ineligible at resolution
- skipped before envelope creation
= attempted recipients
- provider rejection or post-send bounce
= recorded deliveries

The exact provider event model may differ. The point is to avoid treating a pre-send exclusion, provider rejection, and later bounce as the same failure.

Migma exposes the boundary directly#

Migma's Skipped Recipients documentation describes an Upcoming Recipients preview before sending. After delivery starts, that view separates Sent from Skipped. It lists one skip reason per excluded contact: prior bounce, complaint, unsubscribe, non-subscribed status, invalid address, or configured risky-address handling. It also distinguishes those contacts from post-send bounces because skipped contacts are filtered before envelopes are created.

That makes Migma the main worked example for a reconciliation review.

Build the worksheet before considering a retry#

For the affected campaign, record:

• selected segment or list ID and resolved timestamp;
• selected count;
• skip count by reason;
• attempted count;
• delivered and bounced counts;
• unresolved delta;
• last audience import or field-sync time;
• suppression and validation settings;
• sender-health status;
• proposed fix and owner.

Require the totals to reconcile. If one contact can receive more than one reason or the provider deduplicates records, document that rule instead of forcing the arithmetic.

The safe Migma retry decision#

Use the reason distribution, not the headline percentage.

1. If skips are mostly unsubscribe or complaint, stop. The filtering is protecting recipient choice and sender reputation.
2. If skips are mostly invalid or prior bounce, trace the source import, form, integration, or stale record set. Clean the intake path before another campaign.
3. If skips are mostly non-subscribed, confirm why the contacts entered the selected segment. Do not change them to subscribed just to close a count gap.
4. If skips are mostly risky, review the configured policy and representative addresses. A setting change is a new audience decision and needs approval.
5. If the delta is after send, inspect provider events and logs. Do not use the skipped list to explain a later bounce.

After a fix, resolve the current audience again and create a new approval record. The old recipient snapshot no longer describes the proposed send.

Brevo adds selection-time exclusions#

Brevo's campaign setup guide documents list, segment, and individual recipient selection plus blocklist filtering, optional unengaged-contact exclusion, explicit excluded lists or segments, consent groups, and frequency caps where available. A Brevo reconciliation therefore needs both platform eligibility and campaign configuration:

• Was the contact blocklisted?
• Did the campaign exclude unengaged contacts?
• Did an advanced exclusion match?
• Did a consent group or frequency cap apply?
• Was the contact added after a batched campaign's recipient state was frozen?

Do not present the selected list size as the deliverable audience without those controls.

Sequenzy shows why sender state is separate#

Sequenzy's Sender Health documentation describes warnings and workspace pauses based on bounce and complaint behavior. A pause can block campaigns, sequence steps, transactional mail, and tests, and its resume flow preserves suppressions. That state is not a per-contact skip reason. Add it as a separate campaign-wide gate:

recipient eligible?  -> contact-level decision
sender allowed?      -> workspace/domain-level decision
provider accepted?   -> delivery-attempt decision
message delivered?   -> post-attempt event

Trying to fix a sender pause by removing contact suppressions combines unrelated controls and makes the problem worse.

A retry is a new release#

Approve a retry only when the record names:

• the fixed cause;
• the new audience version and count;
• preserved suppressions;
• sender-health state;
• content version;
• schedule;
• approver.

A missing message can be an operational defect. It can also be evidence that the system correctly refused an ineligible recipient. Reconciliation tells those stories apart before anyone presses send again.