Klaviyo Email Deliverability: Warmup and Recovery System

Faisal HouraniFaisal Hourani· Founder & eCommerce Growth Strategist
November 2, 202612 min read

Is your store leaking revenue?

Find out exactly where you're losing sales — takes 2 minutes.

Find Your Revenue Leaks

A fresh domain and a tanked one follow the same decision tree. Here is where yours sits on it.

Marketer typing on a laptop in a bright home office

What Is Klaviyo Email Deliverability?

Deliverability is not a setting. It's a trust score.

Klaviyo email deliverability is the measure of whether your campaigns land in the inbox, the promotions tab, or spam, driven by sender reputation signals like authentication, engagement, and complaint rate. Google now classifies anyone sending 5,000 or more emails a day to personal Gmail accounts as a "bulk sender," subject to stricter authentication rules enforced since February 2024.

Most stores treat deliverability as something Klaviyo handles for them. It doesn't. Klaviyo gives you the sending infrastructure; your account's reputation is built send by send, and it can be destroyed in a single bad campaign. In the audits WebMedic runs on Shopify DTC accounts, every serious deliverability problem traces back to one of two root causes: a botched warmup, or broken authentication. Fix those two, and the rest is maintenance.

Which Klaviyo Deliverability Path Do You Need?

Don't guess. Route yourself first.

A single decision tree routes every Klaviyo account to the right fix: check blacklist status, then authentication, then engagement data, then whether you're currently in spam. Each branch leads to one of three systems, warming from scratch, recovery, or static-list sampling, and running the wrong one wastes weeks.

Before touching the warmup schedule or the recovery blitz below, answer these four questions in order. Each one eliminates an entire branch of wasted work.

Question If yes If no
Is the domain blacklisted? (Check MX Toolbox) New domain, likely new mailbox and sender name. Warm from scratch. Continue to next question.
Is authentication correct and propagated? (3 CNAME + TXT + DMARC) Continue to next question. Fix auth first. Do not send until propagation is confirmed.
Do you have engagement data to build dynamic segments? Continue to next question. Verify and re-import your list, then use static-list sampling.
Are you currently landing in spam? Run the 42-day recovery blitz. Run the 8-stage warmup.

That table is the whole post's navigation. Everything below is one of those four branches, done properly.

Is Your Sending Domain Correctly Authenticated?

Authentication is table stakes, not the finish line.

A Klaviyo branded sending domain needs three CNAME records, one TXT record, and a DMARC policy set to "relaxed" during setup, giving you SPF and DKIM. Klaviyo's own documentation calls these baselines, not guarantees: a fully authenticated domain can still land in spam if the warmup or hygiene behind it is wrong.

Three separate things carry a sending reputation, and fixing one while ignoring the other two is the most common recovery mistake WebMedic sees:

  1. The branded sending domain (a subdomain like send.yourbrand.com), which holds your DNS auth records.
  2. The sender mailbox, the actual inbox behind your "from" address. It has its own, independent reputation.
  3. The default sender name, the display name recipients see. It carries risk too.

If your domain is in a bad state, so is your mailbox and so is your sender name. Remediating a tanked account usually means replacing all three together, not just the domain.

One setup detail matters more than it should: Klaviyo offers a dynamic connection (it manages your DNS records automatically) and a static connection (you place the records yourself). Use static during setup and recovery. Dynamic connections on branded subdomains have a documented history of DNS records failing to propagate cleanly, and a static connection removes that failure mode entirely. Confirm propagation in MX Toolbox before your first send; don't assume it.

What Is the Klaviyo 8-Stage Warmup Schedule?

Warm a new domain like a new engine, not a burner account.

The Klaviyo 8-stage warmup runs eight mapped campaigns (DW1 through DW8) across three phases, starting at 100-250 recipients and expanding toward 70-80% of your sending capacity. Every stage is scaled to your list size, not a fixed headcount, and advancing early is the single most common cause of spam-foldering WebMedic finds in account audits.

