Transactional vs Marketing Email: Key Differences (2026)

A transactional email is sent to one person because of something they did or something that changed on their account: a password reset, a receipt, a shipping update. A marketing email promotes something: a newsletter, a product launch, a sale, or an upgrade offered to one user. The deciding test is purpose. If the email completes or reports on something the user already started, it's transactional. If it promotes something, it's marketing, even when a user's action triggered it. That one difference decides whether you need an unsubscribe link, what consent you need, and why the two shouldn't share a sending reputation.

Transactional vs marketing email at a glance

Most guides split email into two buckets. In practice there are three, because a lot of the email a product sends is triggered by user behavior but written to move people forward.

What is a transactional email?

A transactional email completes or confirms something the recipient already did, or updates them about a relationship they already have. Common examples:

• Email verification and double opt-in confirmations
• Password resets and magic-link sign-ins
• Order confirmations, receipts, and invoices
• Shipping and delivery updates
• Security alerts, like a new-device login or a changed password
• Notices about changes to the terms or features of an account

These are one-to-one, sent in real time, and the recipient is often waiting for them. A marketing email that arrives an hour late is a non-event. A login code that arrives an hour late is a support ticket. For more on the category, see what is transactional email⁠.

What is a marketing email?

A marketing email exists to promote, inform, or bring people back. The primary purpose is commercial: you want the reader to buy, upgrade, return, or pay attention. Examples:

• Newsletters and content roundups
• Product launches and feature announcements
• Promotions, discounts, and seasonal campaigns
• Re-engagement emails to inactive users

Marketing is usually one-to-many, planned ahead, and tolerant of delay. It also tends to draw more spam complaints, because some people who opted in still hit "report spam" instead of unsubscribing.

Where lifecycle and activation email fits

Lifecycle email is the middle category. It's triggered by what one user did, which makes it feel transactional. But its goal is to change what that user does next, which makes it marketing. Examples:

• A nudge 24 hours after signup to someone who hasn't created their first project
• A reminder on day 10 of a trial to a user who hasn't tried the feature paid customers use most
• A usage-limit warning with an upgrade path
• A win-back email 30 days after someone's last login

The test is purpose. A welcome email⁠ that only confirms the account and explains how to sign in can be transactional. The third email in the sequence, pushing a feature or an upgrade, is marketing, so it needs an unsubscribe link and belongs on your marketing stream.

This category matters more than its size suggests. It's where new users either reach the moment the product becomes useful to them (usually called activation) or quietly drift away. Transactional email is judged on speed. Lifecycle email is judged on whether more users take the next step. The drip campaign guide⁠ covers how to build these sequences so they stop as soon as the user reaches the goal.

What's the legal difference between transactional and marketing email?

This section explains the general shape of the rules. It's not legal advice, and the details vary by country, so check with counsel before relying on it.

CAN-SPAM (United States)

The CAN-SPAM Act classifies an email by its primary purpose. According to the FTC's compliance guide⁠, a commercial message must:

• Use accurate header and routing information
• Use a subject line that isn't deceptive
• Identify the message as an ad, unless the recipient gave prior affirmative consent
• Include a valid physical postal address
• Offer a clear way to opt out, able to process requests for at least 30 days after sending
• Honor opt-outs within 10 business days

A transactional or relationship message only has to meet the first requirement. It can't use false or misleading routing information, but it's exempt from the rest.

The primary-purpose test is where teams get caught. If an email mixes transactional and promotional content, the FTC treats it as commercial when a recipient reading the subject line would reasonably think it's an ad, or when the transactional content doesn't appear mainly at the beginning of the message. A shipping notice with a small product recommendation at the bottom is one thing. A "receipt" that opens with a coupon is a commercial email.

Two more points:

• There's no B2B exception. CAN-SPAM covers business-to-business email too.
• Opt-outs don't carry over. Someone who unsubscribes from your newsletter still gets password resets and receipts. Those are separate.

Each email that violates the law can carry a penalty of up to $53,088, per the FTC.

GDPR and ePrivacy (EU and UK)

In the EU and UK, the question is lawful basis. Order confirmations, password resets, and shipping updates generally rest on contract or legitimate interest: you're doing what the user asked for or expects as part of the service. They don't need marketing consent.

Marketing email is stricter than in the US. Under ePrivacy rules, and PECR in the UK, marketing email to individuals generally needs consent. The main exception is the "soft opt-in": you can email existing customers about your own similar products or services, as long as you offered an opt-out when you collected the address and in every message after. The UK version also covers people who were negotiating a purchase, such as by requesting a quote. The EU directive ties it to contact details collected in the context of a sale, and national rules vary. Where you rely on consent, GDPR requires it to be freely given, specific, informed, and unambiguous. Pre-ticked boxes and silence don't count.

The mixing risk shows up here too. Slip "you might also like" into a transactional message and the UK regulator, the ICO, treats the whole message as direct marketing.

Gmail and Yahoo sender rules

Mailbox providers add their own layer. Since February 2024, Google requires anyone sending about 5,000 or more messages a day to personal Gmail accounts (counted across a domain and its subdomains) to authenticate with SPF, DKIM, and DMARC, keep user-reported spam below 0.3%, and support one-click unsubscribe on marketing and subscribed messages. Transactional messages are exempt from the one-click unsubscribe requirement. Yahoo's rules for bulk senders are similar.

Why mixing the two hurts deliverability

