Transactional vs. Marketing Email
Two categories, two different sets of rules
Email splits cleanly into two categories that mailbox providers, regulators, and infrastructure all treat differently: transactional email (receipts, password resets, shipping confirmations, two-factor codes — triggered by a user action and expected by the recipient) and marketing email (promotions, newsletters, campaigns — sent to drive engagement or revenue, not to fulfill an immediate expectation). Treating them as the same traffic class is one of the most common and most damaging infrastructure mistakes a growing company makes, because the two have fundamentally different risk profiles and recipient expectations.
Why they need separate sending infrastructure
Transactional email has near-100% expected engagement — a user who just reset their password is actively waiting for that email, so open rates are extremely high and complaint rates are near zero by nature. Marketing email has a much wider, noisier engagement distribution, and even a well-run promotional program will generate some unsubscribes and complaints as a normal cost of sending at volume.
If both traffic types share the same sending domain or IP, a marketing campaign that triggers a spam-filter response or reputation dip can take password resets and order confirmations down with it — meaning customers can't log in or verify a purchase because of an unrelated promotional email's deliverability problem. This is why mature sending setups use separate subdomains (e.g. mail.example.com for marketing, notify.example.com for transactional) with independent SPF/DKIM/DMARC configuration and often entirely separate sending platforms, so reputation damage in one lane never touches the other.
; Separate subdomains isolate reputation per traffic type
marketing.example.com -> ESP: Klaviyo
SPF: v=spf1 include:_spf.klaviyo.com ~all
DKIM: klaviyo-selector._domainkey.marketing.example.com
DMARC: _dmarc.marketing.example.com p=quarantine
notify.example.com -> Transactional provider: Postmark/SendGrid
SPF: v=spf1 include:spf.mtasv.net ~all
DKIM: pm-selector._domainkey.notify.example.com
DMARC: _dmarc.notify.example.com p=none (monitor only, high-trust traffic)
; A deliverability incident on marketing.example.com
; (e.g. spam complaints spike from a promo blast)
; has ZERO reputation effect on notify.example.com
; -> password resets and receipts keep landing in the inboxTransactional vs. marketing email — key differences
| Dimension | Transactional | Marketing |
|---|---|---|
| Trigger | User action (signup, purchase, password reset) | Scheduled campaign or behavioral flow |
| Recipient expectation | Expected immediately, high open rate | Variable — recipient didn't request this specific send |
| Opt-out requirement | Cannot be unsubscribed from (service-critical) | Must include unsubscribe link (legally required) |
| Typical complaint rate | Near zero | Low but non-zero, a normal cost of volume |
| Infrastructure | Dedicated transactional provider/subdomain | ESP/marketing platform, separate subdomain |
| Deliverability tolerance | Near-zero tolerance — must always arrive | Some variance tolerated, optimized over time |
Don't let marketing content sneak into transactional templates
Compliance: opt-out rules differ by category
Marketing email requires an unsubscribe mechanism under essentially every major anti-spam regulation, and that unsubscribe must be honored promptly (CAN-SPAM requires processing within 10 business days; GDPR-governed sends expect it to be near-immediate). Transactional email is exempt from this requirement specifically because it's necessary to fulfill a service the user already requested — a user cannot opt out of receiving their own order confirmation while still expecting the order to ship.
The practical implication: never route a transactional-only trigger (password reset, 2FA code, shipping update) through a marketing platform's suppression list logic — a customer who unsubscribed from promotions should still receive their receipts and security codes without interruption.
Transactional providers optimize for speed, not design tooling
What's next
Once marketing and transactional sends are cleanly separated, the next deliverability lever worth optimizing within the marketing lane is the subject line — the single highest-leverage, cheapest-to-test variable in a campaign.
Next: Subject Line Optimization →
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.