Here's a disaster I've watched happen more than once: a company sends one aggressive marketing campaign, their domain reputation takes a hit, and suddenly password reset emails start landing in spam. Users can't get into their accounts. Support melts down. All because marketing and transactional email shared one domain.
This is the single most preventable email catastrophe, and it comes down to one rule almost everyone ignores at first.
Transactional email is triggered by a user action — password resets, receipts, notifications — and must arrive every time. Marketing email is bulk, promotional, and opt-in.
Mix them on one sending domain and a bad marketing campaign can poison the reputation that delivers your critical transactional mail. Separate them — different domains or subdomains — and the two can't sink each other.
It's about isolating reputation risk, not bureaucracy.
| Transactional | Marketing | |
|---|---|---|
| Trigger | User action | You decide to send |
| Volume | One at a time | Bulk |
| Urgency | Must arrive now | Can wait |
| Consent | Implied by the action | Explicit opt-in required |
| If it fails | User locked out, angry | Lower open rates |
The asymmetry is the whole point: transactional failures are user-facing emergencies. A password reset in spam is a broken product. A newsletter in spam is a Tuesday.
Email providers score reputation at the domain and IP level. That score is shared across everything you send from that domain. So when your marketing email behaves badly — too much volume, too many complaints, too many dead addresses — the resulting reputation hit applies to all your mail, including the critical stuff.
Marketing email is inherently riskier: higher volume, less engaged recipients, more spam complaints. Tying your password resets to that risk is like storing your emergency cash in a casino. Most days it's fine. The day it isn't, you really need that cash.
The solution is clean and standard: send marketing and transactional mail from different domains or subdomains.
A common setup:
mail.yourdomain.com — protected, low-risk, high-trust.news.yourdomain.com — where bulk sending lives.Now if a marketing campaign damages reputation, it damages the marketing domain. Your transactional mail keeps flowing, users keep resetting passwords, and the blast radius is contained. Each domain gets its own SPF, DKIM, and DMARC and builds its own reputation.
The separation often maps naturally onto tooling. Transactional email tends to go through a transactional email API — built for instant, reliable, triggered delivery. Marketing and outreach tend to go through an email automation platform built for campaigns, lists, and opt-out management.
Using purpose-built tools for each isn't just convenient; it reinforces the separation. The transactional API and the marketing platform send from different domains with different reputations, so the isolation is structural rather than something you have to remember to maintain. This is part of getting your overall email infrastructure right.
Beyond deliverability, there's a legal and ethical line. Transactional email has implied consent — the user did something that requires the email. Marketing email needs explicit opt-in and a working unsubscribe.
Blur the line — sneaking promotional content into a "transactional" receipt — and you're not just risking reputation, you're risking compliance violations. Keep transactional mail strictly transactional. The moment you add a "while you're here, check out our sale," it's marketing, and the rules change.
To separate properly:
Q: I'm small — do I really need to separate now? Setting it up early is far easier than untangling it after a reputation disaster. Even at low volume, using a subdomain for marketing costs nothing and protects you the day you scale. Do it before you're forced to.
Q: Can I send both through the same provider? Often yes — many providers support both — but ensure they're on separate domains/subdomains with separate reputations. Same provider is fine; same sending identity is the risk.
Q: What counts as transactional vs marketing exactly? Transactional = the user's action requires this specific email (reset, receipt, alert). Marketing = you're promoting something. If you'd send it whether or not the user did something, it's marketing. When in doubt, treat it as marketing and get consent.
Transactional and marketing email feel like the same thing, but they carry wildly different risk. Mixing them on one domain means a bad campaign can break your users' ability to log in. Separate them onto different authenticated domains, route each through purpose-built tools, and never let promotional content sneak into transactional mail.
Set up a marketing subdomain this week if you haven't. It's a tiny task that prevents one of the most painful, self-inflicted email disasters there is.
No following, no network, no luck. Just an unglamorous system I ran for eighteen months. Here's exactly what I did.
I went from 200 to 11,000 subscribers without hiring anyone. AI didn't write my newsletter — it did everything around it.
One person, output that looks like five. It isn't about working more hours — it's about a kind of leverage teams rarely have.
Comments
Sign in to join the conversation
No comments yet. Be the first to share your thoughts!