Transactional vs. Marketing Email: The Developer's Guide to Getting It Right
Transactional and marketing emails have different rules, different infrastructure requirements, and different legal compliance obligations. Here's how to set up both correctly and why you should never mix them.
Every company that sends email sends two fundamentally different kinds: transactional email (password resets, order confirmations, account notifications) and marketing email (campaigns, newsletters, promotions). These two categories look similar from the outside but have completely different rules, legal requirements, and infrastructure needs.
The most expensive mistake you can make is sending both types from the same sending domain and IP. When a marketing campaign generates spam complaints — as campaigns inevitably do — those complaints will damage the reputation of your transactional email sending infrastructure. Your password reset emails will land in spam.
What makes email transactional?
Transactional email is triggered by a specific user action or system event. Password resets, email verification links, order confirmations, shipping notifications, team invitations, security alerts, and billing receipts are all transactional. The defining characteristic: the recipient expects this email because they took an action that triggered it.
Transactional email is exempt from CAN-SPAM and GDPR opt-in requirements because it is a direct response to a user action. You don't need consent to send a password reset email to someone who clicked "forgot password". However, you must not include promotional content in a transactional email — that voids the transactional exemption.
What makes email marketing?
Marketing email is sent to a list of subscribers for commercial purposes: newsletters, product announcements, promotional campaigns, re-engagement campaigns, and upsell sequences. The defining characteristic: the recipient opted in (or is expected to have a prior business relationship) and can opt out.
Marketing email has strict legal requirements. CAN-SPAM requires a physical mailing address, a working unsubscribe mechanism, and honest sender identification. GDPR requires explicit opt-in consent for recipients in the EU. CASL requires express or implied consent for Canadian recipients. Violating these requirements carries fines up to $50 million for GDPR.
Infrastructure separation
Use separate subdomains for transactional and marketing email. Send transactional email from mail.yourdomain.com and marketing email from news.yourdomain.com or updates.yourdomain.com. Each subdomain should have its own SPF, DKIM, and DMARC records, and ideally its own dedicated IP or IP pool.
This isolation means that when your marketing campaign generates a spike in spam complaints — which happens even to well-managed lists — the reputation damage is contained to your marketing sending infrastructure. Your transactional emails continue to land in the inbox.
"The week we separated our transactional and marketing streams, our password reset delivery rate went from 94% to 99.8%. Those 6 percentage points represented real users getting locked out of their accounts."
How Sendbound handles both
Sendbound is built for transactional email at its core, with marketing email as a first-class feature. You can configure separate sending domains within a single Sendbound workspace, each with their own reputation metrics, IP pools, and deliverability dashboards. The API endpoint is the same — you just specify which sending domain to use, and Sendbound routes the email through the appropriate infrastructure.