The dedicated versus shared IP question moves real inbox placement, and most Klaviyo senders answer it backwards by treating a dedicated IP as a status upgrade. A dedicated IP helps a large, steady sender because it isolates your reputation from strangers, and it hurts a small or spiky one because a near-idle IP never earns the trust a shared pool already carries. The decision rests on three numbers you can measure this week: how much you send, how consistently, and how clean your list is. Get those wrong and a dedicated IP delivers worse than the pool you paid to leave.
Key takeaways
- Klaviyo puts most small and new accounts on shared IPs, where established senders keep the pool warm and Klaviyo removes harmful senders.
- A dedicated IP tends to pay off above roughly 100,000-300,000 sends a month at a steady weekly-or-more cadence, and rarely below that.
- The real cost of going dedicated is the 30 to 40 day warmup, not a line item on your invoice.
- Google treats 5,000 or more Gmail messages a day as bulk sending and expects spam complaints under 0.3%, ideally under 0.1%.
- Reputation isolation, not raw size, is the strongest reason to move: a dedicated IP puts your name alone on the reputation Google scores.
- Below the volume floor a dedicated IP usually delivers worse than the shared pool, because it never accumulates enough positive signal.
What a shared IP pool actually does for a small Klaviyo sender
A shared pool lends you reputation you have not earned yet. Your sends leave from IP addresses that dozens of other senders also use, so mailbox providers judge that address on the whole pool's behavior, not yours alone.
That is a gift when your own volume is small. Klaviyo assigns shared IPs to most new accounts and constantly monitors the pool, removing harmful senders, which is why Klaviyo notes most small businesses stay on shared IPs. Established high-volume senders in the same pool keep it warm and trusted, and an 8,000-contact store rides on that.
The cost is control. You don't set the pool's reputation, and a bad neighbor can dent it before Klaviyo evicts them. For a small sender that trade is almost always worth taking.
When the shared pool starts working against a large sender
The pool stops helping once your volume dominates it. When you send millions of messages a month, your own behavior is most of the signal on those IPs, so the pool's protective averaging no longer smooths anything for you.
Klaviyo makes the point directly: if you send high volumes at a regular frequency, you are effectively controlling the reputation in the shared pool anyway. At that scale the pool hands you the downside of shared infrastructure, exposure to neighbors, without much of the upside.
Two failure modes show up here. A neighbor's spam spike can drag your placement even though your list is clean, and you cannot fully separate one of your own brands or streams from another because they share the same addresses.
What send volume makes a dedicated IP worth the switch
A dedicated IP starts to make sense above roughly 100,000-300,000 sends a month, sent consistently. Below that, deliverability authorities and ESPs broadly agree a shared pool performs better, because a quiet dedicated IP cannot generate the steady positive signal mailbox providers want to see.
The clearest external marker is Google's bulk threshold. Google classifies anyone sending more than 5,000 messages a day to Gmail as a bulk sender and expects the Postmaster spam complaint rate to stay under 0.3%, ideally under 0.1%. Landing 5,000-10,000 Gmail messages on a normal send day, several days a week, is a reasonable floor for carrying your own IP.
Volume alone doesn't settle it. Use these profiles as a first read.
| Monthly send volume | Send cadence | Recommended setup |
|---|---|---|
| Under 100,000 | Any | Shared pool |
| 100,000-300,000 | Weekly or more, steady | Shared pool, revisit only to isolate brands |
| 300,000-1,000,000 | Weekly or more, steady | Dedicated IP becomes viable |
| Over 1,000,000 | Weekly or more, steady | Dedicated IP, often more than one |
| Any large volume | Spiky, a few big blasts | Shared pool |
Why consistency beats peak volume every time
A dedicated IP rewards rhythm, not size. Mailbox providers build trust from a stream they can predict, so a sender who mails a large engaged list every few days looks safer than one who goes silent for three weeks and then blasts a million messages.
The warmup encodes this. Klaviyo runs a dedicated IP warmup of about 30 to 40 days on a non-linear ramp, front-loading the most engaged subscribers and pushing most of the volume increase toward the end. It's the same engaged-first ramp you would apply when warming a new sending domain, and it breaks the moment your sending turns erratic.
After warmup the discipline doesn't stop. Klaviyo says holding a dedicated IP's reputation requires weekly or more frequent campaigns, so a brand that mails twice a month is a poor candidate no matter how large those two sends are.
What reputation isolation buys you, and what it costs
Isolation is the real reason to go dedicated, and it cuts both ways. On a dedicated IP your name alone sits on the reputation Google scores, so you own every gain and every mistake with no neighbor to blame or to lean on.
That reputation is graded. Google Postmaster Tools sorts senders into Bad, Low, Medium and High reputation bands based on spam reports and history, and a dedicated IP is where you can move that grade purely on your own behavior. On a shared pool you can do everything right and still inherit a neighbor's Low.
Isolation also lets you separate streams. A large operator running several brands or a risky win-back segment can put each on its own IP so one cannot poison the others, which connects to the wider question of sending domain models for multi-brand Klaviyo. The catch is that every isolated IP needs its own volume and its own warmup, so isolation multiplies the maintenance burden.
The list hygiene that has to be true before you move
A dedicated IP amplifies whatever your list quality already is, so clean the list before you switch, not after. The IP has no pooled reputation to hide behind, which means unengaged recipients, spam traps and hard bounces hit your reputation at full strength.
Set concrete gates first. Your Gmail spam complaint rate should sit well under the 0.3% ceiling and closer to 0.1%, your bounce rate should be low and stable, and your sends should be limited to subscribers who have opened or clicked inside a defined engagement window.
If you cannot hold those numbers on the shared pool, a dedicated IP will make them worse, because it strips away the averaging that was quietly protecting you.
A decision framework you can run in ten minutes
Score four inputs, and move only when the first three are strong. Volume and cadence decide whether a dedicated IP can stay warm at all, list hygiene decides whether you should trust it with your reputation, and isolation need decides whether the extra work pays for itself.
| Input | Stay on shared | Move to dedicated |
|---|---|---|
| Monthly volume | Under 100,000, or uneven | 300,000+ sent steadily |
| Send cadence | Monthly or sporadic | Weekly or more, year round |
| List hygiene | Spam rate near or above 0.3% | Spam rate under 0.1%, low bounces |
| Isolation need | One brand, one stream | Multiple brands or high-risk segments to separate |
If three of four point to move and none of the first three says stay, a dedicated IP is worth the warmup. If volume, cadence or hygiene says stay, fix that first.
What to watch after the switch
Never move to a dedicated IP to fix a deliverability problem, because it removes the safety net rather than repairs the cause. If your placement is already slipping on the shared pool, the fault is almost always list quality or content, and a dedicated IP inherits both.
Watch three things in the first 60 days: your Postmaster reputation band, your Gmail spam rate against the 0.1%-0.3% range, and whether your real send cadence holds the weekly minimum. A reputation that drifts toward Low, or a month where cadence slips, is the signal that you moved too early.
My default for a single-brand Shopify store under a few hundred thousand sends a month is to stay on the shared pool and spend the effort on engagement-gated sending instead. The senders who gain from a dedicated IP are the ones large and steady enough that they were setting their own reputation regardless, plus the multi-brand operators who need one brand's mistakes kept off another's mail.