Separating transactional and marketing email is one of the simplest changes that improves reliability. A password reset and a promotion are very different messages: one is expected and urgent, the other optional and often ignored. Mailbox providers learn from how recipients treat each stream, so putting both on one reputation lets the weaker stream drag the stronger one down. This guide explains how to separate them in practice.
What counts as transactional
Transactional mail is sent because of something a person did, or because of their account. The recipient is waiting for it or would complain if it did not arrive. Marketing mail is sent to promote or to maintain a relationship, and the recipient can do without it. Some messages fall in between, and it helps to decide where each one sits and write it down.
| Message | Usual type | Why it matters |
|---|---|---|
| Password reset, login code | Transactional | Time-critical; a delay locks users out |
| Order confirmation and receipt | Transactional | Expected, high engagement |
| Shipping and delivery notice | Transactional | Expected, often opened several times |
| Account alert or security notice | Transactional | Important; must be reliable |
| Invoice and statement | Transactional | Expected; sometimes legally required |
| Welcome email after sign-up | Transactional, often mixed | Keep promotions out of it |
| Product update newsletter | Marketing | Optional; engagement varies |
| Promotion and sale announcement | Marketing | Highest complaint risk |
| Abandoned cart reminder | Marketing or in between | Treat as marketing for list and opt-in rules |
Why reputation must be separated
Providers do not judge a message in isolation. They look at the history of the domain and IP address that send it, built from signals such as complaints, bounces, engagement and spam-trap hits. A receipt is opened and rarely marked as spam. A promotion to a large list is opened less and reported more. Averaged together, the two produce a worse reputation than the receipts would have alone, and the effect lands on exactly the messages you most need to arrive.
- Complaint rates differ. Large providers publish thresholds for spam complaints. A stream that sits near them needs its own space so it cannot affect others.
- Engagement differs. Highly engaged transactional mail lifts a shared reputation, but low-engagement marketing mail lowers it.
- Risk differs. A bad list import or a misjudged campaign is a marketing problem. It should not stop password resets.
- Diagnosis is easier. When streams are separate, a spike in bounces points straight to the stream that caused it.
Designing the structure
Subdomains
Give each stream its own sending subdomain under your main domain. Keep the root domain for staff mail. A common pattern is one subdomain for system messages and one for marketing, and more where you have a clear reason, such as a separate brand.
| Stream | Example From domain | Notes |
|---|---|---|
| Transactional | orders.example.com or mail.example.com | Strictest list hygiene; keep content focused |
| Marketing | news.example.com | Needs consent records and an unsubscribe route |
| Staff email | example.com | Keep away from bulk sending entirely |
Authentication for each subdomain
Authenticate every subdomain on its own: SPF, a DKIM key with its own selector, and a return-path on the same subdomain. This is the work described in our guide to verifying a sending domain. A DMARC record at the root domain covers subdomains by default, and you can publish a record on a subdomain when you need a different policy. Use aggregate reports to confirm that each stream passes before you tighten policy.
IP addresses and pools
Separate subdomains deliver most of the benefit. Separate IP addresses add isolation for senders with enough volume to keep each address busy and warm. A low volume spread across several IPs warms slowly and looks erratic. If you use dedicated IPs, assign one pool to each stream. Our guide to dedicated vs shared IPs explains how to decide, and our warm-up guide covers the ramp-up.
Settings that should differ between streams
| Setting | Transactional | Marketing |
|---|---|---|
| Tracking | Often off for security messages; light for receipts | Click tracking on, with a custom tracking domain |
| Unsubscribe | Usually not a list-style unsubscribe for essential messages | Required, with list-unsubscribe headers |
| Sending pattern | Steady and immediate, triggered by events | Scheduled batches and throttling |
| Suppression | Suppress hard bounces; handle with care | Suppress bounces, complaints and unsubscribes |
| List source | Your own users and customers | Opted-in subscribers only |
| Content | Short, plain, one purpose | Designed, with images and calls to action |
Marketing mail should carry the headers that make unsubscribing easy, as covered in our one-click unsubscribe guide. Keep the suppression lists described in suppression list management in sync, and be deliberate about whether an unsubscribe from marketing should also affect transactional mail. Usually it should not.
Keep transactional mail clean
- Do not add promotions or banners to receipts and alerts. They change how the message is perceived and can change how it is classified.
- Send only to addresses that belong to real users, and validate addresses at sign-up to avoid bounces.
- Keep volume steady, and give the stream a sending history before an important launch.
- Never send imported or purchased lists on this stream.
- Monitor bounce and complaint rates daily, because small problems matter on a small stream.
A safe migration plan
- Inventory. List every system that sends email as your domain, including billing, support and product tools, and classify the messages.
- Create subdomains and authenticate. Publish records and verify each subdomain before sending anything from it.
- Start with the smallest stream. Move one message type to its new subdomain and send a small share first.
- Ramp up over weeks. Increase the share steadily while you watch bounces, complaints and placement.
- Update the application. Change From addresses, templates and links to use the new subdomain, and keep reply handling working.
- Monitor each stream. Use reputation data for each subdomain, including Google Postmaster Tools, and set alerts.
- Retire the old setup. When the new streams are stable, stop sending from the old shared configuration and remove unused records.
Do not move everything on one day. A new subdomain has no history. Sending all your volume from it at once looks abnormal to filters. Move in stages so that each stream earns its reputation.
How to tell whether the split worked
Separation is an investment, so measure the result. Before you start, record a baseline for each message type: delivery rate, bounce rate, complaint rate and, where you can see it, inbox placement from a few test accounts at the main providers. After the migration, compare the same figures for each stream separately. You are looking for three things.
- Transactional stability. Delivery and placement for receipts and resets should be steady, and should no longer move when a campaign goes out.
- Marketing visibility. Complaint and bounce rates for promotions should now be clear on their own. A poor result is a signal about the list or the content, not a hidden drag on other mail.
- Faster diagnosis. When something changes, you should be able to say which stream caused it within minutes, using per-subdomain data.
Give the new subdomains several weeks before judging them. Reputation is built from a pattern, and early numbers on a small volume swing widely. If a stream looks weak, resist the urge to merge it back. Use the separation to find the cause: check list quality, review consent, tighten suppression and slow the sending rate.
A worked example: an online shop
An online shop sends about the same number of order notices and promotional emails each month, all from one domain. After a large sale campaign, customers report that order confirmations arrive in spam. The cause is not the receipts themselves but the shared reputation, which fell when the campaign produced more complaints than usual.
The shop creates orders.example.com and news.example.com, authenticates both and moves order notices first, a little at a time. Marketing follows a few weeks later on its own subdomain, with a custom tracking domain and one-click unsubscribe. The next campaign still produces a rise in complaints, but the effect stays on the marketing subdomain. Order confirmations keep arriving in the inbox, and the team can see exactly which segment caused the complaints and remove it. The problem is the same, but its consequences are contained.
Mistakes to avoid
| Mistake | Result | Better approach |
|---|---|---|
| Sending a newsletter from the transactional subdomain | Complaints damage password resets | Keep promotions on the marketing subdomain |
| Using the root domain for bulk mail | Staff email shares a risky reputation | Use subdomains for all bulk and system mail |
| Forgetting DMARC alignment on a new subdomain | Mail fails authentication | Authenticate each subdomain and test headers |
| Many tiny IP pools | Low volume per IP and slow warm-up | Use fewer pools, or none until volume grows |
| One suppression list for everything, applied blindly | Needed messages blocked after a marketing unsubscribe | Keep scope rules explicit per stream |
Planning to split your streams? Tell us what you send and from where, and we will suggest a subdomain and IP layout.
Further reading and sources
Frequently asked questions
What is the difference between transactional and marketing email?
Transactional email is triggered by an action the recipient took or by their account, such as a receipt, a password reset or a shipping notice. Marketing email is sent to promote something, usually to a list. The line matters for law and for deliverability, because recipients expect and engage with the first far more than the second.
Why should I separate the streams?
Mailbox providers build reputation for domains and IP addresses from recipient behaviour. Promotions usually draw more complaints and lower engagement than receipts. If both share one reputation, a weak campaign can push your password resets towards spam. Separate streams keep the damage contained.
Do I need separate IP addresses?
Not always. Separate subdomains give most of the benefit because domain reputation matters a great deal. Separate IPs add isolation at the network level and make sense once your volume is high enough to keep each one warm. Our guide to dedicated and shared IPs helps you decide.
Can I use one domain with different subdomains?
Yes, and it is the most common design. For example, orders.example.com for transactional mail and news.example.com for marketing. Both belong to the same organisational domain, so a single DMARC policy at the root can cover them, while each subdomain builds its own reputation.
Is a receipt with a promotion inside still transactional?
Be careful. Adding marketing content to a transactional message can change how it is classified by law and by filters. Keep transactional messages focused on their purpose, and place promotions in separate marketing mail that people opted into.
Do transactional messages need an unsubscribe link?
Rules differ by region and message type. Genuine transactional messages that the recipient needs, such as a receipt, are usually treated differently from marketing mail. Marketing mail should always include a clear unsubscribe route. Ask your legal adviser how the rules apply to your messages.
What if my transactional volume is very small?
A small volume of transactional mail on a brand-new subdomain can be slow to build reputation. Start the subdomain early, send consistently and keep it clean. Do not send bulk campaigns from it, since that defeats the purpose of separation.
How do I handle cold or purchased lists?
Do not send them on either stream. Mail to people who have not opted in produces complaints and bounces that harm reputation, and it can breach laws and provider policies. Build lists through consent instead.
How long does a migration to separate streams take?
The DNS work takes hours. Building reputation on a new subdomain takes weeks, because volume should be introduced gradually. Move a small share of one message type first, watch the results and increase over several weeks.