Transactional Email vs Marketing Email
Transactional email vs marketing email: the real difference in deliverability, legal rules, and why mixing them on one domain breaks password resets.
On this page · 9 sections
Overview
Most teams learn the difference between transactional and marketing email the hard way: marketing sends a product launch blast to a stale 18-month-old list, 0.4% of recipients hit 'Report spam', and twenty minutes later paying customers cannot log in because their magic links are landing in Gmail's Spam folder.
Mailbox providers do not care which folder a template lives in inside your codebase. They score reputation per sending domain and IP, and they expect very different behavior from a password reset than from a promotional broadcast. Here is how to draw the line cleanly — legally and technically.
One simple test that separates the two
Ignore labels like 'automated' or 'triggered' — an automated drip campaign is still marketing. Ask one question instead: did the user just take an action that requires this email to complete it? Password resets, login codes, Stripe receipts, team invites, and security alerts are transactional. The recipient expects them within seconds, opens them almost every time, and practically never marks them as spam.
Marketing email is anything you chose to send to persuade, re-engage, or announce — newsletters, feature launches, discount offers, win-back sequences. Under GDPR, CAN-SPAM, and Gmail/Yahoo's bulk-sender rules, marketing email requires a valid legal basis, a clear one-click unsubscribe, and immediate opt-out enforcement. You obviously should not put a marketing unsubscribe button on a password reset — otherwise a user who opted out of announcements six months ago gets locked out of their account.
| Property | Transactional email | Marketing / outbound email |
|---|---|---|
| Trigger | User action (login, payment, invite) | Company decision (campaign, launch, sequence) |
| Recipient expectation | Immediate (seconds matter) | Optional; can wait or be ignored |
| Unsubscribe header | Not required (and can break account flows) | Mandatory (List-Unsubscribe + body link) |
| Marketing opt-out list | Still delivered to unsubscribed users | Must be suppressed permanently |
| Hard bounces & complaints | Must still be suppressed | Must be suppressed |
Where teams accidentally cross the line
The tricky cases live in the middle: a receipt with a huge 'Refer a friend for $50' banner at the top, a trial-ending reminder that turns into a three-email sales pitch, or a 'You have 3 unread notifications' digest sent to someone who hasn't logged in since January. Regulators and spam filters judge by primary purpose. If half the email is selling something, treat it as marketing — add an unsubscribe link and send it from your marketing stream.
Equally dangerous is the reverse mistake: forgetting to suppress hard bounces on transactional mail. Even if a message is genuinely transactional, repeatedly emailing a dead address (550 5.1.1 User unknown) tells Gmail and Microsoft your pipeline has no hygiene. Keep hard-bounce and spam-complaint suppression global across every stream.
- Keep receipts, resets, and alerts visually plain and strictly about the action taken
- Treat trial-nurture, onboarding tips, and weekly digests as marketing with an unsubscribe link
- Never bypass hard-bounce or complaint suppression — only bypass marketing opt-outs
How to isolate them in DNS and in code
Give transactional mail its own dedicated subdomain — for example auth.yourdomain.com or mail.yourdomain.com — and send campaigns or outbound from a separate subdomain or secondary domain (see our email subdomain strategy). Publish aligned SPF, DKIM, and DMARC records on each subdomain so Gmail builds an independent reputation profile for your product mail.
In your application code, make the intent explicit at send time. On Mailbase's transactional email API, passing transactional: true to POST /api/v1/send tells the delivery layer three concrete things: skip marketing opt-out lists, omit the bulk List-Unsubscribe header, and bypass campaign warm-up pacing so password resets leave immediately — while hard bounces and complaints stay blocked.
- Separate subdomains (
auth.example.comvsnews.example.com) contain reputation blast radius - Verify DKIM and Return-Path alignment per subdomain with our free domain check
- Pass
transactional: trueexplicitly in API payloads rather than guessing from templates
Common mistakes
- Sending product-critical mail and marketing from the same domain/reputation.
- Skipping idempotency, so retries create duplicate sends.
- Ignoring bounce and complaint webhooks until suppression breaks.
- Treating an email API as “fire and forget” with no event logging.
Sources and further reading
Official docs for current setup details, pricing, and API behavior — verify specifics there, since they change.
Related guides
More on transactional email vs marketing email and the surrounding transactional email workflow: