Customer.io's Daily Ramp Automates Domain Warming. Set It to the 1.5x Rule, Not "Exponential"

Watch a Falcon 9 climb and, about a minute in, the flight commentator calls out "max-q". It's the moment of maximum dynamic pressure—the point where the force of the atmosphere against the rocket peaks as it accelerates through thick low-altitude air. Push too hard through it and the aerodynamic load can overstress the vehicle.

So the rocket does something that looks backwards. In the seconds before max-q, the engines throttle down. Once it's safely through, they throttle back up and the ascent continues at full power. You go slow through the most dangerous stretch on purpose, then accelerate once the risk has passed.

Warming a sending domain works the same way. The dangerous stretch is the start: a new domain with no reputation, sending into inbox providers that don't yet trust it. You send a little, prove you're legitimate, and only then push the volume up. Until 30 March 2026, doing that in Customer.io meant babysitting a spreadsheet. Now there's a setting that does the throttling for you.

This post is about that setting—Daily ramp—and the one decision that makes or breaks it. Customer.io's newsletters help says Daily ramp increases your volume "exponentially". Its domain-warming guide says never grow faster than 1.5x a day. Both are Customer.io's own words, and they can pull in opposite directions. I'll show you what Daily ramp does, how to set it so it respects the 1.5x rule, and when it's the right tool. I'll also cover the limit the name hides: it warms newsletters only, and volume alone won't rescue a domain with poor engagement or broken authentication.

Domain warming, the manual chore Daily ramp replaces

Domain warming is the process of methodically adding email volume to a new domain over several days or weeks, so inbox providers learn to trust it. That definition comes straight from Microsoft's own sender guidance, and every major provider works the same way.

Here's why it matters. When a new mail stream appears, Gmail, Yahoo and Microsoft have no history to judge it by. They can't tell a legitimate new sender from someone trying to hijack a domain's reputation, so they treat sudden volume as suspicious and respond with throttling, filtering, or outright blocking. Send 50,000 emails on day one from a domain with no track record and a big share of them land in spam, or nowhere.

There's a catch specific to Customer.io. When you set up email sending, you send from a Customer.io-managed subdomain like cio123456.yourdomain.com. That subdomain is new to inbox providers even if your root domain has years of history behind it, so the warm-up applies to every new sending setup, established brand or not.

The old way to warm it was manual. You'd send a small batch, note the number in a spreadsheet, increase it a little the next day, check your reputation, and repeat for weeks. In Customer.io specifically, that meant building a separate newsletter for each step of the schedule. Reaching a normal sending volume can take four to eight weeks, so that's a lot of newsletters and a lot of babysitting. Warming has only shown up on this blog as one step inside a bigger ESP migration, never as a job in its own right. Daily ramp is what turns it from a job into a setting.

What Daily ramp actually does

Daily ramp is a rate-limiting option for newsletters that increases your send volume a little more each day, automatically, over a period you choose.

You'll find it when you schedule a newsletter. On the Schedule tab, turn on Limit send rate and you get two choices: Fixed rate or Daily ramp. Fixed rate sends a constant number of messages per minute, hour or day. Daily ramp starts low and climbs.

Three settings define the ramp. Starting Daily Volume is how many messages go out on day one, and the docs suggest something low, like 100. Target Daily Volume is where you want to end up, usually your normal broadcast size. You don't warm past your real sending volume, so if you send to 30,000 people, you warm to 30,000 and stop. Number of Days is how long the ramp lasts, up to 60. Customer.io raised the maximum newsletter send window to 60 days when it shipped Daily ramp on 30 March 2026, specifically to leave room for gradual warming. The daily volume rises each day until the ramp ends or everyone has received the message, and sends are spread across the day rather than fired all at once.

Two things the feature does quietly are worth knowing. It previews the projected volume as a chart before you commit, and it warns you if the ramp doesn't look optimised. And if you pause a newsletter mid-ramp, it resumes where it left off instead of skipping days.

The contradiction to resolve: "exponential" versus the 1.5x rule

Set the ramp to grow no faster than 1.5x a day, and lean gentler than that. Here's the tension you're resolving.

