Email Deliverability

Quick answer / Definition

What it is: Email deliverability measures how many of your sent emails are accepted by recipients' mail systems and reach a recipient mailbox (inbox or spam). It is different from opens or clicks because it tracks delivery success at the mail-server level.

What it describes: The success of message acceptance and basic placement (delivered vs bounced), and is commonly used by ecommerce teams to estimate whether messages will ever have a chance to be read.

Where it’s used: By email marketers, deliverability specialists, and ecommerce owners to diagnose campaign performance, onboarding flows, and retention messaging.

Why it matters: If deliverability is low, no optimization of subject lines or creative can reach customers—resulting in lost revenue, worse customer experience, and inefficient acquisition and retention spend.

Why it matters for ecommerce

• Revenue: Marketing and transactional emails (welcome, cart recovery, reorder) drive measurable orders; poor deliverability reduces the audience that can convert.
• Conversion funnel: Emails are often the highest-ROI channel for repeat purchases; delivery failures shrink the top of that funnel.
• Customer acquisition & retention: New-customer onboarding and retention sequences depend on deliverability to build lifetime value (LTV).
• Profitability: Wasted sending costs, lower ROI on paid acquisition (if nurtured lists don’t receive messages), and higher support costs when transactional emails fail.
• Customer experience: Failed order confirmations or password resets directly harm trust and increase friction.
• Decision-making: Teams need accurate deliverability diagnostics to know if a campaign's poor performance is creative or technical.

What is Email Deliverability?

Email deliverability is the practical, technical measure of whether messages you send are accepted by recipient mail servers and land in a mailbox. It includes successful SMTP acceptance and any post-acceptance placement (inbox vs spam) as separate but related concerns.

What it includes:

• SMTP acceptance by the recipient's mail server (server returns a 250 OK).
• Post-acceptance placement signals such as inbox vs spam folder (often tracked via seed lists or third-party tools).
• Bounce handling (hard and soft) and suppression lists maintained by your ESP.

What it excludes:

• Opens, clicks, and conversions — these are engagement metrics that depend on deliverability but are not deliverability themselves.
• User behavior after delivery (e.g., whether a recipient reads or deletes the email).

When teams use it: before major campaigns, when onboarding new IPs or domains, after sudden drops in opens/clicks, or when complaints and bounces spike.

What a high or low value signals:

• High deliverability: mail servers accept your messages and you likely have correct authentication, healthy list hygiene, and reasonable sending patterns.
• Low deliverability: problems with authentication (SPF/DKIM/DMARC), high bounce/complaint rates, spam-trap hits, or poor sender reputation.

Formula / Calculation

Email deliverability is usually expressed as a percentage. A common operational formula is:

Deliverability rate = (Accepted messages / Sent messages) x 100

Where:

• Sent messages = emails your ESP tried to deliver (includes those later bounced).
• Accepted messages = emails accepted by recipient mail servers (SMTP 250 response).

Step-by-step numeric example:

1. Sent messages = 100,000
2. Bounces (hard) = 5,000; Soft bounces later retried and accepted = 3,000
3. Accepted messages = Sent - hard bounces = 95,000
4. Deliverability = (95,000 / 100,000) x 100 = 95%

Note: inbox placement rate is different and measures how many delivered messages land in the primary inbox vs spam; it requires seed testing or mailbox provider (MBP) tools and isn’t directly measured by the SMTP accept/deny status.

How it works (practical process)

1. Authenticate the sender

   What happens: You publish SPF, DKIM, and a DMARC policy so recipient servers can validate your sending domain. What you measure: DNS records validation and DMARC reports. Why it matters: Authentication reduces the chance mail is rejected or flagged as spoofing.

2. Send at controlled volumes and cadence

   What happens: ESPs and IP warming processes throttle sends for new IPs/domains. What you do: Gradually increase send volume and monitor bounces/complaints. Why it matters: Sudden spikes trigger reputation filters; steady ramps build trust.

