- Transactional email is triggered by a user action and expected by the recipient, while marketing email is sent in bulk on your schedule.
- Sharing one subdomain or IP lets a bad marketing campaign delay password resets, receipts and security codes.
- Use a separate subdomain for each stream, with its own SPF, DKIM and return-path, and separate IPs once volume justifies them.
- Transactional messages are largely exempt from CAN-SPAM opt-out rules, but only while their primary purpose stays transactional.
- Choose a transactional service for speed, clean infrastructure and detailed logs, and keep campaigns on their own platform or stream.
A password reset that arrives ten minutes late is a support ticket. One that lands in spam is a lost customer. Yet many companies send those resets from the same domain and IP as their weekly promotions, which means one poorly targeted campaign can hold their most important mail hostage.
This guide explains how transactional and marketing email differ, why mailbox providers treat them differently, and how to split them into separate streams using subdomains, authentication and IPs. It also covers the compliance differences and the services worth considering for your transactional stream.
What is transactional email?
Transactional email is triggered by something the recipient did, or by an event on their account. They expect it, and often they are waiting for it.
- Order confirmations and receipts
- Shipping and delivery updates
- Password resets and email address confirmations
- Two-factor and one-time login codes
- Security alerts, such as a login from a new device
- Billing notices, failed payments and renewal reminders
- Appointment confirmations and reminders
Because recipients want these messages, they open them quickly, rarely mark them as spam and often search for them later. That behavior builds a strong, stable reputation, and it is exactly what you want to protect.
What is marketing email?
Marketing email is sent on your schedule to a list or segment, with the goal of driving engagement or sales.
- Newsletters and content digests
- Promotions, discounts and flash sales
- Product launches and feature announcements
- Event invitations and webinars
- Re-engagement and win-back campaigns
Marketing mail is valuable, but it carries more risk. Audiences are larger and less uniformly interested, so complaints, unsubscribes and bounces are higher. Volume comes in bursts, and seasonal peaks can multiply normal volume several times over.
How the two streams differ
| Attribute | Transactional | Marketing |
|---|---|---|
| Trigger | User action or account event | Sender-scheduled campaign |
| Audience | One recipient | List or segment |
| Recipient expectation | High, often waiting for it | Varies with interest |
| Engagement | Very high | Much lower, varies by list |
| Complaint risk | Very low | Moderate to high |
| Volume pattern | Steady, follows user activity | Batches and seasonal spikes |
| Time sensitivity | Seconds matter | Minutes to hours acceptable |
| Opt-out under CAN-SPAM | Not required if purely transactional | Required in every message |
| One-click unsubscribe (Gmail/Yahoo) | Not required | Required for bulk senders |
Why you should separate them
Reputation contamination
Imagine your newsletter goes to an old segment and draws complaints near 0.3%, the ceiling Gmail and Yahoo publish for bulk senders. If receipts and resets share that domain and IP, they inherit the damage. Gmail may start routing some of them to spam or deferring them with codes like 421 or 4.7.28. Your customers do not care why; they just do not get their code.
Conflicting volume patterns
Mailbox providers model normal behavior for each sender. A stream that usually sends a few hundred messages an hour and then suddenly pushes 80,000 in twenty minutes looks suspicious, and providers throttle it. Throttling applies to everything on that stream, including the reset email caught in the middle of your sale blast.
Different engagement profiles
Transactional mail has excellent engagement. Marketing mail has average engagement at best. When both share a reputation, the average drags down the excellent. Separating them lets your transactional stream keep the reputation it earns.
Cleaner diagnostics
With separate streams, a spike in bounces or complaints points to one program immediately. Mixed streams make every investigation slower.
How to set up separate email streams
Step 1: create a subdomain for each stream
Pick names that make the purpose obvious and use them consistently:
notify.example.comormail.example.comfor transactional mailnews.example.comoroffers.example.comfor marketing mail
Keep your root domain (example.com) for staff mailboxes. Subdomains inherit some reputation from the organizational domain, but each builds its own history too, so a problem on news. is contained far better than a problem on the root. For more on this, see our DNS records for email guide.
Step 2: authenticate each subdomain separately
Each subdomain needs its own SPF record (on the domain that appears in the return-path), its own DKIM selector and signature, and coverage by DMARC.
; Transactional stream
notify.example.com. TXT "v=spf1 include:spf.transactional-provider.example -all"
t1._domainkey.notify.example.com. CNAME t1.dkim.transactional-provider.example.
; Marketing stream
news.example.com. TXT "v=spf1 include:spf.marketing-provider.example -all"
m1._domainkey.news.example.com. CNAME m1.dkim.marketing-provider.example.
; DMARC on the organizational domain (applies to subdomains unless sp= says otherwise)
_dmarc.example.com. TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"Use 2048-bit DKIM keys where the provider supports them, and make sure the DKIM d= domain matches the From subdomain so DMARC aligns. Check each subdomain with the SPF checker, DKIM checker and DMARC checker. Our email authentication guide covers alignment in depth.
Step 3: separate IPs when volume justifies it
On shared infrastructure, many providers already keep transactional and marketing traffic in different pools. If you use dedicated IPs, give each stream its own IP (or pool) once each has enough steady volume to warm and keep warm. A dedicated IP that sends a few hundred messages a day never builds a reputation of its own and may perform worse than a good shared pool. Our shared vs dedicated IP guide has the thresholds, and every new IP needs a gradual warmup.
Step 4: route each message type correctly
Configure your application to send transactional mail through the transactional subdomain, API key and IP, and your campaigns through the marketing ones. Many providers let you do this inside one account with separate sending domains or message streams. Alternatively, use two providers: a transactional specialist for application mail and a marketing platform for campaigns.
Compliance differences
The law treats the two streams differently. This is general guidance, not legal advice, so check the specifics for your markets.
CAN-SPAM (United States)
CAN-SPAM classifies messages by their primary purpose. Transactional or relationship messages are exempt from most requirements, including the opt-out link and physical address, but they must not contain false or misleading header or routing information. Commercial messages need a working opt-out honored within 10 business days, a valid postal address and a non-deceptive subject line.
A shipping notice with a small “you may also like” block stays transactional. A “shipping notice” that is mostly a sale announcement is a commercial message and must follow the commercial rules.
GDPR and ePrivacy (European Union and UK)
Transactional mail usually relies on contract performance or legitimate interest as its legal basis, so you do not need marketing consent to send a receipt. Marketing mail generally needs opt-in consent, with a limited “soft opt-in” for existing customers in some countries. Keep a clear record of which basis applies to each stream.
CASL (Canada)
CASL requires consent for commercial electronic messages but exempts purely transactional ones, such as receipts, warranty information and account notices. As with CAN-SPAM, adding promotions changes the category.
Mailbox provider rules
Gmail and Yahoo’s 2024 bulk sender rules require authentication for all bulk mail, and one-click unsubscribe (RFC 8058) for marketing and subscribed messages. Microsoft’s Outlook rules from May 2025 follow the same pattern. Transactional mail still needs SPF, DKIM and DMARC even though it does not need a one-click unsubscribe header.
Choosing a transactional email service
Your transactional stream needs speed, reliability, detailed logs and clean infrastructure. Three strong options cover most teams:
| Service | Best for | Strengths | Watch out for |
|---|---|---|---|
| Postmark | SaaS products where speed matters most | Separate message streams by design, fast delivery, excellent logs | Higher cost at very high volume |
| Amazon SES | Developer teams on AWS sending at scale | About $0.10 per 1,000 emails, configuration sets per stream | You build bounce handling and reporting yourself |
| SendPulse SMTP | Teams that want marketing and transactional in one account | 12,000 emails a month free, dedicated IP included on SMTP Pro | Marketing features add interface complexity if you only need SMTP |
Postmark is the specialist. It separates transactional and broadcast streams at the infrastructure level and rejects senders who try to push bulk marketing through it, which keeps its pools clean.
Amazon SES is the value choice. Use one configuration set per stream, a custom MAIL FROM subdomain for SPF alignment, and wire bounce and complaint notifications into your suppression list from day one.
SendPulse offers an SMTP and transactional service alongside its campaign tools. The free tier covers 12,000 emails a month, and the Pro plan (100,000 emails a month) includes a dedicated IP and unlimited sending domains, so you can put notify. and news. on separate domains in one place. Its SPF include is include:mxsmtp.sendpulse.com and its DKIM selector is sign.
SendGrid and Mailgun are also solid for transactional traffic, especially for developer-led teams. Our bulk email services comparison covers all of them in more detail.
Example: a mid-sized online store
Here is how a store sending about 20,000 order and account emails and 150,000 marketing emails a month might set things up:
| Stream | From address | Subdomain | Provider and IP | Notes |
|---|---|---|---|---|
| Orders, shipping, resets | orders@notify.example.com | notify.example.com | Transactional service, shared transactional pool | Sent by the store platform through the API in real time |
| Newsletters and promotions | news@news.example.com | news.example.com | Marketing platform, dedicated IP once volume is steady | Scheduled campaigns, one-click unsubscribe |
| Staff mail | name@example.com | example.com (root) | Workspace mail | Never used for bulk sending |
If a holiday campaign draws complaints, only the news. subdomain and its IP take the hit. Customers still get their order confirmations on time.
Monitoring each stream separately
Separation only pays off if you watch each stream on its own. Blended dashboards hide exactly the problems you split the streams to catch.
Transactional metrics to watch
- Time to inbox. Measure how long a reset or login code takes from trigger to delivery. Seconds are normal; minutes mean queuing or throttling.
- Deferral rate. Temporary 4xx responses by mailbox provider. A rise at one provider usually signals a reputation problem there.
- Hard bounce rate. Should stay very low. Spikes often trace back to a signup form accepting typos, such as 550 5.1.1 user-unknown bounces.
- Support tickets. “I never got the email” tickets are a leading indicator. Track them alongside delivery data.
Marketing metrics to watch
- Complaint rate per campaign, ideally under 0.1%.
- Click rate by mailbox provider, which reveals when one provider starts filtering you.
- Unsubscribe rate, which rises before complaints do when frequency or content misses the mark.
- Domain reputation in Google Postmaster Tools for the marketing subdomain.
Register each subdomain separately in Google Postmaster Tools so you can see its reputation on its own. If you use dedicated IPs, register them in Microsoft SNDS too.
Common mistakes when splitting streams
Sharing the From address
If receipts and newsletters both come from hello@example.com, recipients cannot tell them apart and complaints about marketing land on the address they also need for receipts. Use distinct addresses, such as receipts@notify.example.com and news@news.example.com, with clear sender names.
Leaving the root domain in the return-path
Some setups separate the From domain but still bounce everything through one shared return-path. SPF and bounce handling then mix the streams again. Give each stream its own bounce subdomain.
Warming the transactional stream with marketing mail
When a team launches a new transactional subdomain, it is tempting to “help” it along with a newsletter. That defeats the purpose. Transactional streams warm naturally from real user activity, so let them.
Promotional creep
Over time, marketing teams tend to add banners, offers and upsells to receipts because open rates are high. A little is fine. A lot changes the legal classification and the complaint profile. Agree on a written rule, such as one small, relevant block below the transactional content.
Forgetting DMARC for subdomains
A DMARC record on the root covers subdomains by default, but an sp=none tag can leave them unprotected. Check the record with the DMARC checker after any change, and make sure reports cover both streams.
Best practices for each stream
Transactional
- Optimize for speed. Send from your application in real time, not in batches, and set alerts for queue delays.
- Keep content functional. Clear subject, clear purpose and minimal promotion.
- Handle soft bounces with retries. Temporary 4xx errors should be retried with backoff, and hard bounces suppressed immediately.
- Watch bounce rates closely. Transactional bounce rates should be very low. A rise usually means a signup form is accepting typos or bots, so add real-time verification.
- Inspect headers when something looks off. Our header analyzer shows authentication results and routing hops in one view.
Marketing
- Warm new subdomains and IPs gradually, starting with your most engaged subscribers.
- Keep complaints under 0.1% and never let them approach 0.3%.
- Segment by engagement and sunset contacts who stop responding.
- Make unsubscribing easy, with one-click headers and a visible link. An unsubscribe is always better than a complaint.
- Check Google Postmaster Tools within a day of each send for spam rate and domain reputation.
Separate the streams once, set up authentication properly for each, and your receipts, resets and security codes will keep arriving on time, no matter how your next campaign performs.
Frequently asked questions
What counts as a transactional email?
An email whose main purpose is to complete or update a transaction or relationship the recipient already has with you: receipts, shipping updates, password resets, security codes, account alerts and billing notices. If the message would still make sense to send to someone who has unsubscribed from marketing, it is probably transactional. If its main aim is to sell, it is marketing.
Can I include promotions in transactional emails?
A small, relevant mention is generally fine, such as a related product under an order summary. Once promotional content becomes the main point of the message, regulators and mailbox providers treat it as marketing. That brings opt-out requirements under CAN-SPAM and consent requirements under GDPR and CASL, and it exposes your transactional stream to marketing-level complaints.
Do I need a separate IP for transactional email?
Not at first. A separate subdomain gives you most of the isolation, because mailbox providers now weight domain reputation heavily. Separate IPs become worthwhile when each stream has enough steady volume to warm and sustain its own IP, usually tens of thousands of messages a week or more. Check both IPs regularly with a blacklist checker.
Do transactional emails need an unsubscribe link?
Purely transactional messages do not need one under CAN-SPAM, and the Gmail and Yahoo one-click unsubscribe requirement applies to marketing and subscribed messages. Recipients must still be able to stop marketing, so never slip promotions into a message without an opt-out. Many senders add a link to notification preferences in transactional mail anyway.
Which email service is best for transactional email?
Postmark is the specialist choice for speed and strict stream separation. Amazon SES is the cheapest at scale for teams with developers on AWS. SendPulse SMTP suits teams that also want marketing tools in the same account and a dedicated IP on its Pro plan. SendGrid and Mailgun are solid developer-focused alternatives.