It's Black Friday morning. Your marketing team sends the biggest promotion of the year to two million subscribers. An hour later, support tickets start piling up: customers can't log in because their password reset emails never arrived. Order confirmations are landing in spam. Nobody touched the transactional templates, so what happened?

The answer is almost always the same: both types of email were sent from the same infrastructure, and the promotional messages took the transactional emails down with it.

Keeping transactional and broadcast email on separate infrastructure is one of the simplest, highest-leverage deliverability decisions you can make. Here's why it matters and how to do it.

Two kinds of email, two very different jobs

Transactional email is triggered by something a single person did: signing up, resetting a password, placing an order, requesting a 2FA code. The recipient is expecting it, often waiting for it, and usually needs it within seconds.

Broadcast email (also called bulk, marketing, or promotional email) is sent by you to many people at once: newsletters, product announcements, sales, re-engagement campaigns. It's valuable (hopefully!), but nobody is staring at their inbox waiting for it.

Those differences show up in how mailbox providers like Gmail, Yahoo and Microsoft see each email type:

Transactional Broadcast
Trigger A user action Your schedule
Volume pattern Steady, one at a time Large spikes
Recipient expectation Expected, often urgent Optional, read when convenient
Typical engagement Very high opens, near-zero complaints Lower opens, more complaints and unsubscribes
Cost of a delay Locked-out users, lost orders, support tickets A campaign that underperforms

How one bad campaign takes down your transactional mail

Mailbox providers decide where your email lands largely on reputation. They track it against the signals they can see: your sending IP addresses, your sending domain, the domains in your DKIM signatures and return-path, and even the links in your content. When everything shares the same signals, everything shares the same reputation.

That's where the trouble starts. A few common ways broadcast mail can damage a shared reputation:

  • A stale list. A campaign to subscribers who haven't engaged in a year hits spam traps and invalid addresses.
  • A complaint spike. An aggressive promotion or an unexpected sending frequency drives up "report spam" clicks. Gmail and Yahoo expect bulk senders to keep complaint rates well below 0.3%.
  • A volume surge. Sending far more than usual in a short window looks like a compromised account and triggers throttling.
  • Content filtering. Promotional content, link shorteners or a flagged tracking domain can push messages toward spam.

Each of these is a recoverable problem for a newsletter, but it's a serious problem for a 2FA code. When providers start deferring or filtering mail from a shared IP or domain, they don't check which messages are "the important ones." Your receipts and login links get throttled and filtered alongside the campaign that caused it.

There's a queueing problem too. On shared infrastructure, a two-million-message send can sit in the same queue as a password reset. Even with perfect reputation, that reset might wait behind the campaign for minutes. To a user stuck on a login screen, that's the same as it never arriving.

What "separate infrastructure" actually means

Separation isn't one setting. It's a set of layers, and the more of them you separate, the better insulated your transactional mail is.

  1. Separate sending IPs (or IP pools). Transactional and broadcast mail go out from different IP addresses, so IP-level reputation problems stay contained to one stream.
  2. Separate sending subdomains. Use something like mail.yourbrand.com for transactional and news.yourbrand.com for marketing. Providers increasingly weigh domain reputation over IP reputation, so this layer matters as much as the IPs.
  3. Separate authentication. Each subdomain gets its own SPF, DKIM signing domain and return-path (bounce) domain, all aligned for DMARC. That gives providers a clean, distinct identity for each stream.
  4. Separate tracking domains. If you track clicks, give each stream its own branded tracking domain so a flagged marketing link doesn't taint your receipts.
  5. Separate queues and sending streams. Transactional messages should never wait behind a bulk send. Dedicated queues keep delivery times measured in seconds regardless of what marketing is doing.

One thing should stay shared: your organizational domain and brand. Recipients should still recognize every message as coming from you. Separation happens in the infrastructure, not in the customer's experience.

What you get from separating them

Your critical mail is protected. If a campaign goes wrong, the issue stays with the marketing sendes. Password resets, receipts, and alerts keep reaching the inbox while you fix the problem.

Faster, more predictable delivery. With dedicated queues, transactional email isn't competing with bulk sends for throughput. Delivery times stay consistent, even on your busiest marketing days.

Clearer data. When streams are mixed, a healthy 60% open rate on receipts can hide a struggling newsletter, or a complaint spike can look like it came from everywhere. Separate streams give you clean metrics, so you can see exactly which email type needs attention.

Easier compliance. Gmail, Yahoo and Microsoft require bulk senders to fully authenticate their mail and keep complaint rates low, and marketing mail must also offer one-click unsubscribe. Separating streams lets you apply those rules where they belong without cluttering transactional messages with unsubscribe links people shouldn't use.

Freedom to experiment. Marketing can test new segments, send times, and content without putting the login flow at risk. Lower stakes mean better campaigns.

A checklist for separating your streams

Whether you're setting up from scratch or untangling an existing setup, work through these steps:

  • Audit what you send. List every email type and classify it. Rule of thumb: if the recipient would be upset not to receive it, it's transactional. If you, the sender, triggered it, it's broadcast. The exception: anything promotional is broadcast, even if a user triggered it. An abandoned-cart nudge is marketing.
  • Create dedicated subdomains for each stream, such as mail. for transactional and news. for broadcast.
  • Authenticate each subdomain with SPF, DKIM and a custom return-path, and confirm DMARC alignment.
  • Assign separate IPs or IP pools to each stream. Ensure your sending provider uses different IPs and queues for each mail type.
  • Set up separate branded domains for click and open tracking.
  • Keep promotions out of transactional mail. A small cross-sell in a receipt is fine; a full promotional block turns it into marketing in the eyes of providers.
  • Monitor each stream on its own in Google Postmaster Tools and your email provider's stats, watching complaint rates, bounces, and engagement separately.

If you're migrating an existing program, move one stream at a time and ramp volume gradually. Switching everything overnight to new IPs or domains with no history can cause serious deliverability problems (we see this a lot).

How Helo keeps your streams apart

At Helo, we treat separation as a default, not an upgrade. You can send both mail types with Helo, but transactional and broadcast email run on separate sending infrastructure all the way through the pipeline.

Here's what that looks like in practice:

  • Separate IP pools and processing queues per mail type. Your transactional email never shares sending reputation or waits in line behind a marketing send.
  • Subdomains and branded tracking domains. Each mail type can use its own subdomain (and tracking domain), keeping their reputations separate and ensuring an issue with one never affects the other.
  • Stats and activity separated by mail type. We make it easy to monitor signals for each type separately and spot problems before they spread.
  • Priority support for deliverability concerns. We keep a close eye on the signals that matter. When something looks off, a human is here to help you sort it out.

Your customers trust you to deliver the email that matters, every time. Separating your streams is non-negotiable for keeping that promise, and it's exactly what we built Helo to do.

Want a second opinion on your setup? Reach out to us for a chat. Helping you build solid sending practices is our responsibility, whether you're sending your very first email or tidying up a program you've run for years. We love this stuff!

‍