3. List hygiene and segmentation

   What happens: Remove invalid addresses, suppress known hard bounces and spam traps. What you measure: Bounce rates, complaint rates, engagement scores. Why it matters: High-quality lists reduce rejections and improve sender reputation.

4. Monitor deliverability signals

   What happens: Track SMTP acceptance, complaint (spam) rates, unsubscribes, and seed inbox placement. What you measure: Delivered %, inbox placement %, and MBP feedback loop data. Why it matters: These signals tell you whether technical or content changes are needed.

5. Troubleshoot and iterate

   What happens: If acceptance drops, you investigate IP/domain reputation, authentication, and content triggers. What you do: Test subject lines, template images, or segmentation while fixing technical issues. Why it matters: Rapid fixes reduce revenue loss and protect long-term sending ability.

Key components / factors that affect deliverability

• Authentication (SPF, DKIM, DMARC): Incorrect or missing records increase rejection and spam placement risk.
• IP and domain reputation: History of complaints, spam-trap hits, and sending volume patterns drive mailbox provider trust.
• List quality and source: Purchased lists, scraped addresses, or stale opt-ins increase bounces and spam complaints.
• Bounce and complaint rates: High hard-bounce or spam-complaint rates lower reputation and acceptance.
• Engagement signals: Opens, clicks, replies and forwarding influence inbox placement at major providers that use engagement-based filtering.
• Content and formatting: Spammy language, excessive images, large attachments, or broken links can trigger filters.
• Sending cadence and volume: New IPs/domains need warming; sudden spikes can trigger blocks.
• Feedback loops and unsubscribes: Ignoring feedback loop data (reports when a user marks mail as spam) is harmful.
• Seasonality and campaigns: Holiday spikes and promotions change engagement; poor segmentation during spikes can raise complaints.

Example: Ecommerce scenario showing impact

Scenario: A DTC brand with a list of 100,000 opted-in subscribers runs a sale email. Average order value (AOV) = $75. Typical campaign conversion from click = 3%. Click-to-open rate (CTOR) = 12%. Expected open rate based on delivered mail = 18%.

Case A — deliverability at 85%:

• Sent = 100,000
• Delivered = 85% × 100,000 = 85,000
• Opens = 18% × 85,000 = 15,300
• Clicks = CTOR 12% × 15,300 = 1,836
• Orders = 3% × 1,836 ≈ 55 orders
• Revenue = 55 × $75 = $4,125

Case B — deliverability improves to 95% (after fixing authentication and list hygiene):

• Delivered = 95% × 100,000 = 95,000
• Opens = 18% × 95,000 = 17,100
• Clicks = 12% × 17,100 = 2,052
• Orders = 3% × 2,052 ≈ 62 orders
• Revenue = 62 × $75 = $4,650

Impact: An improvement from 85% to 95% deliverability increased campaign revenue by $525 (≈12.7% uplift) in this example. For repeatable flows (welcome, cart recovery), the cumulative impact is larger over time.

Benchmark / What is a good deliverability rate?

There is no single universal benchmark because deliverability depends on sender history, industry, list source, geography, and mailbox provider. However:

• Operational target: many teams aim for high acceptance (delivered) rates above 90% for established senders. This is a practical target, not a universal rule.
• Inbox placement: inbox placement (primary inbox vs spam) varies more and must be measured with seed tests; a 90% acceptance rate can still have poor inbox placement.

Remember: acceptable rates differ by context. A new IP will have different expectations than a 5-year-old sender with stable engagement.

How to improve / Optimize email deliverability (prioritized)

1. Fix authentication first (highest impact)

   What to change: Publish correct SPF and DKIM records, and implement a DMARC policy (monitor mode before enforcement). Why it works: Authentication proves your messages are legitimate and reduces rejections and spoofing flags. How to implement: Work with your DNS host and ESP; test with online DMARC/SPF checkers and review DMARC aggregate reports. What to monitor: SMTP acceptance rate, DMARC reports, and decreases in hard bounces.