Treat the volumes below as ramp shapes to scale against your own list, not literal targets:

Phase Audience size Engagement window Content rule
1. Initial Ignition 100-250, then ~500 Engaged last 3-5 days Plain text. No promos, no discounts.
2. Building Authority ~1,000 → 1,500 → 2,000 → 2,500 Engaged last 7-15 days Educational content, light brand stories.
3. Graduated Expansion Toward 70-80% of your upper limit, in steps (5k → 7.5k → 10k → 15k...) Engaged-30 (hold here) Full content mix, still no heavy promos until week 4.

Two details separate a warmup that works from one that stalls. First, no promotions or discounts before roughly week four; you earn the right to sell by proving value first. Second, leave at least 24 hours between sends so the prior day's opens and clicks register before you make the next decision. Klaviyo's Smart Send and Gradual Send features (available from roughly 12,000 profiles, and earlier respectively) spread volume across hours instead of firing it all at once; use Gradual Send on your first one or two campaigns especially.

How Wide Should Your Engaged Segment Be During Warmup?

Never widen past day 30 while you're still warming.

The engaged-segment ladder runs 3, 5, 7, 15, 30, 60, 90, 120, and 180 days, but warmup only ever uses 3 through 30. The 60-180 day windows are win-back segments, unlocked only after warmup completes, typically 60-90 days into established engagement-based sending.

Build each "engaged last N days" segment as a dynamic segment on opened-or-clicked email, not a static list. Dynamic segments update automatically as contacts enter and exit; static lists only change when you manually import or export, which is exactly the kind of unpredictability that damages a warming domain.

The preferred execution method sends one email creative multiple times to progressively wider, non-overlapping slices of the engaged base, using include and exclude rules in Klaviyo's campaign builder so no one is mailed twice:

Send Include segment Exclude segments
1 Engaged last 3 days —
2 Engaged last 5 days Engaged last 3
3 Engaged last 15 days Engaged last 3, 5
4 Engaged last 30 days Engaged last 3, 5, 15

This clears four warmup sends off a single piece of creative inside roughly 72 hours, with every send landing on contacts already proven to engage. Once warmup is done, continue sending on engagement, never a full-list blast, and widen gradually to 60, 90, 120, and 180 days to win back lapsed contacts.

When Can You Advance to the Next Warmup Stage?

The gate matters more than the calendar.

A warmup stage only advances when open rate holds above 40%, ideally above 50%, and the account has accumulated roughly 10,000 cumulative sends with opens still holding. Below that gate, the rule is explicit: stop, reassess, and deploy a narrower strategy. Never push forward through bad metrics.

That last line is worth repeating because it's the rule most accounts break. A founder watching a warming domain under pressure to "just get the emails out" will widen the audience on a weak open rate, and that single decision is often what tips a warming account into spam. If a stage doesn't clear the gate, the fix is to narrow, not to push through and hope the next send recovers.

Does this sound like your store? Find out where you're leaking revenue — take the free Revenue Score. 3 minutes. Free. No pitch.

Patch cables plugged into a network panel in a data center

How Does the 42-Day Recovery Blitz Work?

A tanked domain gets the same warmup, just faster and under tighter rules.

The 42-day recovery blitz runs the same 8-stage warmup across three two-week phases: stabilization, rebuilding, and reintroduction. Four rules hold for the entire six weeks without exception: spam complaints under 0.1%, open rate above 50%, daily domain-reputation checks in Google Postmaster, and continuous DNS propagation checks.

The phases, in order:

  • Weeks 1-2, Stabilization. Restart sending to only your most-engaged contacts. If the domain is badly tanked or blacklisted, replace all three reputational entities together: new branded domain, new sender mailbox, new default sender name. Place a temporary static connection and confirm propagation before any send.
  • Weeks 3-4, Rebuilding. Expand systematically toward the engaged-30-day segment, advancing only on passing gates.
  • Weeks 5-6, Reintroduction. Bring back the 60 and 90-day engaged segments to recapture lapsed-but-valuable contacts.

