Most SaaS teams blur the line between transactional and marketing email until something breaks: either deliverability tanks, legal gets nervous, or users start marking critical system emails as spam.
The difference isn't "boring vs fun" or "text vs design." It's about intent, expectation, and legal obligation.
What actually qualifies as transactional vs marketing?
The line is simpler than most docs make it sound: did the user trigger this email by taking an action, or are you starting the conversation?
Transactional email
User-initiated, service-related messages that fulfill an expectation or complete a workflow.
- Password reset
- Email verification / magic link
- Order confirmation / receipt
- Shipping notification
- Failed payment alert
- Account security alert (login from new device)
- API key generated / webhook triggered
Marketing email
Promotional, educational, or engagement-driven messages you send to start a conversation or drive behavior.
- Product announcements
- Feature launches
- Weekly newsletters
- Case studies / blog roundups
- Seasonal promotions
- "We miss you" re-engagement campaigns
- Upsell / cross-sell offers
Legal and compliance differences
This is where most teams get burned: treating transactional infrastructure like a marketing loophole.
CAN-SPAM (US)
- Transactional: No unsubscribe required. Must facilitate a transaction or provide account info.
- Marketing: Requires unsubscribe link, physical address, accurate subject line.
- Hybrid: If you add promotional content to a transactional email, CAN-SPAM treats the whole email as marketing.
GDPR (EU)
- Transactional: Allowed under "legitimate interest" or "contractual necessity" (no consent needed).
- Marketing: Requires explicit opt-in consent. Pre-checked boxes don't count.
- Soft opt-in exception: You can send marketing to existing customers for similar products/services—but must offer unsubscribe and honor it immediately.
Infrastructure and deliverability differences
Even if you stay compliant, sending marketing email through transactional infrastructure (or vice versa) will hurt deliverability.
Separate sending domains
Best practice: use different domains or subdomains.
- Transactional:
mail.yourapp.com - Marketing:
news.yourapp.com
Why? Marketing campaigns risk spam complaints. If those complaints tank the reputation of your transactional domain, password resets stop landing in the inbox.
ESP choice matters
Transactional and marketing ESPs are optimized for different goals.
- Transactional ESPs (Resend, Postmark, SendGrid Transactional): Fast delivery, API-first, webhook-heavy, high reputation.
- Marketing ESPs (Mailchimp, ConvertKit, Klaviyo): Drag-and-drop builders, segmentation, A/B testing, analytics dashboards.
When to use transactional vs marketing (decision framework)
Ask these three questions:
1. Did the user trigger this email?
- Yes: Transactional (e.g., they clicked "reset password").
- No: Marketing (e.g., you're announcing a new feature).
2. Is this email required for the user to complete a task?
- Yes: Transactional (e.g., email verification, receipt).
- No: Marketing (e.g., product tips, feature highlight).
3. Would removing this email break a workflow?
- Yes: Transactional (e.g., magic link, order confirmation).
- No: Marketing (e.g., newsletter, upsell offer).
Hybrid patterns (and when they're allowed)
Some emails feel transactional but include promotional elements. Here's what's safe vs risky.
Safe: Transactional email with soft promotional content
A receipt email that includes "Related products you might like" at the bottom is legal under CAN-SPAM's "transactional or relationship message" exception—as long as the primary purpose is transactional.
Rule of thumb: the transactional content must dominate the email.
Risky: "Transactional" email that's mostly promotional
Examples that will get flagged:
- Password reset email with 3 paragraphs about a Black Friday sale.
- Shipping notification buried under a product upsell pitch.
- Trial expiration email that's 80% feature marketing.
Common mistakes that hurt deliverability
1. Sending marketing through transactional ESP
You send a "new feature announcement" blast through Postmark or Resend. Users mark it as spam. Your transactional domain reputation tanks. Password resets start landing in spam.
Fix: Use separate sending domains and ESPs for transactional vs marketing.
2. No unsubscribe link on borderline emails
You send a "we noticed you haven't logged in" email and treat it as transactional because it references the user's account. But it's promotional in nature—you're trying to drive engagement, not fulfill a transaction.
Fix: When in doubt, add an unsubscribe link. It won't hurt true transactional emails and protects you legally.
3. Abusing the "account notification" loophole
You label every marketing email "Account Notification" or "Important Update" to bypass consent requirements. Regulators and spam filters see through this instantly.
Fix: Be honest. If it's promotional, treat it like marketing.
Infrastructure setup: how to keep them separate
1. Use separate subdomains
- Transactional:
mail.yourapp.com - Marketing:
news.yourapp.com
Publish SPF, DKIM, and DMARC for both.
2. Split ESPs (or use separate sending pools)
- Transactional: Resend, Postmark, or SendGrid Transactional API.
- Marketing: Mailchimp, ConvertKit, or SendGrid Marketing Campaigns.
If using one provider for both, configure separate IP pools or sender identities.
3. Track consent separately
Store marketing consent independently from account creation.
user.email_verified→ transactional alloweduser.marketing_consent→ marketing allowed
Honor unsubscribes immediately (legally required in EU/US).
Pre-send checklist
Before hitting send, ask:
- Did the user trigger this? (Yes → transactional)
- Is it required to complete a workflow? (Yes → transactional)
- Does it include promotional content? (Yes → add unsubscribe, treat as marketing)
- Am I sending from the right domain? (transactional ≠ marketing)
- Do I have consent (if marketing)? (GDPR/CAN-SPAM)
- Is there an unsubscribe link (if marketing)?
TL;DR
- Transactional: User-triggered, required for workflows, no consent needed, no unsubscribe required.
- Marketing: Promotional, requires consent, must include unsubscribe.
- Hybrid emails: Legal if primary purpose is transactional, risky if promotional content dominates.
- Infrastructure: Use separate domains/ESPs to protect transactional deliverability.
- When in doubt: Treat it like marketing.
Get transactional templates that follow these patterns: SaaS Essentials bundle.