Why your receipts and your newsletters should never share a reputation

Two very different kinds of email leave your company every day.

Transactional email exists because a user did something: password resets, receipts, shipping confirmations, magic links. Recipients want these — open rates run several times higher than any campaign — and when one is late, it's a support ticket.

Marketing email exists because you did something: newsletters, promotions, announcements. Valuable, but unsolicited in the moment — and it's where all your reputation risk lives. Every complaint, every bounce from an old list, every aggressive campaign happens here.

The problem: mailbox providers score reputation per sending identity. If both streams share one, they share one fate.

The failure mode

It always plays out the same way. Marketing sends a campaign to a cold segment. Complaints spike, the domain's reputation dips, Gmail gets cautious with everything from that identity — and suddenly password resets are landing in spam. Users can't log in. Support drowns. Engineering investigates the auth system, which is fine.

Your most important email got taken down by your least important email. That's the entire argument for separation: firewall the mail your product depends on from the mail your growth experiments run on.

The setup: subdomains

You don't need two domains — separation happens at the subdomain level, because major providers track reputation per subdomain:

• Transactional → mail.yourdomain.com (or tx.)
• Marketing → news.yourdomain.com (or hello.)

Each subdomain gets its own DKIM keys and SPF/DMARC alignment, and builds its own track record. Your transactional subdomain becomes boringly pristine — high engagement, near-zero complaints — while the marketing subdomain absorbs the volatility of campaigns. A bad send dents news. and mail. doesn't notice.

Keep the root domain out of bulk sending entirely — reserve it for human-to-human mail. And avoid the tempting shortcut of sending anything from a lookalike domain (yourcompany-mail.com): it fragments the trust you've built and reads as phishing to both filters and humans.

Two things to remember once split:

Warm up each subdomain separately. Reputation doesn't transfer. A new marketing subdomain starts cold even if your transactional one is golden.

Respect the streams' different rules. Unsubscribes apply to marketing, not to receipts — someone who left your newsletter must still get their password reset. This only works if the streams are cleanly separated in your platform, not just in DNS.

One platform, two streams

Separation of reputation doesn't mean separation of tooling — running marketing on one vendor and transactional on another usually just means two dashboards and a suppression list that doesn't sync (a real compliance hazard: the unsubscribe captured on one system never reaches the other).

PristineSend runs both streams natively — transactional API sends and marketing campaigns — with shared suppression where it's legally required and separated identities where reputation demands it.

The bottom line

If your receipts and your promotions share a sending identity, your best email is underwriting your riskiest. Split them by subdomain, warm each one, and let your marketing team experiment without putting password resets in the blast radius.

Send both streams safely →