All dispatchesView as Markdown

The email deliverability checklist for every campaign

MC
Maya ChenDeliverability at Email Bump

A practical pre-send routine for protecting your sender reputation and reaching more inboxes.

Deliverability is not a switch you flip after a campaign underperforms. It is the result of dozens of small, consistent choices: who you send to, how you collect consent, what you write, and how quickly you react when engagement changes.

Use this checklist before every important send. It is intentionally short enough to become a habit, but thorough enough to catch the issues that most often keep good email out of the inbox.

What deliverability actually tells you

Delivery and deliverability are related, but they are not the same result. Delivery means the receiving server accepted a message. Deliverability describes where that accepted message ultimately appears: the primary inbox, another tab, a junk folder, or somewhere the customer never notices it.

No single dashboard number can explain that placement on its own. A useful deliverability review combines technical acceptance, bounce patterns, complaints, engagement, sending consistency, and the quality of the audience. Treat the signals as a system rather than chasing one benchmark.

1. Start with the audience, not the email

The strongest subject line cannot rescue a disengaged list. Build the campaign around people who have a clear reason to hear from you, and narrow the segment when the message is only relevant to part of your audience.

Start by tracing every recipient back to a clear source. A product signup, checkout opt-in, event registration, or preference form creates context you can use. An old spreadsheet with uncertain origins creates risk you cannot solve with better copy.

  • Exclude unsubscribed, suppressed, bounced, and complained contacts.
  • Prioritize people who have opened, clicked, purchased, or signed up recently.
  • Avoid sudden jumps in sending volume, especially from a new domain.
  • Make sure the segment matches the promise made when each person subscribed.
  • Remove role addresses, obvious typos, and contacts whose source you cannot verify.
  • Separate newly acquired audiences from established, consistently engaged subscribers.

Build an engagement policy before you need one

Decide what inactive means for your business before a campaign is on the calendar. A weekly newsletter and an annual renewal reminder should not use the same window. Define meaningful activity, choose when to reduce frequency, and decide when a contact should leave regular campaigns entirely.

A re-engagement message can be useful when it offers a real choice: continue, receive less email, or leave. It should not become a permanent loop that keeps mailing people who have shown no interest.

2. Check the technical foundation

Authentication tells receiving providers that Email Bump is authorized to send on your behalf. Before scaling volume, confirm that SPF and DKIM pass, your From address uses the authenticated domain, and DMARC is configured with a policy appropriate for your sending program.

  • SPF identifies the systems allowed to send for your domain.
  • DKIM attaches a signed identity that receiving servers can validate.
  • DMARC defines how receivers should handle messages that fail alignment checks.
  • A branded tracking domain keeps links recognizable and aligned with your identity.
  • A monitored reply-to address gives customers and support teams a reliable path back.

Authentication records should be verified after every provider or DNS change, not only during initial setup. A record can be syntactically valid and still fail to align with the domain customers see in the From address.

3. Match volume to your reputation

A new domain or sending stream has little history. Introduce volume gradually, beginning with the people most likely to recognize and engage with the message. Consistency gives mailbox providers a clearer signal than a quiet month followed by an enormous launch.

If volume must increase, grow it in measured steps and watch the response at each stage. Slow down when hard bounces, complaints, or unusual deferrals rise. A warm-up plan is not a fixed calendar; it is a feedback loop.

  • Start with recent, high-intent subscribers and customers.
  • Keep daily volume predictable instead of alternating between silence and spikes.
  • Separate marketing and transactional streams so one does not destabilize the other.
  • Pause expansion when negative signals change materially.

4. Make the message worth opening

Write a subject line that accurately previews the email. The body should fulfill that promise quickly, with one clear primary action. Avoid hiding the unsubscribe link or relying on a single large image to carry the entire message.

  • Use a descriptive subject line instead of manufactured urgency.
  • Balance useful copy with lightweight, optimized images.
  • Include a plain-text version and meaningful link text.
  • Proof every merge field and test the destination of every link.
  • Make the sender identity, purpose, and primary action understandable without images.
  • Keep the preference and unsubscribe experience easy to find and use.

5. Test the inbox experience

A preview inside an editor catches only part of the experience. Send the real message through the real sending path to test accounts at the mailbox providers your audience uses. Check desktop, mobile, dark mode, blocked images, long preview text, and the plain-text alternative.

Testing is also where operational mistakes surface. Confirm that the From and reply-to addresses are correct, personalization has fallbacks, links use the intended tracking domain, and the unsubscribe action works without requiring a login.

01 / Sender checkDoes the From name match what subscribers expect?
02 / Mobile checkIs the useful part visible before the subject truncates?
03 / Content checkDoes the email still make sense with images disabled?
04 / Action checkDo the CTA, reply-to, and unsubscribe paths all work?

6. Watch the first signals

The work is not over at send. Watch delivery, bounce, complaint, and click signals as they arrive. A sudden change is most useful when you see it early enough to pause, investigate, and protect the next campaign.

Read metrics in context. A higher open rate can reflect stronger interest, but privacy features and automated scanning make it an imperfect measure. Clicks, replies, conversions, complaints, and unsubscribes help explain whether the campaign was both wanted and useful.

  • Investigate hard bounces by source and acquisition date.
  • Compare complaint and unsubscribe patterns across segments and message types.
  • Look for provider-specific deferrals or sudden delivery changes.
  • Record the audience, volume, content, and timing so the next send has a baseline.
  • Suppress permanent failures immediately and review repeated temporary failures.

When a campaign underperforms

Avoid changing everything at once. First confirm authentication and delivery events, then compare the audience and volume with recent successful sends. Next review acquisition source, engagement age, content, and provider-level patterns. A controlled diagnosis preserves the evidence you need to find the real cause.

The final pre-send checklist

  • The audience source and consent are clear.
  • Suppressions and engagement rules are applied.
  • SPF, DKIM, and DMARC alignment are healthy.
  • The planned volume is consistent with recent sending.
  • The subject, preview text, and body make the same honest promise.
  • Personalization, links, reply handling, and unsubscribe behavior were tested.
  • Someone is responsible for watching delivery and engagement after launch.