Transactional email vs marketing email
Transactional mail goes to one person because of something they just did: a receipt, a password reset, a shipping notice. Marketing mail goes to a list because you decided to write. The difference matters legally and practically. Marketing mail needs consent, an unsubscribe and a postal address, and it should never share a reputation with a password reset.
At a glance
- Category
- Sending
- Transactional
- Triggered by the recipient's own action, to one person
- Marketing
- Sent to a list, on your schedule
- Marketing needs
- Consent, an unsubscribe control and a postal address
- Unsubscribe stops
- Marketing only — service mail still goes out
- Usually split by
- Subdomain, so reputations stay independent
How it works
The distinction is about why a message was sent, not about its content or how it was built. A receipt triggered by a purchase is transactional even if it is beautifully designed; a monthly summary sent to everyone is marketing even if it contains only facts about their account. In practice systems encode the difference by keeping the two on separate sending domains, applying consent checks to one and not the other, and honouring an unsubscribe against marketing alone.
Why it matters
The legal obligations differ by jurisdiction and attach to marketing mail, so misclassifying a campaign as transactional to skip the unsubscribe is a risk rather than a shortcut. The practical reason is reputation: bulk mail attracts complaints, complaints attach to the sending domain, and a password reset sharing that domain arrives in junk on exactly the day somebody is locked out. Keeping them apart means the riskiest mail cannot take the most important mail down, and it costs nothing more than a second verified subdomain.
Example
A company sends receipts from a domain used for nothing else, and its newsletter from a subdomain. A reader unsubscribes from the newsletter; the contact is marked unsubscribed and receives no further campaigns, while their receipts keep arriving unchanged. A later campaign to an old segment raises complaints and placement for the newsletter subdomain suffers for a few weeks, without affecting a single receipt.
Common mistakes
- 01Adding a marketing paragraph to a receipt, which makes the whole message marketing in the eyes of most regulators.
- 02Sending both kinds from one domain, so a campaign's complaints decide whether password resets reach the inbox.
- 03Suppressing transactional mail on an unsubscribe, which stops receipts somebody still needs and is not what they asked for.
- 04Classifying a message by how it was built rather than by why it was sent, which is the mistake the distinction exists to prevent.
In Rasket
Both run through the same sending pipeline, and an unsubscribe stops broadcasts to that address while transactional mail still goes out. Broadcasts
Related terms
Frequently asked questions
Is a monthly account summary transactional?
It depends on whether the recipient's own action triggered it. A summary sent on your schedule to everybody is closer to marketing, and treating it that way is the safer reading.
Does transactional mail need an unsubscribe link?
No, and adding one confuses readers about what they are leaving. A receipt has no subscription behind it, so there is nothing to opt out of.
Do both kinds need authentication?
Yes, identically. Authentication is about proving the domain sent the message, which matters just as much for a password reset as for a campaign.
Last updated 16 September 2026.
Start sending this morning
Verify a domain and send your first email in minutes.