Transactional vs marketing email: why you must separate the streams

The last row matters more than it looks. Transactional volume is smooth because it tracks real usage. Marketing volume is bursty by design — a campaign sends a month of transactional volume in twenty minutes. Receiving providers treat sudden volume spikes from a given sending identity with suspicion, and when the two streams share an identity, your campaign spike is throttling your receipts.

Reputation is not attached to your brand, your company, or your account with an email provider. It is attached to identifiers that appear in the message and the connection carrying it.

Work the numbers. Suppose you send 400,000 marketing messages and 100,000 transactional messages in a month, all from yourdomain.com with a single DKIM key. The marketing stream runs at a 0.15% complaint rate, which is unremarkable for opted-in promotional mail. The transactional stream runs at 0.005%.

Six hundred marketing complaints and five transactional complaints land on the same identity. The blended rate is 0.121% — comfortably past the 0.10% figure Google advises staying under, and creeping toward the 0.30% threshold where throttling begins. Your receipts did nothing wrong and are now being scored as if they did.

Now run one bad month. A poorly segmented campaign to a re-engagement list pushes the marketing complaint rate to 0.4%. The blended rate crosses 0.32%. Gmail begins throttling the identity, and the mail that gets throttled includes the password resets. Support volume rises, and nobody on the engineering side has changed a line of code.

The asymmetry is the point. Separation does not just protect transactional mail from marketing mail — it also lets marketing be evaluated honestly rather than being propped up by transactional engagement it did not earn. Both streams get judged on their own behaviour, which is what you want when you are trying to diagnose anything.

The standard pattern is one subdomain per mail stream, each fully authenticated in its own right, all under the same organisational domain so the brand relationship stays visible to recipients.

Notification email is the awkward middle case. It is transactional in mechanism but discretionary in value, and at high volume it accumulates complaints in a way receipts never do. If your product sends a lot of it — comment notifications, digests, activity summaries — give it a third subdomain rather than letting it share with mail that genuinely cannot fail. The cost is one more DNS block; the benefit is that a noisy notification stream cannot take your password resets with it.

Each sending subdomain needs its own complete authentication set. They do not share records, and they should not share DKIM keys — separate keys are what make the identities separable in the first place.

One DMARC record at the organisational domain covers every subdomain unless a subdomain publishes its own. The sp= tag sets the policy applied to subdomains specifically, which is useful during a rollout: you can hold the organisational domain at p=reject while a newly separated marketing subdomain runs at sp=quarantine until its alignment is confirmed clean.

The adkim=s and aspf=s tags request strict alignment, meaning the authenticated domain must match the From: domain exactly rather than merely sharing an organisational parent. Strict alignment is the right end state, but turn it on only after aggregate reports confirm every legitimate source is aligned — otherwise you will reject your own mail.

Subdomain separation partitions domain reputation. It does not partition IP reputation, and Microsoft in particular still weights IP heavily. If both streams leave from the same IP addresses, you have solved half the problem.

The complete version routes each stream through infrastructure that only carries traffic of that kind. In practice that means using a provider whose transactional network does not also carry marketing blasts, and — above a certain volume — moving to IPs that are yours alone.

This is the design SuperSend TX is built around. The production pool carries transactional mail from paying customers only — no free-tier signups, no campaign traffic, no cold outbound — so the neighbours on the shared lane are senders with the same incentives you have. Above that, Dedicated gives you your own mail servers and IP addresses, provisioned, warmed through a full ramp, and operated by us, with the same POST /emails contract so nothing in your application changes.

A new subdomain has no sending history, which means it needs the same gradual introduction any new sending identity does. Cutting 100% of transactional volume over on a Tuesday afternoon will produce exactly the throttling you were trying to avoid.