A common myth deserves a direct answer: spinning up a new domain does not automatically fix anything. A new domain resets your entire sending history and forces the full, slow rebuild, which is the worst option for an established 7-9 figure brand bleeding revenue in spam. Reserve a new domain for genuinely blacklisted accounts, where the alternative (waiting out a blacklist) can take weeks to months and is outside your control. One caveat on timeline: high-revenue brands in a hurry can turbo this to roughly three weeks with third-party mailbox-warming tool support, but the reliable, repeatable path the source behind this framework recommends is four to six weeks. Don't compress it without that tooling in place.

What If You Don't Have Engagement Data Yet?

A brand-new list needs a different, slower method.

Static-list sampling is the fallback for brands with no engagement history to build dynamic segments from. The list must be verified through an email-checking tool, re-imported with consent confirmed, then sent to six to eight increasing sample sizes, with each round required to clear a 45% open rate before expanding.

The sequence matters and skipping steps is what turns a pre-launch list into a deliverability problem before the brand even sends its first real campaign:

  1. Export the raw list.
  2. Run it through a verification tool to strip bounces and invalid addresses.
  3. Re-import only the cleaned contacts, with consent to receive marketing confirmed.
  4. Build increasing sample sizes from the cleaned list, each one excluding everyone already mailed in a prior round.

Never buy or scrape a list. A purchased or scraped list has typically been resold many times over, and it will send a fresh domain straight to spam on contact. If a sampling round comes in under the open-rate bar, stop and narrow rather than expanding to the next size.

Close-up of a smartphone screen displaying an email inbox

What Should You Monitor Daily, Weekly, and Monthly?

Deliverability decays quietly if nobody is watching.

Four numbers gate every Klaviyo deliverability decision: spam complaints under 0.1%, bounce rate around 0.2%, delivery rate around 99.8%, and a Klaviyo deliverability score that stays sticky in the 80s to 90s across a trailing 365-day view, not just a single snapshot.

Metric Healthy range Action if breached
Open rate Above 40%, ideally above 50% Stop expanding, narrow to most-engaged, check auth and hygiene
Spam complaint rate Below 0.1% Stop, narrow audience, review content and consent
Bounce rate Around 0.2% Auto-suppress bounces immediately, audit contact source
Delivery rate Around 99.8% Investigate bounces and authentication
Klaviyo deliverability score 80s-90s, sticky over 365 days Contract sending, re-audit auth and hygiene

Four tools do the actual checking: MX Toolbox for DNS, SPF, DKIM, and blacklist status (free, and worth checking weekly even on a healthy account); Google Postmaster Tools for domain reputation, used daily during any recovery; GlockApps for inbox-placement testing; and mail-tester for a single-send spam-score sanity check before a real campaign goes out. One sequencing note: Postmaster and GlockApps only become reliable once you're sending at natural volume. Early in a warmup, trust Klaviyo's own in-platform opens, clicks, and bounces instead; sparse Postmaster data at low volume is noise, not signal.

Also worth naming directly: sources disagree on what a "healthy" Klaviyo deliverability score looks like. One WebMedic-reviewed framework treats 80s-90s as the healthy band; a separate Klaviyo account-audit framework treats roughly 65-75+ as healthy for the accounts it reviewed. Both are real operator thresholds, just calibrated against different account samples. Read your own score's trend over the 365-day view rather than anchoring to either number in isolation.

Team of young professionals in a business meeting reviewing data

Do Gmail and Yahoo's Bulk Sender Rules Change Anything for Malaysia and Singapore Stores?

The rules are global, but the sending patterns that trip them are regional.

Both Google and Yahoo require SPF, DKIM, and a published DMARC policy for any sender crossing roughly 5,000 emails a day to personal accounts, enforced since February 2024. A Shopify store sending a single blast to its full list during Raya, 11.11, or CNY, on a domain that has never been warmed, is exactly the pattern these rules were built to catch.

