Dedicated IP for Email Sending and When a Shared Pool Wins

A client of mine was sending 9,000 receipts and newsletters a month when their email provider offered a dedicated IP for an extra 30 dollars. It sounded like a promotion: your own address, your own reputation, nobody else's spam dragging you down. Six weeks later their Gmail inbox placement had dropped from roughly 94 percent to the low 70s, and the upgrade was the cause.

A dedicated IP for email sending is a real tool, but it only pays off at a certain volume and with a certain discipline. Below is how I decide whether a sender needs one, what a warmup actually looks like day by day, and the mistakes that turn a reputation upgrade into a slow deliverability leak.

What a Dedicated IP for Email Sending Actually Changes

Every message you send leaves from an IP address, and mailbox providers keep a running score for that address. On a shared pool, your mail goes out alongside hundreds of other customers of the same provider. Their behaviour and yours are blended into one score.

On a dedicated IP, the score belongs to you alone. That cuts both ways. A clean sender no longer pays for a neighbour's purchased list, but a messy sender loses the cushion that a large, well policed pool provides. Your domain reputation still matters on both setups, and these days Gmail and Outlook weigh the domain at least as heavily as the IP. If your authentication is shaky, fix that first; the walkthrough on why authentication records still confuse website owners covers SPF, DKIM and DMARC in the order you should check them.

The Volume Threshold Most Providers Will Not Tell You

Mailbox providers need a steady stream of mail to form an opinion about an IP. Too little volume and the address looks cold every time you send, which earns throttling and spam folder placement.

Monthly volume	Recommended setup	Why
Under 50,000	Shared pool	Not enough daily mail to keep an IP warm
50,000 to 150,000	Shared, or dedicated if sending daily	Works only with consistent daily volume
Over 150,000	Dedicated IP	Enough signal for a stable, independent score
Over 1 million	Two or more dedicated IPs	Split transactional and marketing streams

My client at 9,000 a month was nowhere near the line. Their mail arrived in bursts on Tuesday mornings, and between bursts the IP went quiet. Gmail treated each Tuesday like a stranger knocking on the door.

Why "Get Your Own IP" Is Often Bad Advice

Forum threads repeat the same line: shared IPs are dirty, serious senders go dedicated. I disagree for most small teams, for three reasons.

Good pools are policed. Reputable providers suspend abusive accounts within hours. Their shared pools often carry a better score than a new dedicated IP will reach in its first two months.
Shared pools absorb your bad days. One import of an old list with 4 percent bounces barely moves a pool sending millions of messages. On your own IP, that same mistake shows up in Postmaster Tools the next morning.
Your domain carries reputation anyway. Moving IPs does not reset a damaged domain. If your problem is complaints, a new address just gives the problem a new home.

The honest case for a dedicated IP is control and isolation at scale, not a quick fix for spam placement. If messages are already landing in junk, start with how deliverability works and why messages land in spam before spending money on infrastructure.

A Warmup Schedule That Survives Real Traffic

A new IP has no history, so you build one by sending small, engaged volumes and increasing them gradually. The schedule below is what I use for a sender heading toward 200,000 messages a month.

Days 1 to 3: 500 messages a day, only to people who opened or clicked in the last 30 days.
Days 4 to 7: 1,000 to 2,000 a day, still the most engaged segment.
Week 2: double every second day if bounces stay under 1 percent and complaints under 0.1 percent.
Weeks 3 and 4: add the 31 to 90 day engagement segment and reach roughly 70 percent of full volume.
Week 5 onward: full volume, with the least engaged contacts sent last and least often.

Keep the shared pool carrying the rest of your traffic during warmup. Most providers let you split sending by percentage, which avoids a hard cutover that would force cold mail through a cold address.

Separating Transactional and Marketing Streams

Once you are large enough for one dedicated IP, the next useful step is usually a second one. Password resets, receipts and shipping notices get opened at 60 percent or more and almost never draw complaints. Newsletters and promotions get opened at 20 to 30 percent and collect the occasional spam click.

Putting both on one address means a bad campaign can delay a customer's password reset. I give transactional mail its own IP and, ideally, its own subdomain such as a "mail" subdomain for receipts and a "news" subdomain for marketing. Each subdomain then signs with its own DKIM key, so a reputation dip on one stream stays contained.

What to watch after the split

Check Google Postmaster Tools and Microsoft SNDS weekly for each IP. A transactional IP that shows anything below "High" reputation deserves immediate attention, because those messages are the ones customers actually wait for.

Costs and Hidden Work Behind the Upgrade

The line item is usually 20 to 80 dollars a month per IP, depending on the provider. The real cost is attention. Somebody has to own reverse DNS, check blocklists, read bounce reports and pause campaigns when complaint rates climb. On a shared pool, the provider's deliverability team quietly does a share of that work.

Budget at least an hour a week for monitoring once you go dedicated. If no one on the team will reliably do it, the shared pool is the safer choice even above the volume threshold.

Frequently Asked Questions

Can I move back to a shared pool after buying a dedicated IP?

Yes. Most providers let you switch with a support request or a settings toggle. Move gradually over a week rather than all at once, and keep sending to engaged contacts first so the pool sees clean traffic from your domain.

Does a dedicated IP help with Apple Mail Privacy Protection?

No. Apple's proxy loads images regardless of your IP, which inflates open rates for everyone. Use clicks and replies as your engagement signal when building warmup segments, not opens.

How long does a dedicated IP stay warm if I pause sending?

Reputation starts fading after about two weeks of silence and is largely gone after 30 days. If you pause for a month, plan a short rewarm at reduced volume before your next big send.

The Practical Takeaway

Look at your last three months of sending. If you average under 50,000 messages a month or send in irregular bursts, stay on a well run shared pool and put your effort into list hygiene and authentication. If you send over 150,000 a month on a steady daily rhythm, a dedicated IP gives you control worth paying for, provided you warm it slowly and assign someone to watch it every week. More setups are compared in the email infrastructure section.