Ramping Up Sending Volume

How reputation works on Tratto's shared sending pool, and how to ramp new volume without damaging it

IP warming is the practice of increasing email volume on a new IP gradually, so mail servers can build a reputation for it instead of treating a sudden flood as an attack.

On most plans you do not warm an IP, because you have no IP of your own. Sending goes over a shared pool that Tratto operates, and there is no per-workspace warming automation for it: nothing watches your volume or paces it for you. A dedicated IP is available on the Scale plan only, see If you have a dedicated IP. What follows is what you have to do on the shared pool, and it is not optional.

What this means for you

The pool's reputation is shared by every workspace sending through it. That cuts both ways:

  • You inherit a reputation you did not build. A new workspace does not start from zero the way a new dedicated IP does — the pool already has standing with the major mailbox providers.
  • You can damage a reputation that is not only yours. A bad list sent at volume raises the bounce and complaint rates the mailbox providers measure across the pool. The consequences land on every workspace on it, including yours.

So the ramp is still your job. It is just about your domain's reputation and your effect on the pool, not about an IP you own.

If you have a dedicated IP

A dedicated IP is included on the Scale plan only, one per workspace. It is enabled on request once the workspace sends at least 3,000 emails a day (each recipient counts as one, like the monthly quota). It is not available on other plans.

A new dedicated IP warms up automatically over about 45 days. During warm-up part of your mail keeps going out over shared IPs, and nothing is delayed or rejected because of warm-up. After warm-up, the IP's reputation depends only on your own sending.

Ramping New Volume

If you are about to send materially more than you have been sending — a first campaign to a list you imported, a migration from another provider, a seasonal peak — increase in steps rather than in one jump, and watch the metrics between steps.

A reasonable shape: start with a few hundred of your most engaged recipients, then roughly double per send while bounce and complaint rates stay in the bands below. Back off a step the moment they don't. There is no schedule that is right for every list; the metrics decide, not the calendar.

1. Start With Your Best Recipients

Send to your most engaged recipients first:

  • Customers who opened past emails
  • Internal team (guaranteed opens)
  • Beta users with high engagement

Avoid:

  • ❌ Cold lists
  • ❌ Purchased or scraped addresses
  • ❌ Addresses you have never mailed and cannot verify

2. Maintain List Quality

While ramping, every bounce matters:

  • Verify email addresses before sending
  • Remove bounced addresses immediately — Tratto suppresses them for you, and a contact moved to bounced or complained cannot be moved back
  • Remove unengaged addresses after 6 months

3. Monitor Metrics

Check analytics between steps:

curl "https://api.tratto.email/v1/analytics/summary?period=7d" \
  -H "Authorization: Bearer tratto_live_..."

Watch for:

  • Delivery rate staying 99%+ (good sign)
  • Bounce rate < 2% (good sign)
  • Complaint rate < 0.1% (critical)

Rates from this endpoint are percentages: 98.5 means 98.5%.

4. Send Consistently

Send regularly — daily if you can. Mailbox providers reward consistency:

✅ 100 emails/day, every day
❌ 7,000 emails Monday, then nothing for a week

Throttling Signs

If mailbox providers are throttling you, you'll see:

  • Delivery rate dropping below 95%
  • Soft bounces increasing
  • Slower send times

Action: stop increasing volume, hold at the last level that was healthy for a few days, then resume more gradually.


See Deliverability for authentication, content and list practices.


Edit this page on GitHub

Last updated on