Person reading a security-notice email on a laptop screen

Google's sender guidelines define a bulk sender as anyone sending 5,000 or more emails a day to personal Gmail accounts, counting all traffic including transactional mail. Yahoo's sender requirements mirror this closely: authenticate with SPF and DKIM, and publish a DMARC policy of at least p=none. Neither requirement is Southeast Asia-specific, but the failure mode is. A fast-growing Malaysian or Singaporean Shopify brand with a seasonal spike calendar, Raya, 11.11, 12.12, CNY, is the exact profile most likely to cross 5,000 sends in a single day on a domain that was never warmed for that volume, because the campaign calendar was built around the sale date, not the domain's readiness.

The fix is the same warmup system above, just timed earlier. If a major sale sits 6-8 weeks out and your domain hasn't sent consistently at volume before, start the 8-stage warmup now rather than discovering the gap the week of the sale. Sending from a dedicated branded subdomain, not your root domain, also isolates a bad sale-day send from affecting your primary domain's reputation.

Frequently Asked Questions

What causes poor Klaviyo email deliverability?

The two most common root causes are a botched warmup, where sending volume widened faster than open-rate metrics could support, and broken DNS authentication, missing or unpropagated SPF, DKIM, or DMARC records. Sending to cold or static lists and skipping suppression flows are close behind, but authentication and warmup pacing explain most of what WebMedic finds in Shopify account audits.

How long does it take to warm a new Klaviyo sending domain?

A full 8-stage warmup to roughly 10,000 cumulative sends with opens holding above 40-50% typically takes several weeks, scaled to how large your engaged base already is. A recovery blitz for an already-tanked domain runs on a fixed 42-day (six-week) schedule, with a faster roughly 3-week option available only with third-party mailbox-warming tool support.

What's a healthy Klaviyo deliverability score?

Operators disagree slightly by account sample: one WebMedic-reviewed framework treats 80s-90s as healthy, while a separate account-audit framework treats 65-75+ as acceptable. Rather than anchoring to a single number, check your score's trend over Klaviyo's 365-day expanded view; a sustained downward trend matters more than the absolute figure.

Should I switch Klaviyo sending domains if my open rates drop?

Not automatically. A new domain resets your entire sending history and forces a full, slow rebuild, which usually costs an established brand more revenue than re-warming the existing domain. Reserve a new domain for a domain that is actually blacklisted, checkable for free in MX Toolbox; everything short of blacklisting is better handled with the 42-day recovery blitz.

How many emails can I send before Gmail or Yahoo treats me as a bulk sender?

Google classifies any sender crossing roughly 5,000 emails a day to personal Gmail accounts as a bulk sender, counting all traffic including transactional email, with stricter authentication enforced since February 2024. Yahoo applies similar authentication requirements at scale. A seasonal campaign (Raya, 11.11, CNY) can cross that threshold in a single blast on a domain never built for that volume.

Keep Reading

Share this article

#klaviyo email deliverability #klaviyo warmup #email deliverability shopify #klaviyo domain authentication #sender reputation

Ready to grow?

Find out exactly where your store is leaking revenue.

Answer a quick set of multiple-choice questions and we'll pinpoint your biggest revenue leaks — and whether we can help plug them.

Find Your Revenue Leaks

Free · No obligation · 2 minutes

Faisal Hourani

Faisal Hourani

Founder & eCommerce Growth Strategist

19 years building for the web, 9+ focused on ecommerce. Faisal founded WebMedic in 2016 to help DTC brands fix the conversion problems that hold them back. He has worked with brands across Malaysia and Singapore — from first-store launches to 8-figure scaling.

Ready to Boost Your Conversion Rates?

Book a quick strategy call. We'll analyze your store, identify your biggest revenue leaks, and show you exactly how we can plug them.

Book Your Strategy Call

Score your store

Find Your Revenue Leaks