One campaign. Every domain. No single point of failure.
Every campaign is spread across the client’s brand-matched sending domains, so no one domain carries the volume, a warming domain contributes its share, and a domain that is slowed hands its load to the others without anyone noticing. Each recipient gets one domain — and their From address, links and landing page all resolve to it.
Putting a whole campaign on one domain is a reputation bet you never have to make.
A receiver judges a sending domain partly on what it sends and partly on how much arrives at once. One domain carrying a fifty-thousand-message campaign presents a fifty-thousand-message spike, and a bad afternoon — a stale segment, a subject line that draws complaints — lands entirely on that one domain. Recovery takes weeks, and every campaign the client sends in the meantime is slowed.
Spread the same campaign across four or five brand-matched domains and each presents a fraction of the volume, each builds its own reputation, and a bad afternoon costs one domain a fraction of the damage while the others carry on. The client’s campaigns keep going out.
The largest senders in the world do exactly this, with engineers to run it. SendTo does it for every client by default — and does something most large senders cannot: every recipient’s message is fully aligned to the one domain that carries it.
Every domain gets its share
When a campaign launches, the dispatch engine assigns each recipient to one of the client’s domains in rotation, weighted by what each domain has earned. Established domains take equal shares; a warming domain takes what its ceiling allows; a slowed domain’s share is redistributed. The report shows the result per domain, so you can see the balance working.
- Round-robin assignment at dispatch
- Warmup ceilings and slowdowns respected automatically
- Per-domain results on every report
Aligned per recipient
Assigning a domain is half the job. For it to help, everything the recipient sees must agree: the From address uses that domain, the message is signed by it, the tracking links are served on it, and the landing page — published once — is served on it for that recipient. One brand, one domain, end to end, for every single message.
- From, signature, links and page on one domain per recipient
- Landing pages published once, served on every domain
- Tracking hostnames provisioned on each domain automatically
Pin when you want control
A VIP list on the best-established domain. A test cohort on a new one. A client who wants a particular address on a particular campaign. Pin a recipient or a group to a domain and the balancer works around it, and the report shows the pins.
- Pin recipients to a domain per campaign
- Balancer distributes the rest around the pins
- Pins visible on the report
● Automated 12.1%
Scanners never count as customers.
| Variation | Subject line | Human opens | Clicks |
|---|---|---|---|
| A · winner | Your six-month check-up is due, {first name} | 33.2% | 7.4% |
| B | Six months already? Let’s keep that smile on track | 29.6% | 6.2% |
Campaigns that finish, on domains that keep their reputation.
A rough send stays a private matter
A slowed domain hands its share to the others. The client sees a campaign that completed, never an incident report.
Reputation that compounds
Several domains each building clean history is several times the resilience of one — and every campaign adds to all of them.
An answer to “why”
Delivered per domain, on every campaign. When a client asks what happened, the explanation is already on the screen.
One client had a rough send — an old list, our mistake. One domain got slowed. Nobody outside our team ever knew, because the other three just carried it.
Questions
Is the split always even?
Between established domains, yes. A warming domain takes the share its ceiling allows and a slowed domain hands its share to the others. The report shows the actual split.
Does a recipient notice different From addresses?
A recipient sees one From address on every message they receive from a campaign, on a domain that reads as the client. Rotation happens across recipients, never within one.
Does the landing page need publishing per domain?
No. Publish once. The platform serves the page on whichever domain a recipient was assigned, so the click always lands on the domain that sent the email.
Can I balance across more domains?
Yes. Add managed domains to the client account and the balancer includes them as they warm.
Can I turn it off?
Pin recipients to a domain wherever you want control. Balancing is on by default because it is the safe default.
Spread the load. Keep the alignment.
Every client gets balanced, aligned sending across their domains from the first campaign.
No contract · Cancel any time · Explore everything before you pay