2. Improve list hygiene and segmentation

   What to change: Remove hard bounces immediately, suppress non-engaged users (90+ days of zero opens), and avoid purchased lists. Why it works: Reduces bounces and complaint rates which improve reputation. How to implement: Use your ESP to automate suppression and segment by engagement recency and frequency. What to monitor: Bounce rate, complaint rate, and engagement by segment.

3. Warm IPs and domains carefully

   What to change: Gradually increase sending volume for new IPs/domains and prioritize highly engaged recipients first. Why it works: Mailbox providers watch volume and reputation; a ramped approach builds trust. How to implement: Follow a daily volume ramp schedule and monitor acceptance closely. What to monitor: Delivery rate, rejection messages, and placement from seed testing.

4. Segment by engagement and tailor content

   What to change: Send different content and cadences to highly engaged vs. dormant subscribers. Why it works: Higher engagement improves reputation and inbox placement. How to implement: Create engagement-based segments (e.g., last 30/90/180 days) and run re-engagement flows with lower frequency and clear opt-out. What to monitor: Open, click, and complaint rates per segment.

5. Monitor feedback loops and complaint sources

   What to change: Process ISP feedback loop reports and unsubscribe signals quickly. Why it works: Removing complainants prevents further reputation damage. How to implement: Configure feedback loops where available and auto-suppress complaining addresses. What to monitor: Complaint rate and downstream account suspensions.

6. Test inbox placement and content

   What to change: Use seed lists and placement tools to see inbox vs spam for major MBPs and test subject/content variations. Why it works: Identifies provider-specific issues and content triggers. How to implement: Run weekly seed tests and A/B subject/content tests for problem segments. What to monitor: Inbox placement by provider and deliverability over time.

Best practices

• Always implement SPF, DKIM, and a DMARC policy in monitor mode before enforcement.
• Remove hard bounces immediately and suppress addresses that soft-bounce repeatedly.
• Segment sends by recent engagement—send highest volumes to most engaged users first when warming new IPs.
• Use double opt-in for new subscribers to reduce invalid addresses and spam complaints.
• Keep sending cadence predictable; avoid sudden, large spikes in volume.
• Monitor complaint rates (via ESP and ISP feedback loops); aim to keep them well below 0.1% for most lists.
• Run seed inbox-placement tests across major ISPs (Gmail, Outlook, Yahoo) before large campaigns.
• Keep message templates lean: avoid large attachments, excessive images, or misleading subject lines.
• Document and follow an IP/domain warm-up plan when changing providers or sending infrastructure.
• Track deliverability alongside revenue per recipient to prioritize fixes that move business metrics.

Common mistakes to avoid

• Ignoring authentication errors: Why it happens: DNS changes or copy/paste mistakes. Harmful because it leads to rejections or spoofing flags. Correct approach: Validate SPF/DKIM records and use DMARC reports to find misconfigured senders.
• Confusing delivery with inbox placement: Why it happens: Teams look only at accepted/sent metrics. Harmful because messages can be accepted but land in spam. Correct approach: Use seed testing and placement tools to measure inbox vs spam.
• Over-sending to unengaged users: Why it happens: Desire to reach maximum recipients. Harmful because it increases complaints and lowers reputation. Correct approach: Suppress or re-engage dormant users with targeted flows first.
• Purchasing lists or ignoring acquisition source: Why it happens: Growth pressure. Harmful because purchased lists contain traps and uninterested users. Correct approach: Opt for organic and verified capture methods (double opt-in).
• Failing to monitor provider-specific issues: Why it happens: One-size-fits-all reporting. Harmful because Gmail, Yahoo, and Outlook score senders differently. Correct approach: Track deliverability by ISP and adjust sending patterns/content per ISP findings.

Email Deliverability vs related concepts

Inbox placement vs Email deliverability