Customer.io's newsletters page tells you to "choose Daily ramp to exponentially increase your send volume over multiple days". Its domain-warming guide, in the same documentation set, says the opposite in spirit: "Volume increases should not exceed 1.5x the previous stage." In plainer terms, the same guide adds: "Never exceed 1.5x the previous stage's daily volume in a single day." One page says exponential. The other caps how steep the exponential can be.

They reconcile, because "exponential" only describes the shape of the curve, not its steepness. A ramp that grows 1.5x a day is exponential. So is one that grows 1.14x a day. The word tells you nothing about whether you're inside the safe zone... the growth rate does. Your job is to pick a growth rate at or under the 1.5x ceiling.

And 1.5x is a ceiling, not a target. Read Customer.io's documented warm-up schedule closely: it steps from 100 to 150 to 225 to 340 to 500, and each of those steps is held for two to three days before the next increase. That's 1.5x every stage, not every day, which works out to roughly 1.14x to 1.22x of actual daily growth. The schedule reaches about 29,000 a day at stage 15, on days 43 to 45.

So put a real number on it. To warm a 30,000-person list, the schedule Customer.io publishes takes about 45 days. That's the pace to copy: set Number of Days near 45 for that target. Don't pick the two-week sprint that would have you multiplying by the full 1.5x every single day, with no margin for a bad signal. Use the preview chart, watch for the "not optimised" warning, and if in doubt, add days. A ramp that's too slow costs you a little time. One that's too fast costs you the domain.

When to use it, and when not to

Use Daily ramp for two jobs: warming a fresh sending domain, and pushing a large newsletter to a list you haven't mailed in a while. Reach for something else outside that.

The first job is a new domain. A daily ramp that mirrors the warm-up schedule is exactly what the schedule was built for, and automating it saves you from hand-building twenty newsletters. The second is a big send to a re-engaged or long-dormant list. Mailing 200,000 people who haven't heard from you in six months looks, to an inbox provider, a lot like a cold start. Ramping the volume gives providers time to see the engagement before the full blast lands.

Now the limits, because the feature name hides them. Daily ramp is a newsletter setting. It is not available on campaigns or transactional sends. Warm your domain with newsletters while blasting transactional email through the same subdomain at full volume and you've undermined the whole exercise, because the ramp only governs the newsletter you attached it to. For campaign-based warming, Customer.io's own suggestion is manual: start a new low-volume campaign every few days to follow the schedule by hand.

Two more cases sit outside Daily ramp's reach. You can't use it when you're sending in each recipient's timezone; that combination isn't allowed, so you'd set a fixed hourly rate instead. And if your volume is stable and you're not warming anything, Daily ramp has no job to do... Fixed rate is the tool for holding a steady send speed to protect downstream systems.

Why volume alone won't save you

Ramping volume is necessary, but it's not sufficient. Two other things decide whether you reach the inbox, and Daily ramp touches neither: engagement and authentication.

Start with engagement, because it's the signal providers weigh most heavily. Customer.io's guidance is blunt: "Engagement is the primary signal providers are evaluating." The schedule tells you to send early stages only to people who opened or clicked in the last 14 to 30 days. Long-dormant contacts, those 120 days or more without engagement, come in last, at no more than 5% of a day's volume. Ramp the volume perfectly while mailing a stale, unengaged list and your reputation still sinks. When list hygiene is the problem, the ramp won't fix it... that's a job for suppression and frequency discipline.

Then authentication: the records that prove an email genuinely came from you, namely SPF, DKIM and DMARC. Microsoft's guidance lists authentication alongside engagement and complaints as a core input to sender reputation. A gentle ramp does nothing for a domain that fails those checks, and the volume curve can be flawless while the mail still bounces. If authentication is where you're weak, that's its own project: we've written the Customer.io authentication audit for Microsoft's sender rules and a complete deliverability guide that covers SPF, DKIM, DMARC and reputation together.

One number ties it together. During warm-up, Customer.io says to keep your Gmail spam-complaint rate below 0.08% and to pause the moment it hits 0.10%. That's not only a warming threshold... it's the ceiling every Customer.io sender now works under. Volume ramping buys you a clean on-ramp. Engagement and authentication are what keep you on the road.

Frequently asked questions

Q: How do I warm up a new sending domain in Customer.io?

Send a small volume first and increase it gradually over several weeks, following Customer.io's published warm-up schedule, which starts at about 100 emails a day and grows by no more than 1.5x per stage. The fastest way to run that schedule is a newsletter with Daily ramp, which increases the volume for you each day. Start with your most engaged subscribers and hold at each level for two to three days before stepping up.

