Transactional vs marketing email: why you should separate them
Receipts and password resets are not newsletters. Learn how the two differ in law, speed and reputation, and how to keep one from hurting the other.
Your newsletter gets a spike of spam complaints. Two days later, customers say they aren't receiving password resets. Nothing about the password reset changed. What changed is that your domain's reputation took a hit, and every message you send shares it.
That's the core argument for splitting transactional and marketing email.
The difference in one table
| Transactional | Marketing | |
|---|---|---|
| Trigger | One person's action or account event | A campaign you schedule |
| Audience | One recipient | A list |
| Expected? | Yes, people wait for it | Sometimes |
| Speed | Seconds matter | Minutes or hours are fine |
| Opt-out | Usually not offered per message | Required |
| Examples | Receipt, code, reset link, alert | Newsletter, sale, product launch |
If you're not sure which side a message belongs on, ask whether the recipient would be annoyed if it never arrived. A reset link, yes. A weekly roundup, probably not.
Reason 1: reputation is shared
Mailbox providers build a score for your sending domain, and for the IP address you send from. Bounces, spam complaints and low engagement all lower it. Marketing mail has the worst numbers because recipients can ignore it, delete it or mark it as spam. Transactional mail has the best, because people want it.
If both go out under the same domain, the marketing numbers pull the transactional ones down. The standard fix is a separate sending identity for each. Many senders use a subdomain such as mail.yourdomain.com for transactional and news.yourdomain.com for marketing. Reputation is tracked per domain, so the two stay mostly independent.
Reason 2: speed
A login code is a race against the user's patience. A newsletter to forty thousand people is a long queue. If one system sends both, the codes wait behind the campaign. Separate paths let transactional mail go straight out.
Reason 3: unsubscribe and consent
Marketing mail needs a way to opt out, and in many countries consent before you send it. Gmail and Yahoo now expect a one-click unsubscribe header on marketing mail from bulk senders. The Gmail and Yahoo requirements post has the details.
Transactional messages are generally treated differently, because they relate to something the person has already done. That only holds if they stay purely transactional. Put a promotion inside a receipt and some regulators, and some mailbox filters, start treating it as marketing. The rules depend on where your customers live, so check them.
Reason 4: list hygiene
A marketing list rots. People change jobs, abandon addresses and stop reading. Sending to dead addresses produces bounces, and bounces hurt reputation. A transactional list is always fresh, because every send is triggered by a recent action. Keep the clean stream away from the rotting one.
How to split them
- Pick the subdomains. For example
mail.yourdomain.comfor app mail and a different one for campaigns. - Authenticate each. Every sending domain needs its own SPF, DKIM and DMARC. The authentication checker helps verify them.
- Use different from addresses.
[email protected]for receipts,[email protected]for campaigns. - Use different tools. Transactional mail goes through an API or SMTP from your app. Campaigns go through a platform that handles lists, unsubscribes and reporting.
- Never import marketing contacts into the transactional stream. Don't send a promotion because a customer's address happens to be in your app's database.
One detail to remember about Mailions's API: the from address must be on the key's domain, and a subdomain such as @app.yourdomain.com counts as a different domain from @yourdomain.com. If you send from a subdomain, add that subdomain as its own domain in the panel so it gets its own records and its own key.
What Mailions is and isn't
Mailions is built for transactional mail and for business mailboxes: an API, SMTP and private webmail on your own domain. It isn't a newsletter platform, and it doesn't handle subscriber lists or campaign analytics. If you also send newsletters, use a tool designed for them and keep it on its own subdomain.
Warning signs that you should have split already
- Password resets get slower or vanish after campaigns
- Complaint rates climb after each newsletter
- Your marketing opt-outs are mixed up with account notifications
- One broken campaign template can block all outgoing mail
A quick example
Imagine an online shop. The order confirmation, the shipping notice and the password reset are all transactional. They go out through the app, from [email protected], and nothing else shares that address. The monthly sale announcement goes out from a campaign tool, from [email protected]. If the sale email draws complaints, only the news subdomain suffers, and orders keep arriving.
Where to go next
If you're new to the term, start with what is transactional email. To send app mail from your own domain, the API guide has working examples, and you can contact us to get a trial for your domain.
Frequently asked questions
What is the difference between transactional and marketing email?
Transactional email is triggered by a person's own action and needed to complete it, such as a receipt or password reset. Marketing email promotes something to a list and needs consent and a way to unsubscribe.
Should transactional and marketing emails use different domains?
Sending marketing from a separate subdomain, such as news.yourdomain.com, is common good practice. Complaints about newsletters then affect that subdomain's reputation instead of delaying your password resets and receipts.
Is a welcome email transactional or marketing?
A plain welcome that confirms the account and explains the next steps is generally transactional. Once it promotes offers, upgrades or other products, treat it as marketing and follow the marketing rules.