• Inbox placement: The share of delivered emails that land in the primary inbox rather than spam; measured with seed lists or placement tools.
• Email deliverability: The rate at which messages are accepted by recipient servers (delivered) and thus have a chance to be placed in inbox or spam.
• Key difference: Deliverability answers "did the mail reach the mailbox server?" Inbox placement answers "did it land in inbox or spam?"

Bounce rate vs Email deliverability

• Bounce rate: Percentage of messages rejected (hard or soft). Direct contributor to lower deliverability.
• Email deliverability: Broad acceptance metric; deliverability = 100% - hard bounces (ignoring other rejections).
• Key difference: Bounce rate is a primary cause of poor deliverability, but deliverability encompasses successful acceptance beyond just bounce counts.

Sender reputation vs Email deliverability

• Sender reputation: A score/mailbox provider signal based on historical complaints, bounces, spam-trap hits, and engagement.
• Email deliverability: The outcome (acceptance/placement) influenced heavily by sender reputation.
• Key difference: Reputation is the leading cause; deliverability is the observed effect.

When should you track email deliverability?

Who: Email marketers, growth teams, ecommerce founders, and operations who've delegated sending to ESPs. If your business relies on email revenue or transactional flows, track it.

Stage of growth: Track from day one if you send order confirmations or password resets. As you scale (tens of thousands+ recipients) add more formal monitoring and seed tests.

Frequency: Monitor daily for acceptance/bounce and complaint rates; run seed placement tests weekly or before major campaigns.

Segments to analyze: New subscribers, welcome flows, reactivation segments, transactional messages, and large promotional sends. Also analyze by ISP (Gmail, Outlook, Yahoo) and by sending IP/domain.

Metrics to view alongside deliverability: Inbox placement rate, open/click rates by segment, bounce rate, complaint rate, unsubscribe rate, and revenue per recipient.

Related ecommerce metrics

• Inbox placement rate: Shows whether delivered mail lands in inbox or spam—directly affects opens.
• Bounce rate (email): Hard bounces reduce deliverability and must be removed promptly.
• Complaint rate: Spam complaints harm sender reputation and future deliverability.
• Open rate: Engagement signal that influences provider filtering but must be interpreted after deliverability checks.
• Click-through rate (CTR/CTOR): Measures recipient engagement after delivery; used to prioritize high-value segments.
• Revenue per recipient (RPR): Business metric tying deliverability improvements to monetary impact.
• Unsubscribe rate: Indicator of list relevance and a signal to providers if high.

FAQs

• What exactly does "email deliverability" measure?

  It measures whether an email you sent was accepted by the recipient's mail server (delivery) and, when tested, whether it landed in an inbox or spam folder (placement).

• How is deliverability different from open rate?

  Deliverability is about acceptance by mail servers; open rate is recipient engagement after acceptance. Low deliverability means fewer recipients can open mail, regardless of subject line quality.

• How often should I check deliverability?

  Check acceptance and bounce data daily; run seed placement tests weekly or before large campaigns and after infrastructure changes.

• Why did deliverability drop suddenly?

  Common causes: authentication issues, a spike in bounces or complaints, sending from a new/warm IP without ramping, or hitting a spam-trap. Inspect bounce/rejection messages and DMARC reports first.

• Can I fix deliverability quickly?

  Some fixes (correcting SPF/DKIM, removing hard bounces) can show improvement in days; reputation recovery and inbox placement can take weeks depending on severity.

• Do transactional emails have different deliverability needs?

  Yes—transactional emails typically require stricter reliability and should be sent from authenticated subdomains or dedicated IPs to isolate reputation from marketing sends.

• Is buying a new dedicated IP a quick solution?

  Only sometimes. A new IP needs careful warming and good sending patterns; moving to a dedicated IP without warming or list hygiene can make deliverability worse.

• How do I measure inbox placement?

  Use seed lists or a placement-testing service that delivers identical emails to accounts across major ISPs and reports inbox vs spam placement.