Q: What is Daily ramp on a Customer.io newsletter?

Daily ramp is a rate-limiting option that increases a newsletter's send volume a little more each day, over a period you set. You choose a Starting Daily Volume, a Target Daily Volume and a Number of Days, and Customer.io raises the daily send towards the target across that window. It shipped on 30 March 2026 and is built for domain warming.

Q: Where do I find Daily ramp in Customer.io?

Create a newsletter, go to the Schedule tab, and turn on Limit send rate. You'll see two rate types: Fixed rate and Daily ramp. Pick Daily ramp and set your starting volume, target volume and number of days.

Q: How fast can I safely increase my email send volume?

No faster than 1.5x the previous day's volume, and ideally gentler. Customer.io's domain-warming guide states it plainly: "Never exceed 1.5x the previous stage's daily volume in a single day." Its own schedule is more conservative still, stepping up about 1.5x every two to three days rather than every day.

Q: Does Daily ramp increase volume "exponentially" or by 1.5x—which is right?

Both, read correctly. "Exponential" describes the shape of the curve; the 1.5x rule limits how steep that curve can be. A ramp growing 1.5x a day and one growing 1.14x a day are both exponential, and only one rides the ceiling. Set your Number of Days so the daily growth stays at or below 1.5x.

Q: Does Daily ramp warm my whole domain or just newsletters?

It warms your sending domain's reputation, but it only controls the volume of the newsletter you attach it to. Reputation is built at the domain level, so a well-paced newsletter helps the whole subdomain. But if you're pushing campaigns or transactional email through the same subdomain at full volume, Daily ramp doesn't throttle those, and they can undo the warming.

Q: Will ramping volume fix my deliverability on its own?

No. Volume pacing is necessary but not sufficient. Inbox providers weigh engagement most heavily, and they check authentication, so a perfectly paced ramp to an unengaged list, or from a domain with broken SPF, DKIM or DMARC, still lands in spam. Ramp the volume, but fix engagement and authentication too.

Q: Daily ramp versus fixed-rate limiting—which should I use?

Use Daily ramp when you're warming, because it increases volume over days. Use Fixed rate when you want a steady send speed, a constant number of messages per minute, hour or day, to protect downstream systems or pace a one-off large send you're not using to warm. Fixed rate holds; Daily ramp climbs.

Q: How many days should I set for the ramp?

Match Customer.io's published schedule for your target volume. To warm to about 30,000 a day, that schedule takes roughly 45 days, so set Number of Days near there rather than a shorter sprint that forces the full 1.5x jump daily. The maximum is 60 days. Preview the chart and add days if Customer.io warns the ramp isn't optimised.

Q: Can I use Daily ramp when sending in a recipient's timezone?

No. If you schedule a newsletter to send in each recipient's timezone, you can set a fixed rate per hour or minute, but not a daily ramp. Choose one or the other: timezone-accurate delivery, or an automated ramp.

Q: What happens if I pause a newsletter mid-ramp?

It resumes where it left off. Customer.io picks up based on how many messages have already gone out, and it doesn't skip days in the schedule. You can also edit the rate limit while a newsletter is sending, which is useful for slowing down if you see deferrals or weak engagement.

Q: Do I need to warm a domain if my root domain is already established?

Yes. Customer.io sends from a managed subdomain like cio123456.yourdomain.com, and that subdomain is new to inbox providers even if your root domain has years of history. Warm every new sending setup, established brand or not.

Q: What should I watch during warm-up?

Watch your Gmail reputation, spam-complaint rate and bounce rate after each stage. Customer.io says to keep the Gmail spam rate below 0.08% and to pause at 0.10% or above, keep bounces under 2%, and hold your Gmail domain reputation at Medium or better. If any of those slip, hold at your current volume for a few days rather than pushing higher.

Sources

• Automate domain warming with Daily ramp for newsletters. Customer.io Release Notes, 30 March 2026.
• Safely warm up your sending domain. Customer.io Docs, updated 8 June 2026.
• Newsletters. Customer.io Docs, updated 15 June 2026.
• Warm-up process for marketing senders. Microsoft Learn, updated 9 October 2025.