Mailbox providers score sender reputation on how recipients react: spam complaints, bounces, spam-trap hits, and engagement. Marketing mail tends to produce more of the bad signals. Transactional mail usually produces far fewer, because people expect it.

Send both from the same domain and IP, and marketing complaints drag down the reputation your password resets depend on. A bad campaign on Tuesday can mean spam-foldered login codes on Wednesday, for users who never saw the campaign. It works the other way too: a promotion fired through your clean transactional path can spike complaints on the channel you most need to stay reliable. The Supabase auth emails going to spam⁠ post covers a common version of this.

How to separate transactional and marketing email

Isolate the streams so one can't hurt the other:

• Separate subdomains. Send transactional mail from something like mail.yourapp.com and marketing from news.yourapp.com, each with its own SPF and DKIM setup. Providers still look at the parent domain's history, so this reduces crossover rather than eliminating it.
• Separate IPs or IP pools, at higher volume. Once you send enough to keep a dedicated IP warm, keep transactional traffic on its own. Below that, subdomains do most of the work.
• Separate from-addresses. A recognizable transactional sender reassures people waiting for a code, and it makes per-stream reporting readable.
• Separate suppression lists. A marketing unsubscribe should never block a password reset. One shared list is how teams stop sending login codes to people who only meant to leave the newsletter.
• Separate reporting. If transactional metrics hold steady while marketing slides, the problem is contained. If both drop together, look at domain authentication.

Some providers enforce the split for you. Postmark, for example, puts transactional and broadcast mail in separate Message Streams. For a comparison of providers on this, see best transactional email services⁠. For the authentication side, see the email deliverability guide⁠.

Quick decision guide

When you're not sure which bucket an email belongs in, ask:

1. Does it complete or confirm a service the user requested, or report necessary account information? That's the transactional purpose test; the trigger alone doesn't decide.
2. Does it promote a product, offer, or upgrade? Marketing, whether sent to one person or a list.
3. Is the recipient waiting for it right now? Strong sign of transactional.
4. Is it trying to change what the user does next? Lifecycle. Treat it as marketing.
5. Does it promote anything, even partly? Then the whole email may count as marketing. Under CAN-SPAM it does if the promotion leads the email or the subject line reads like an ad. In the UK, any added marketing is enough.
6. Could the recipient reasonably want to stop getting it without losing service? Then it needs an unsubscribe link.

Where Dreamlit fits

The purpose test above applies whether you write the sending code or use a workflow platform. Dreamlit, the company behind this blog, supports auth, transactional, lifecycle, and broadcast email from your Supabase or Postgres database. Your AI agent builds the workflows, and you preview them with real data before publishing.

Dreamlit handles unsubscribes, bounces, and complaints. You still choose each message's purpose and consent requirements; a database trigger alone doesn't make it transactional.

Start a 7-day free trial⁠ or connect your agent.

References

• FTC: CAN-SPAM Act compliance guide for business⁠
• ICO: How do we comply with the PECR electronic mail marketing rules?⁠
• ICO: Key concepts for direct marketing using electronic mail⁠
• Directive 2002/58/EC (ePrivacy Directive)⁠
• EDPB Guidelines 05/2020 on consent⁠
• Google: Email sender guidelines⁠
• Google: Email sender guidelines FAQ⁠
• Yahoo Sender Hub: Best practices⁠
• Postmark: Message Streams⁠

---

Frequently asked questions

What is the difference between transactional and marketing email?

A transactional email is sent to one person because of something they did or something that changed on their account, like a password reset or a receipt. A marketing email promotes something, like a newsletter or a sale. The deciding test is purpose, not trigger: an email that promotes something is marketing even when a user's action triggered it.

Do transactional emails need an unsubscribe link?

Under the US CAN-SPAM Act, messages whose primary purpose is transactional or relationship content don't need an opt-out link or postal address, but they still can't use false or misleading routing information. If the subject line suggests an ad, or the transactional content isn't mainly at the beginning, the FTC treats the whole message as commercial. This is a general explanation, not legal advice.

Is a welcome or onboarding email transactional or marketing?

A welcome email that only confirms the account and gives access details can be transactional. Onboarding nudges, trial reminders, and upgrade prompts are triggered by behavior but exist to change what the user does next, so treat them as marketing, with an unsubscribe link and a separate sending stream.

Does GDPR treat transactional and marketing email differently?

Yes. Transactional messages like order confirmations and password resets usually rely on contract or legitimate interest, so they don't need marketing consent. Marketing email to EU and UK recipients falls under ePrivacy and PECR rules too, and generally needs consent or a narrow soft opt-in for existing customers, with an opt-out in every message.

If someone unsubscribes from marketing, can I still send them transactional email?

Yes. An unsubscribe from your newsletter doesn't stop receipts, password resets, or security alerts. Keep separate suppression lists so a marketing opt-out never blocks the transactional messages a user needs to use your product.

Is a password reset a marketing email if it has my logo and a footer link?

No. A logo, your address, and a link to your help center don't make an email commercial. Promotional content can, such as a coupon block or a 'you might also like' section. Under CAN-SPAM, the whole email counts as commercial if the subject line reads like an ad or the promotion comes before the transactional content, and UK guidance treats any added marketing as making it direct marketing. Keep transactional messages focused on the action the user took.

Should transactional and marketing email use different domains?

Send them from separate subdomains, for example mail.yourapp.com for transactional and news.yourapp.com for marketing, each with its own authentication records. Marketing draws more complaints, and separation makes it less likely a bad campaign delays or spam-folders a login code.