A customer wrote in last month with a wrecked domain. He had a list of users and a product update to announce. Instead of using our campaigns feature, he pushed the whole thing through the bulk send API as if it were transactional mail. No rate control. No suppression list. No unsubscribe link.
Within an hour the deferrals started. Gmail and Yahoo throttled him because nobody sends that volume that fast from a cold lane. Then the spam complaints came in, fast, because there was no way for anyone to opt out. Some of the people he hit had already unsubscribed from him before. By the end of the day his domain reputation was down, and his real transactional mail, the password resets and receipts people actually needed, started landing in spam too.
That is what happens when you treat these two types of email as the same thing. They are not sent the same way. They are not governed by the same rules. ISPs do not read them the same way.
The mistake that tanks domains: sending a marketing campaign through a transactional pipeline to skip the unsubscribe link. You reach people who opted out, complaints spike, and your domain reputation drops. Reputation is the one thing you cannot quickly buy back.
A transactional email is triggered by something one user just did. A password reset. An order confirmation. A login alert. An email verification. A shipping notification.
The defining trait is that it is time sensitive and expected. The user took an action and is waiting for the result. If a password reset shows up ten minutes late, or in the spam folder, that is a broken product. So these emails get treated as important by ISPs, and they get sent one at a time as the events happen, not in a batch.
I wrote a full breakdown of the types in what is a transactional email. The short version: if a single user's action caused it, it is transactional.
A marketing email is the same message sent to many people at once. A newsletter, a product announcement, a promotion, a re-engagement push. Nobody is sitting there waiting for it. You decided to send it.
Because it goes to a list, it carries a different set of obligations. You need consent to be on that list. You need an unsubscribe link in the body. You need a List-Unsubscribe header so inbox providers can offer one-click opt-out. You need to honor every opt-out, every time. And you need to send at a controlled rate so you do not look like a spammer hitting an ISP all at once.
Here is the side by side I give to every founder who asks.
| Transactional | Marketing |
|---|
| What triggers it | One user's action | You decide to send |
| Audience | A single recipient | A list |
| Consent needed | No, it is expected | Yes, opt-in |
| Unsubscribe link | Not required | Required |
| List-Unsubscribe header | Optional | Required |
| Rate limiting | Send immediately | Controlled, gradual |
| Open and click tracking | Avoid it | Standard |
| Suppression rules | Suppress hard bounces | Suppress bounces and opt-outs |
| Sending reputation | Should stay clean | Carries more risk |
The legal line matters too. Under CAN-SPAM and similar rules, a transactional email is exempt from the unsubscribe requirement because the user asked for it. A marketing email is not. The moment you add a promotion to a transactional email, you can lose that exemption.
This is the part people skip. Marketing email is riskier than transactional email. It draws more complaints, more spam folder placement, more unsubscribes. That is normal for marketing.
If you send both from the same domain, the risk from your marketing mail drags down the reputation of your transactional mail. Now your receipts and password resets inherit the spam score of your last promotion. I have seen founders lose their login flow to the spam folder this way, and they have no idea why because the transactional email itself was fine.
The fix is separation. Send transactional and marketing from different subdomains so they build separate reputations. If one lane has a bad week, the other is untouched. The same logic is why you warm up a new sending domain slowly instead of blasting it on day one, and it is one of the bigger factors in how spam filters score you.
A small thing that bites people. If you wrap links in a transactional email with open and click tracking, you add the same markers a marketing email carries. Gmail and others read those markers and decide the message looks promotional. Your receipt lands in the Promotions tab or worse, in spam.
Keep transactional emails clean. Plain links, no tracking pixels, no campaign UTM tags. Save the tracking for marketing, where it belongs.
People send campaigns through the transactional API on purpose, because the transactional path does not force an unsubscribe link. They think they have found a shortcut to email everyone, including people who opted out.
It works for about a day. Then the complaints arrive, because the people who unsubscribed report the mail as spam. Spam complaints are the single fastest way to destroy domain reputation. Once Gmail decides your domain sends unwanted mail, everything you send, transactional included, starts getting filtered. The shortcut costs you the whole channel.
An unsubscribe is a healthy signal. A spam complaint is a wound. Always pick the unsubscribe.
When I designed AutoSend, I did not want one generic send endpoint that left people to figure this out on their own. So transactional and marketing automation are two separate features with different defaults.
Transactional sends go out immediately, one event at a time, optimized for speed, with no unsubscribe link forced because they do not need one. Campaigns run through a different lane that enforces the List-Unsubscribe header, respects your suppression list, and ramps the send rate so ISPs stay happy. They build separate reputation by design. You would have to work hard to make the mistake my customer made, because the campaigns path will not let you ignore opt-outs.
What is the difference between transactional and marketing email?
A transactional email is triggered by one user's action and is expected, like a password reset or receipt. A marketing email is sent to a list because you decided to send it, like a newsletter or promotion. Marketing email requires consent and an unsubscribe option. Transactional does not.
Can I include marketing content in a transactional email?
You can add a small amount, but it is risky. If the promotional content becomes the main purpose of the email, you lose the legal exemption from unsubscribe rules, and ISPs may start treating the whole message as marketing. Keep receipts and resets focused on the transaction.
Do transactional emails need an unsubscribe link?
No. Because the user asked for them, transactional emails are exempt from the unsubscribe requirement under CAN-SPAM and similar laws. Marketing emails always need one.
Should transactional and marketing email use the same domain?
No. Send them from separate subdomains so they build separate sending reputations. That way a rough week on marketing does not push your password resets into spam.
Why did my transactional emails start going to spam after I sent a campaign?
Most likely you sent both from the same domain, and the campaign drew complaints that lowered the shared reputation. Split them onto different subdomains and the transactional mail recovers its own standing.
Is a newsletter transactional or marketing?
Marketing. A newsletter goes to a list and is not triggered by an individual action, so it needs consent and an unsubscribe link.
At Peerlist we run password resets, verification, and login alerts through the transactional path, and product announcements through campaigns, on separate subdomains. The two never touch each other's reputation. That separation is the reason our login emails arrive in seconds even in a week when we send a big announcement.
If you want both lanes set up correctly from the start, AutoSend gives you transactional and marketing as separate features so you do not have to wire the reputation split yourself.