Two kinds of email
Every email a business sends is one of the two, and the test is purpose. A message whose purpose is to inform the recipient about something they initiated, or that the relationship requires, is transactional: order confirmations, shipping updates, receipts, password resets, account alerts, appointment reminders, invoices. A message whose purpose is to promote a product, a service or the brand is promotional, whatever it is called: a newsletter, a sale announcement, a product launch, a re-engagement series, a reminder about an unfinished purchase.
The distinction is older than email. Regulators who police direct marketing draw it, mailbox providers draw it when they decide what their users want, and recipients draw it instantly when they open the message. The UK regulator's direct marketing guidance, listed in sources, is one published example: it separates service messages that a customer needs from marketing that a business wants to send, and makes clear that the content and purpose of a message decide which it is, not the label on the campaign. Rules vary by jurisdiction and nothing here is legal advice; the principle, though, is widely shared.
Why it matters is practical. Transactional email is the most trusted mail a business sends, because people are waiting for it. Promotional email is the least, because nobody asked for this particular message. Mixing them lends the trust of one to the other for a while, and then spends it. The campaigns section covers the promotional side in depth; this page is about the boundary and what to do on each side of it.
Compare table
Promotional email vs Transactional email
| Row label | Promotional email | Transactional email |
|---|---|---|
| Purpose | Promote a product, offer, content or the brand | Confirm, inform or enable something the recipient initiated |
| What triggers it | The sender's decision: a campaign send, a scheduled series, a behavioural flow aimed at a sale | The recipient's action or a system event: an order, a sign-up, a reset request, a delivery |
| Consent basis | Requires a lawful basis for marketing, consent or an equivalent allowance, varying by jurisdiction | Sent as part of the service the recipient asked for; no marketing consent needed |
| Who receives it | The consented, segmented list; anyone can be excluded | Only the person the event concerns; cannot be segmented out |
| Unsubscribe | Required, visible, honoured promptly; a preference centre where volume is high | Generally not expected for pure service content; opting out of marketing must not stop it |
| Content limits | Free to sell, within the promise made at sign-up and the rules on claims | Service content first; marketing content minimal or absent, or the message becomes promotional |
| Timing | Chosen by the sender; batched; tolerates minutes of delay | Expected within seconds of the event; delay is a failure the recipient notices |
| Sending infrastructure | Marketing platform, bulk sending, often a dedicated subdomain | Application or transactional provider, event-driven, its own authenticated subdomain |
| Reputation profile | Carries the complaint and unsubscribe risk of the list | Carries the trust of expected mail; damaged only by leakage from marketing |
| Deliverability dependence | List quality, engagement and sending habits | Authentication and system reliability |
| Volume pattern | Spiky: large batches on send days | Steady: follows business activity |
| Measurement | Opens, clicks, conversions, revenue per send, unsubscribes and complaints | Delivery, latency, bounce reasons, and whether the recipient completed the task |
| Ownership | Marketing | Product, engineering or operations, with marketing consulted on design |
| Failure mode | Goes to spam, or unsubscribes climb | Does not arrive, or arrives late, and support tickets follow |
Where the line sits
The hard cases are the messages that serve both purposes. A shipping confirmation with a "you may also like" block. A welcome email that confirms the account and then introduces the product range. A receipt with a discount code for the next order. An abandoned basket reminder that the shop describes as a courtesy. The question in each case is what the message is for, and the honest test is to ask what would be left if the promotional content were removed. If the recipient would still need the message, it is transactional with marketing attached, and the marketing is the problem. If nothing useful would remain, it was promotional all along.
Three rules of thumb follow. First, a reminder about an unfinished purchase is promotional: the shopper has not transacted and the purpose is to prompt a sale, which is why the abandoned cart flows tutorial treats consent and unsubscribe as requirements rather than options. Second, the first message after a sign-up can be transactional if it confirms the account and explains what happens next, and becomes promotional at the point it starts selling; many businesses send a short confirmation as transactional and start the marketing welcome series on the consented stream a little later. Third, where a message must carry both, the service content leads, the promotional content is clearly secondary and small, and the message is treated as marketing for consent and unsubscribe purposes. The list building and consent guide covers how the consent basis is captured and recorded, which is what makes the second and third rules workable. A chaser on a quote the customer has not yet accepted raises the same question as a basket reminder, and the tutorial on automating quote follow-ups applies these rules to it.
Where the position is unclear in a given market, the safer classification is promotional, because the cost of treating a marketing message as transactional is a complaint or a penalty, and the cost of treating a transactional message as marketing is an unsubscribe link that nobody uses.
Infrastructure and streams
The two kinds of mail should not share a pipe. Promotional email carries the risk of the list: unknown addresses, people who forgot they subscribed, spam-trap hits, bursts of volume on send days. Transactional email carries none of that, and a receipt that lands in spam because a sale campaign drew complaints the same morning is the predictable result of sharing a sending identity.
Separation happens at a few levels. The sending domain or subdomain: marketing on one subdomain, transactional on another, each with its own authentication recordsRecords and signatures, SPF, DKIM and DMARC, that let mailbox providers check that a message comes from the domain it claims., so that reputation is tracked separately by mailbox providers. The sending system: a marketing platform for campaigns and flows, an application-side or transactional provider for event-driven mail, so that a campaign queue cannot delay a password reset. The suppression logic: an unsubscribe from marketing suppresses marketing only, and a hard bounce suppresses both. Google's sender guidelines, listed in sources, set out the authentication expected of senders to its mailboxes, including SPF, DKIM and DMARC, the one-click unsubscribe requirement for marketing and subscribed messages, and a complaint-rate ceiling stated on the help page; the deliverability guide covers how to meet them and how to monitor reputation per stream. The point here is that separate streams let each be judged on its own behaviour.
Separation has costs. Two systems to maintain, two sets of templates, two places where the brand has to look consistent, and a handover between marketing and engineering whenever a transactional template changes. The costs are worth paying as soon as the business sends promotional mail in any volume, and most businesses that resist end up separating the streams after the first deliverability incident rather than before it.
An online retailer separates its streams after a bad week
An online furniture retailer sent everything from one domain through its marketing platform: a weekly newsletter to 140,000 subscribers, a monthly sale announcement, and all order confirmations and delivery updates. A clearance sale drew 410 spam complaints in a day, and for the following week around 9% of order confirmations landed in spam, producing 230 support tickets from customers who thought their order had not gone through. The fix took a month: order and delivery mail moved to a transactional provider on its own subdomain with separate SPF, DKIM and DMARC records, and the marketing platform kept the newsletter and promotions on another subdomain with one-click unsubscribe enabled. In the quarter after the change, the transactional stream delivered 99.8% of messages to the inbox regardless of what the marketing stream did, and the retailer rebuilt the marketing subdomain's reputation separately with a re-engagement pass that removed 22,000 dormant addresses.
Using transactional email responsibly
Transactional email is read at a rate no campaign approaches, which makes it tempting as a marketing surface. The temptation should be resisted in most cases, for three reasons. Promotional content changes the classification, which can bring the message under consent and unsubscribe rules it was exempt from. It dilutes the message the recipient needed, so that the shipping date is harder to find under the cross-sell. And it teaches recipients that mail from the transactional address is partly advertising, which is the trust the stream depended on. The same split decides an app's push settings, where the tutorial on notification preferences by topic keeps order updates and offers in separate topics so that turning off one never silences the other.
What transactional email can do, responsibly, is be excellent at its job. A clear subject line that states the event. The essential facts first: the order, the amount, the date, the next step. A link to the account or the order page. A reply address that reaches a person. Consistent branding so that it is recognisably from the business. Prompt sending, because the recipient is waiting. Where a secondary message is justified, such as a short note on how to track the parcel or how to get help, it belongs below the service content and stays informational rather than commercial. The same holds for messages about a delay or disruption, which the guide to proactive service messages keeps free of offers, treating any goodwill as a remedy rather than a promotion.
Measurement follows the purpose. The promotional stream is measured on engagement and outcome: click-through (CTRShare of impressions that result in a click.), conversion rate (CVRShare of visits or clicks that convert.) on the landing page, revenue per sendEmail-attributed revenue divided by the number of emails delivered., and the unsubscribe and complaint figures that show whether the list is tolerating the frequency. The transactional stream is measured on reliability: delivered on time, bounce reasons investigated, and whether the recipient completed the task the message enabled, such as resetting the password or confirming the address. Those are different key performance indicators (KPIA metric tied directly to an objective.) and should sit on different reports; a transactional stream judged by click-through will be pushed towards marketing content, which is the wrong direction. When customers report that receipts or password resets never arrived, the diagnosis for order and account emails not arriving separates a message never sent from one refused or filed as junk. Design craft for the promotional side, including structure, subject lines and calls to action, is covered in the newsletter design and copy guide.
For promotional sends that carry a price cut, the discount depth test shows how to choose the discount level on profit rather than orders.
Common mistakes
- One domain for everything. The marketing list's complaints decide whether receipts arrive.
- Marketing in the receipt. A prominent offer turns a service message into a promotional one, with the rules that follow.
- Calling an abandoned basket email transactional. The shopper has not transacted; the purpose is a sale.
- Suppressing transactional mail on marketing unsubscribe. The person who opted out of promotions still needs the password reset.
- Routing transactional mail through the campaign queue. A big send delays the messages people are waiting for.
- Measuring the transactional stream on clicks. It rewards the wrong behaviour; measure delivery, latency and task completion.
- Assuming one jurisdiction's rules. The line between service and marketing is drawn differently in different markets; the stricter reading is the safer default.
- No authentication on the transactional subdomain. The most trusted stream is the one most worth protecting with SPF, DKIM and DMARC.
