How to Warm Up a Dedicated Klaviyo IP: A Week-by-Week Schedule That Actually Works
A conservative six-week warming schedule, per-ISP thresholds, and how to catch a bad warming before it compounds.
Warming a dedicated Klaviyo IP takes four to eight weeks of disciplined sending. Start at roughly 50 messages per day to your most engaged subscribers, double volume every 48 to 72 hours if engagement holds, and watch Gmail Postmaster Tools and Microsoft SNDS daily. Cut back immediately if complaint rate rises or spam placement appears. Warming mistakes take six to twelve weeks to recover from, so slow is faster than aggressive.
IP warming is the process of gradually ramping volume on a new dedicated IP to build a positive reputation at every major mailbox provider. Done correctly, it produces a dedicated IP that delivers your mail reliably for years. Done badly, it produces a dedicated IP that Microsoft, Gmail, or Yahoo view with suspicion, and recovering from that first impression is harder than starting from scratch.
This article walks through the full Klaviyo IP warming schedule, what to monitor during each phase, and how to handle the specific mistakes that derail most warming attempts.
Why IP Warming Matters
A brand-new IP has no reputation. Mailbox providers know nothing about its sending history. Until they see a consistent pattern of engaged recipients over time, they treat the IP with suspicion. This is not a flaw in the system; it is the correct default behaviour when an unknown IP suddenly starts sending large volumes of commercial mail.
The providers want to see three things during warming:
- Consistent daily volume, ramped predictably.
- Engagement from recipients (opens, clicks, replies, no complaints).
- Authentication that is stable and aligned across every message.
If you send a huge first-day volume, engagement drops (not because the mail is bad, but because a proportion of any large audience will inevitably be cold), and the provider's filtering treats the IP as suspicious. That initial impression can take months to recover.
Pre-Warming Checklist
Before day one of warming, everything else must already be correct. Warming cannot compensate for broken authentication or a dirty list.
- DKIM records are configured for the sending domain and verified in Klaviyo.
- SPF includes Klaviyo and passes for the sending domain.
- DMARC policy is published (p=none is acceptable for warming, tighten later).
- Sending subdomain is dedicated or, at minimum, isolated from existing shared-pool sending.
- Your list is segmented so you have a clear pool of highly engaged subscribers (opened or clicked in the last 30 days).
- Gmail Postmaster Tools access is set up for the branded sending domain (this gives you domain reputation; note that Klaviyo-owned IPs are not visible to you in GPT).
- Seed-test accounts at Gmail, Outlook/Hotmail, Yahoo, and iCloud are prepared so you can check inbox placement daily during warming.
- You have agreed with Klaviyo's deliverability team on their role during warming. They have SNDS and IP-level GPT access that you do not, and they can share status when asked.
- A rollback plan exists (what do you do if warming goes sideways on day 5).
If any of these are not in place, fix them before starting. Warming with a rushed setup is the most common cause of failed warming.
The Standard Klaviyo Warming Schedule
This is a conservative six-week schedule. Aggressive senders sometimes compress this to four weeks. Aggressive is not better; it just increases the chance of errors you cannot recover from.
Week 1: Introduction
Daily volume: 50 to 200 messages.
Audience: Only your top 10% most engaged subscribers (opens and clicks in the last 14 to 30 days).
Content: Low-promotional. Transactional-style messages if possible. Welcome flows and order confirmations are ideal.
What to watch: Bounce rate under 2%, complaint rate under 0.05%, Gmail Postmaster Tools showing "High" or "Medium" domain reputation for your branded sending domain, and inbox placement at seed accounts staying at or above 90%.
What to avoid: Any bulk promotional campaigns, cold segments, re-engagement flows.
Week 2: Steady Ramp
Daily volume: 200 to 1,000 messages, increasing by roughly 50% every 48 hours.
Audience: Top 20 to 30% of your list by engagement.
Content: Gradually introduce promotional content, keeping quality high.
What to watch: Same metrics as week 1, plus status reports from Klaviyo's deliverability team on SNDS signals for your pool or dedicated IP. Microsoft-side visibility for you as a customer remains mostly bounce codes and seed tests.
What to avoid: Volume spikes beyond the planned ramp. If a Monday send would exceed the schedule, split it across two days.
Week 3: Real Volume Begins
Daily volume: 1,000 to 10,000 messages.
Audience: Top 50% of your list by engagement.
Content: Full promotional content is acceptable, but keep subject lines and calls-to-action conservative.
What to watch: Gmail Postmaster domain reputation should be "High." Seed-test Junk placement at Microsoft should be near zero. Any degradation is a warning to slow down. Ask Klaviyo's deliverability team for SNDS status on your IP if anything feels off; they can see what you cannot.
What to avoid: Adding new segments faster than the ramp allows. If you planned to double volume on day 15, but reputation dipped on day 14, hold volume flat for 72 hours before resuming the ramp.
Week 4: Expanding Reach
Daily volume: 10,000 to 30,000 messages.
Audience: Top 70% of your list.
Content: Normal promotional cadence.
What to watch: Reputation indicators should be fully stable. Click and conversion rates should match or exceed your historical shared-pool performance.
What to avoid: Sudden large campaigns. Keep volume smoothing in place.
Weeks 5 and 6: Final Ramp
Daily volume: Reaching your normal operating volume.
Audience: Full list, minus any genuinely dormant subscribers.
Content: Standard promotional program.
What to watch: Transition to routine monitoring. Daily seed tests at the major providers. Weekly Gmail Postmaster Tools domain review. Periodic check-ins with Klaviyo's deliverability team for IP-level signals.
By the end of week six, the IP should have a stable reputation across Gmail, Microsoft, and Yahoo, and you should be sending at your full operational volume with delivery rates matching or exceeding what you saw on shared pools.
Per-ISP Volume Thresholds
Mailbox providers apply different thresholds during warming. Approximate daily sending limits that work for most senders:
Gmail: Can accept higher volume earlier than Microsoft. Day 1 of 100 to 500 messages is usually fine if engagement is strong.
Yahoo and AOL: Similar tolerance to Gmail, but more sensitive to complaint rate. Keep complaint rate under 0.1% during warming.
Microsoft (Outlook.com, Hotmail, Live): Most restrictive during warming. Volume spikes at Microsoft produce SNDS "Yellow" or "Red" more quickly. Ramp slower here than at other providers.
Apple (iCloud.com, me.com, mac.com): Generally permissive, but reputation builds slowly. Apple filtering decisions often lag other providers by a week or two.
The practical implication: during warming, watch Microsoft most carefully. If Microsoft reputation is healthy, the others usually follow.
What to Watch Each Day
During warming, daily monitoring is not optional. The specific metrics:
- Bounce rate. Should be under 2% on engaged segments.
- Complaint rate. Should be under 0.05% during warming, under 0.1% in steady state.
- Gmail Postmaster Tools domain reputation for your branded sending domain. Should be "High" or "Medium." (IP reputation is not visible to Klaviyo customers; it is Klaviyo's to track.)
- Microsoft bounce codes in Klaviyo's logs. Any rise in S3150, 5.7.1, or 5.7.511 is a warning sign.
- Spam and Junk placement rate at seed accounts. Should be near 0% at major ISPs throughout warming.
- Engagement rate. Open and click rates should match expectations for your most engaged segments.
If any indicator moves in the wrong direction for more than 48 hours, pause the volume ramp and investigate. A short pause adds a few days to warming. A missed warning sign adds months of recovery.
Common Warming Mistakes
Sending to the full list on day one. This is the most common warming mistake. "I already have engaged subscribers, why restrict volume?" Because mailbox providers do not know you are sending to engaged subscribers, and the first impression of a dedicated IP that sends 100,000 messages on day one is a spammer. Reputation built from that impression is slow to rebuild.
Warming through transactional-only traffic. Mailbox providers can distinguish transactional from promotional, and a reputation built purely on transactional volume does not transfer to promotional sending. Include promotional mail during warming, just to your most engaged subscribers.
Ignoring a reputation dip. If Gmail Postmaster drops from High to Medium on day 10, the correct response is to hold volume flat and investigate. Pushing through the dip is the fastest way to turn a minor warming issue into a six-week recovery.
Warming multiple IPs simultaneously. If you have acquired multiple dedicated IPs for different sending streams, warm them sequentially, not in parallel. Your operational capacity to monitor and respond is the limiting factor.
Not setting up a rollback path. What do you do if warming fails? "Go back to shared IP" is a rollback, but it has to be configured and tested in advance. Klaviyo's shared pool will not automatically re-accept you.
When Warming Goes Wrong
Signs that warming is failing:
- Bounce rates at Microsoft exceed 5% or bounce codes include S3150.
- Gmail Postmaster drops to Low and stays there for 48 hours.
- Complaint rate exceeds 0.2%.
- Spam placement appears at seed tests.
- Click rates at a specific ISP drop meaningfully below your historical baseline.
If warming is failing, the right response is usually:
- Pause volume immediately. Go back to day-1 levels.
- Review the last 72 hours of sending for specific patterns (segment, content, ISP distribution).
- Identify and suppress the cohort that generated the negative signal.
- Resume warming at lower volume, with stricter engagement filtering, over a longer timeline.
The instinct to "push through" a warming problem by sending more almost always makes it worse.
Get visibility before you change anything
Whether your warming is on track depends on signals you cannot see from inside Klaviyo. Pick your entry point. No sales call on any of them.
Klaviyo Posture Report
Public signals only. DNS, SPF, DKIM, DMARC, blocklist checks, and domain reputation for your sending domain. No API key needed.
- Full auth posture (SPF / DKIM / DMARC)
- Blocklist and domain reputation scan
- PDF in your inbox within an hour
Klaviyo Trial Audit
Connect your Klaviyo API key. We combine your sending data with Gmail Postmaster, seed tests, and blocklist status to tell you whether a warming process is on track. Written audit returned in 24–48 hours.
- Warming health check (not just public DNS)
- Bounce code and engagement analysis
- Actionable per-ISP recommendations
Klaviyo Autonomous AI Email Intelligence
Engagor's AI continuously monitors your warming and post-warming program: reputation signals per ISP, bounce-code patterns, engagement decay, anomalies. You get plain-English findings and a recommended action, not another dashboard to interpret.
- Continuous monitoring across Gmail, Microsoft, Yahoo, and Apple
- Alerts on reputation drift during and after warming
- Month 1 full AI audit included (standalone value €2,500)
- Cancel anytime after month 1
Frequently asked questions
How long does IP warming take for Klaviyo?
A conservative Klaviyo IP warming schedule takes four to eight weeks. Six weeks is a reasonable default. Faster is possible for experienced senders with very engaged lists, but failed warming attempts take six to twelve weeks to recover from, so the downside of rushing outweighs the speed benefit.
What is a good Klaviyo IP warmup schedule?
Start at 50 to 200 messages per day to your top 10% most engaged subscribers. Double volume every 48 to 72 hours if engagement holds. Ramp through weeks of gradually broader audiences, reaching full volume by week six. Monitor Gmail Postmaster Tools and Microsoft SNDS daily throughout.
Can I skip IP warming in Klaviyo if my list is engaged?
No. Engagement is necessary but not sufficient. Mailbox providers do not know your list is engaged until they see a consistent pattern of positive engagement over time. A large first-day send from a new IP triggers suspicion regardless of how engaged the audience is.
How many emails can I send per day during Klaviyo IP warming?
Depends on the week and the provider. Week 1: 50 to 200 total. Week 2: 200 to 1,000. Week 3: 1,000 to 10,000. Week 4: 10,000 to 30,000. Full operational volume by week 5 or 6. Microsoft is typically the most restrictive, so use Microsoft volume as your ceiling guide.
What happens if I do IP warming wrong in Klaviyo?
A failed Klaviyo IP warming produces an IP with negative reputation at one or more providers. Recovery takes six to twelve weeks of disciplined sending, during which delivery will be worse than on a shared pool. Common failure modes: bounced back to Klaviyo shared pool, requiring re-integration, or months of below-baseline delivery while reputation rebuilds.
Does Klaviyo provide IP warming automation?
Klaviyo's deliverability team provides guidance during warming and can help with schedule design, but the ongoing volume ramp and audience selection is your responsibility. Some third-party tools provide automated warming ramps, but the quality varies. Engagor's approach is monitoring rather than automation, so the schedule is under your control with continuous visibility into whether it is working.
How do I check if my Klaviyo IP warming is working?
Watch Gmail Postmaster Tools domain reputation daily for your branded sending domain (should stay High or Medium), Microsoft bounce codes in Klaviyo (S3150 or 5.7.x rising is a warning), complaint rate (under 0.1%), bounce rate (under 2%), and seed-test inbox placement at major providers (should be near 100%). Because Klaviyo owns the sending IPs, SNDS and IP-level GPT are not directly accessible to you; Klaviyo's deliverability team can share those signals on request. Any sustained negative movement in the indicators you can see is a warning to slow down.