Start with a small group of subscribers who expect your messages. Increase volume as the results justify it, with clear conditions for slowing down.
Positive warm-up results are useful evidence, but they cannot tell you how every subscriber will respond to your next campaign.
A client’s question
A client preparing to introduce production traffic asked how to move from encouraging warm-up results to real campaigns: should they control daily volume, hourly volume, or both? And what should happen when their campaign schedule produces quieter days?
This article draws on that exchange and describes a recommended approach. Identifying details and account-specific volumes have been removed.
1. Choose the audience before choosing the growth rate
Before recommending a starting volume, I want to understand who will receive the first campaign.
Do they recognize the sender? Did they subscribe to this type of message? Is the content still relevant to them?
A technically clean setup does not answer those questions. Neither does a successful seed test. The test tells us what happened in the mailboxes observed under those conditions. Production adds the responses of actual subscribers.
Adobe’s transition guidance recommends beginning with engaged subscribers and tailoring the volume plan to the sender’s circumstances. Adobe: Volume.
For this transition, I recommend looking at recent, meaningful signals: useful clicks, replies, purchases, or other relevant activity. An open alone is usually not enough for me to select a recipient for the first group.
The objective is to learn how a suitable audience responds before expanding the campaign.
2. Set a starting volume and a sending pace
Review both the daily total and the sending pace. The same daily volume can produce a very different pattern when sent in a short burst instead of distributed over several hours.
Google recommends low initial volume to engaged users, gradual increases, and a consistent sending rate rather than bursts. It also advises monitoring server responses and reducing volume when bounces or deferrals appear. Google: Email sender guidelines.
My approach is to define the first group, how the send will be distributed, and when the next decision will be made. Review traffic by receiving provider and include other sending activity using the same infrastructure.
I do not recommend using the same starting count or daily growth percentage for every sender. The plan needs context: recent sending history, shared or dedicated IPs, audience composition, and the changes being introduced.
During the first test, keep avoidable changes to a minimum. If you simultaneously change the audience, content, and volume, a change in performance becomes harder to interpret.
3. Decide what would make you slow down
Decide what would make you hold, reduce, or pause sending before the first campaign goes out.
| Decision | What to review |
|---|---|
| Increase cautiously | Stable delivery signals and a real audience response consistent with the campaign’s purpose |
| Hold and investigate | Conflicting signals, insufficient observations, or an unexplained change in performance |
| Reduce or pause the affected traffic | Rising deferrals, rejections, complaints, or a significant deterioration that needs investigation |
Using this decision framework, define the actual limits before launch, based on the provider’s requirements and the account’s baseline.
For Gmail, Postmaster Tools adds useful context, but its data is delayed and may be incomplete at low volume. Missing data is not proof that everything is healthy. Google: Postmaster Tools dashboards.
Read operational evidence alongside business results: useful clicks, replies, and conversions. An accepted message, a seed placement result, and a purchase answer different questions.
What about quieter days?
You do not need to create a production campaign on a day when there is no relevant message to send.
Instead, document the normal cadence and account for it in the transition plan. A program sending a few times a week needs a plan that reflects that pattern. Assess dedicated-IP requirements separately, and revisit the role of any seed activity as production develops.
Treat the next increase as a decision supported by evidence. Review the results before increasing, even when the original schedule calls for a larger send.
Email Deliverability Is Earned, Not Configured.
Before your next volume increase, write down three things: who receives the campaign, how the send will be paced, and which signals would make you stop.
Which signal has made you hold or reverse a ramp-up in your own email program?
If you need to accelerate your warm-up process, I recommend using InboxAlly.
Disclaimer: Some of the links here are affiliate links. You’ll pay the same price, but I may earn a small commission. This helps me keep testing and recommending only the tools I genuinely trust and use every day.
