Your password reset and your Black Friday promotion are both emails, but they should not be treated the same way.
One is something your customer is waiting for: a transactional email. The other is a marketing email, a promotion you want them to read. The 2 have different purposes, sending patterns, unsubscribe rules and deliverability risks.
When both types of email share the same sending setup, problems with your marketing email can start affecting the messages people actually need, including receipts, login codes and account alerts.
This guide explains the difference between transactional and marketing email, when you should separate them, and how to set up each stream so problems in one do not spill into the other.
What is the difference between transactional and marketing email?
Transactional email is a message triggered by something the recipient did, and it exists to complete or update that action, for example a password reset, an order receipt or a shipping notice. Marketing email promotes a product or service and goes out on your schedule to a list, for example a newsletter, a sale announcement or a product launch. US law, specifically the CAN-SPAM Act, decides which type an email is by what the message is for, not by who receives it.
In the US, the FTC's CAN-SPAM guide calls this the "primary purpose" test. If an email's main purpose is to advertise or promote a product or service, it is a marketing message. It counts as transactional only if its content fits one of these 5 categories:
Completing or confirming a purchase the recipient agreed to
Warranty, recall, safety or security information about something they bought
Changes to their account, subscription or membership, including balance updates
Information about their employment or employee benefits
Delivering goods or services they are entitled to, such as product updates
The FTC also warns that an ongoing relationship with someone does not make everything you send them transactional.
For example, when a customer buys a pair of running shoes, the order confirmation is transactional. The "you might also like these socks" email 3 days later is marketing, even though it mentions the same order. Our guide to transactional emails covers more examples.
Transactional email | Marketing email | |
Purpose | Completes or updates an action the recipient took | Promotes a product, service or content |
Trigger | A user event, for example a signup, purchase or password request | Your calendar or an automation you design |
Consent | Implied by the transaction itself | Mailbox providers expect clear opt-in |
Unsubscribe rules | No opt-out required, as long as the content stays transactional | Must include a working opt-out and honor it |
Expected delivery | Seconds; a late password reset is a failed one | Minutes to hours is acceptable |
Volume pattern | Steady, follows user activity | Spiky, with large batches on send days |
Why sending both from one domain puts your password resets at risk
Gmail, Yahoo and Outlook keep a reputation score for every domain and IP address that sends email, based on how recipients react to that mail. If your newsletters and your receipts both come from brand.com, they are scored as one sender. Spam complaints on a promotion lower the score for brand.com, and your receipts get filtered by that same lower score.
Yahoo says this directly in its sender best practices. It tells senders not to send bulk or marketing mail from the same IPs used for transactional mail and alerts, because each IP and DKIM domain has its own reputation, and it recommends segregating email by function. Google's sender guidelines make the same point from a different angle, telling senders who use more than 1 IP to give each message type its own IP, for example one for account notifications and another for promotions.
Here is how that plays out. An online store sends its newsletters and its order confirmations from the same domain, store.com. A sale email goes to customers who bought once 2 years ago, and some of them mark it as spam. Gmail now sees store.com as a sender people complain about, and it starts filtering more mail from store.com. The next morning, order confirmations land in spam, and customers email support asking whether their order went through.
If the store had sent its newsletters from news.store.com and its order confirmations from orders.store.com, the complaints would have landed on news.store.com. The confirmations would have kept their own clean record and kept reaching the inbox.
LoriBeth Blair, an email deliverability consultant who works with SendX, says people really don't understand "the devastation that bad deliverability can cause" until they are in the middle of it. When a domain's reputation falls, the damage doesn't stay with the newsletter. Password resets, one-time passcodes and support replies start failing too.
Many teams assume transactional mail is so clearly wanted that it always gets through. In our experience at SendX, a password reset sent from a damaged domain inherits that damage, because providers score the sender as well as the message. Our guide to email sender reputation explains how that scoring works.
Where the legal line sits when you mix content
Receipts get high open rates, so marketing teams often want to add promotions to them. The FTC's mixed-content test decides what that message becomes. If a recipient reading the subject line would reasonably conclude the email is an ad, or if the transactional content does not appear mainly at the beginning, the FTC treats the whole email as a marketing message, and it must meet every CAN-SPAM requirement, including a working opt-out. According to the FTC, each separate email that violates the law can draw penalties of up to $53,088.
For example, an email with the subject line "Your receipt" that opens with the order details and closes with 1 line about a new product line stays transactional. The same email with the subject line "Your receipt plus 30% off your next order," or one that opens with a hero banner for the sale, is a marketing message. Once it is a marketing message, you need an unsubscribe link, a physical address, and a process that honors opt-outs within 10 business days.
Gmail applies its own standard on top of the law. Its bulk sender requirements list mixing content types as a practice to avoid, for example promotions in sales receipts, and they require marketing messages to support one-click unsubscribe once you send more than 5,000 messages a day to Gmail accounts. Our CAN-SPAM Act guide covers the rest of the legal requirements.
How SendX decides which of its own emails are transactional
The law tells you what you are allowed to send without an unsubscribe link. It doesn't tell you where each email should be built: in your product's code, where your engineers own it, or in your marketing platform, where your marketing team can edit and test it. At SendX, we use a stricter internal rule for our own emails: an email stays transactional only if it passes all 5 of these tests.
Its purpose is to confirm a transaction or a critical change. That covers account changes like a signup, payment or cancellation, security events like a password reset, and setup steps like a verified domain.
It has to arrive within seconds. A delay would break what the user is trying to do.
It contains data unique to that user. A login token, a receipt amount, DNS records or a one-time link, not pre-written copy.
It has no promotional content. No upgrade pitch, no feature highlight, no call to action beyond what the transaction needs.
Marketing has no reason to change it. The copy is fixed, with no A/B tests planned and no place in a sequence.
If even one test fails, the email moves to our marketing platform. That includes emails triggered by something the user did. A "congrats on sending your first campaign" email is triggered by a user action, but its purpose is to celebrate and keep people engaged, so we treat it as marketing. The same goes for a nudge after 14 days without a campaign. The trigger doesn't decide the type. The purpose does.
When we are unsure, we pick marketing. Putting a borderline email in the marketing platform costs very little. Putting a marketing email in the product's code risks the reputation of every password reset and receipt we send, and it means every copy change needs an engineering ticket instead of a quick edit by the marketing team.
How to separate transactional and marketing email
In the steps below, a "stream" means all the email of one type: your transactional stream and your marketing stream. You can separate the 2 streams at 3 layers, and the steps build them in order:
The domain, which gives each type of email its own reputation
The infrastructure, meaning the IP addresses or email providers that send each type
Authentication and unsubscribe handling, which prove each type is legitimate and keep its rules separate
1. List every email you send and sort it by primary purpose
List every email you send in one spreadsheet: one-off campaigns, automated emails like welcome series and abandoned-cart reminders, and the emails your product sends on its own, like receipts and login codes. Mark each one as transactional or marketing using the 5 tests above, and flag any hybrid messages, for example a welcome email that is half account setup and half product tour. For every hybrid, either strip the promotion or move the whole email to the marketing stream. If you can't decide, choose marketing.
2. Give each stream its own subdomain
Send transactional mail from one subdomain and marketing mail from another, for example mail.brand.com for receipts and resets and news.brand.com for newsletters and promos. Keep the root domain for your team's day-to-day mail.
This gives Gmail and Yahoo 2 separate identities to score. In our view at SendX, it is the most useful split for a small sender, because complaints on news.brand.com land on that subdomain first while mail.brand.com keeps the history it earned. Learn how to monitor your domain reputation once both are live.
3. Authenticate each subdomain on its own
Publish SPF and DKIM for each sending subdomain, and set a DMARC policy that covers both. Use a different DKIM signing domain for each stream, since Yahoo treats each DKIM domain as a separate reputation. Our SPF, DKIM and DMARC setup guide covers the DNS records, and our post on transactional email authentication covers the rest.
Outlook's high-volume sender rules now require SPF, DKIM and DMARC for domains sending more than 5,000 emails a day, with non-compliant mail routed to Junk first and rejected after that.
4. Split IPs or providers once your volume supports it
Subdomains separate your domain reputation, but a shared IP still ties your streams together at the network level. Once your marketing volume is large and steady enough to keep its own IP warm, move the 2 streams onto separate IPs or IP pools. Teams whose product depends on login codes can go further and send transactional mail through a different provider, which also keeps 1 outage from taking down both streams.
Below that volume, our view is that a well-managed shared pool with separate subdomains beats a dedicated IP you can't keep warm. Our guide to dedicated IPs for email explains where that threshold sits.
5. Keep unsubscribe handling on the marketing stream
Every marketing email needs a visible unsubscribe link and a List-Unsubscribe header. Yahoo's requirements ask bulk senders to support one-click unsubscribe, honor requests within 2 days, and keep the spam rate below 0.3%. RFC 8058 defines how one-click works, with the header pointing to an HTTPS address the mailbox provider can POST to and a DKIM signature that must cover both unsubscribe headers.
Transactional mail doesn't need an opt-out, and it shouldn't offer one that unsubscribes people from receipts. A customer who unsubscribes from your newsletter should still get their password reset.
6. Keep transactional templates purely transactional
Separated setups drift back into trouble at this step more than any other, in our experience. Someone adds a "refer a friend" banner to the shipping notice, and the email is now a marketing message travelling on your transactional subdomain without an unsubscribe link. Give transactional templates an owner who reviews every change, and move any cross-sell to a follow-up email on the marketing stream.
7. Monitor each stream separately
Track bounces, complaints and placement for each subdomain, not as one blended number. LB's view is that basic delivery, open and click rates no longer cut it; you need to understand those metrics by mailbox provider. A blended dashboard can look healthy while Gmail filters your newsletter and Outlook defers your receipts. If your transactional placement slips, our guide to getting transactional email past spam filters covers the fixes.
How SendX handles transactional and marketing streams
Separating transactional and marketing email sounds simple until you have to manage 2 domains, 2 sending setups, bounce data, suppression lists, authentication and reporting across different tools.
You can send both through SendX, using campaigns and automations for marketing and the API or SMTP for transactional messages. SendX then helps you get both types of email delivered.
If your transactional email goes through another provider, such as Amazon SES, SendGrid or Postmark, SendX records the hard bounces from that connected provider and suppresses those addresses from future marketing sends. You are not continuing to send newsletters to an address another part of your email stack already knows is undeliverable.
If you send both streams through SendX, you manage marketing and transactional sending from the same platform while keeping their jobs distinct. Marketing emails get the unsubscribe handling they need, including one-click unsubscribe served from your own domain. Transactional messages such as password resets and receipts keep reaching customers even after they opt out of your newsletters.
As your sending grows, SendX gives you room to build a more isolated setup, with your own sending domains and a dedicated IP add-on, instead of forcing every message through the same reputation.
The result is a cleaner email stack: fewer disconnected systems to monitor, a clear line between the messages customers need and the messages you want them to read, and more control over the reputation behind both.
If your business sends both kinds of email, start a free SendX trial.
FAQs
Can I put a promo banner in an order confirmation?
Legally, a small secondary mention can stay transactional if the subject line doesn't read as an ad and the order details come first. Gmail advises against promotions in sales receipts at all, so our view at SendX is to keep receipts clean and send the cross-sell as a separate marketing email.
Do I need a separate ESP for transactional email?
Not if your platform lets you send each stream from its own subdomain, with its own authentication and, at higher volume, its own IPs. A separate provider adds a hard wall between streams, but it also means 2 sets of DNS records, templates and reports to maintain.
Is a subdomain enough, or do I need a separate IP?
For most small senders, our view is that separate subdomains on a well-managed shared pool are enough, because the domain carries most of the reputation you control. Add separate IPs once each stream has the steady volume to keep its own IP warm.
Is a welcome email transactional or marketing?
Usually marketing. The email that verifies a new address with a unique link is transactional: the user needs it within seconds, and it only works for them. The welcome email that introduces your product is marketing, even though a signup triggered it, because its job is to get people using the product, and your marketing team will want to test and improve it. At SendX, our verification email is transactional and our welcome email lives in our marketing platform. If one template does both, split it into 2 emails.
Will moving marketing to a new subdomain reset my reputation?
A new subdomain starts with little sending history, so treat the move as a warm-up. The smoothest moves we see at SendX start with the most engaged subscribers and raise volume over several weeks, while transactional mail keeps flowing from the subdomain with the good record.
