Skip to content
All articles

Guides · 27 October 2026 · 8 min read

Transactional vs marketing email: the differences that matter

Rampsend team

Two streams, one suppression list

Most products send two very different kinds of email. One kind is triggered by something a person just did: a receipt, a password reset, a sign-in link, a shipping notice. The other kind is sent because you want something from them: a newsletter, a launch announcement, a discount. They look similar in an inbox, but the law treats them differently, mailbox providers judge them differently, and if you mix them carelessly one can drag the other down.

What counts as transactional email

A transactional message exists to complete or support something the recipient started. If they didn't receive it, they would notice and probably contact you. Typical examples:

  • Account emails: sign-up confirmation, email verification, password reset, magic sign-in link, two-factor codes.
  • Commerce emails: order confirmation, receipt, invoice, shipping and delivery updates, refund confirmation.
  • Service emails: security alerts, changes to terms, billing failures, usage warnings, a reply notification in your app.

The test is purpose, not format. A receipt can be beautifully designed and still be transactional. What changes it is content: once a receipt carries a large promotional block ("20% off your next order, today only"), the primary purpose starts to blur, and regulators look at the primary purpose.

What counts as marketing email

Marketing email, sometimes called commercial or promotional email, is anything whose main job is to advertise or promote a product, service or cause. Newsletters, product announcements, offers, re-engagement campaigns and "we miss you" sequences all sit here, even when they are sent automatically by a trigger.

That last point catches people out. An abandoned-cart reminder is triggered by user behaviour, but its purpose is to sell, so it is marketing. Automation describes how a message is sent, not what kind of message it is.

This is a plain-language overview, not legal advice. Rules differ by country and change over time, so check with someone qualified for your situation.

United States: CAN-SPAM

The CAN-SPAM Act applies to commercial messages. It doesn't require prior consent, but it does require that commercial email:

  • uses accurate From, To and routing information;
  • has a subject line that isn't deceptive;
  • identifies itself as an advertisement where that applies;
  • includes a valid physical postal address for the sender;
  • offers a clear way to opt out, and honours opt-outs promptly (the FTC sets a limit of 10 business days).

Transactional or relationship messages are largely exempt, though they still must not use false or misleading header information. The FTC decides which category a message falls into by its primary purpose.

EU and UK: GDPR and ePrivacy rules

In the EU, the ePrivacy rules (implemented nationally) and the GDPR work together. In the UK, the equivalent is PECR alongside the UK GDPR. In broad terms:

  • Marketing email to individuals generally needs prior consent, freely given and specific, which you should be able to prove.
  • There is a narrow "soft opt-in" for existing customers: you can market similar products or services to people who bought from you, provided you gave them a chance to opt out when you collected their address and in every message since.
  • Transactional email doesn't need marketing consent, because you send it to perform a contract or meet an obligation. You still need a lawful basis for processing the address, and you shouldn't slip promotions into it.

In practice this means you need to store a consent status for each contact and respect it at send time. Rampsend profiles carry an email_consent field for exactly this, and segments can filter on whether someone can receive email marketing.

TransactionalMarketing
Triggered byAn action or relationship the recipient startedYour decision to promote something
Consent (EU/UK)Not marketing consent; sent to perform a serviceUsually prior consent, or soft opt-in for customers
Unsubscribe linkNot required for genuinely transactional mailRequired, and one-click for bulk senders to Gmail and Yahoo
Recipient expectationWants it now; often waiting for itTolerates it if it's relevant and not too frequent

Deliverability differences

Mailbox providers such as Gmail, Yahoo and Microsoft don't read a "transactional" label in your headers and wave the message through. They judge each message by the reputation of the domain and IP that sent it and by how recipients react. That reaction is where the two types diverge sharply.

Transactional mail usually earns excellent engagement. People open password resets within seconds, almost nobody reports a receipt as spam, and the recipient list is fresh because every address belongs to someone who just used your product.

Marketing mail is more fragile. Lists age, people forget they subscribed, and a too-frequent schedule pushes some of them to the spam button. Complaint rates that are normal for a newsletter would be alarming for receipts. The Gmail and Yahoo sender requirements set a ceiling of 0.3% spam complaints for bulk senders, and the practical target is far lower. Our guide to bounce and complaint rates covers how to measure them.

Bulk sender rules also treat the two types differently. Gmail and Yahoo ask bulk senders to support one-click unsubscribe (RFC 8058) on marketing and subscribed messages and to process requests within two days. Genuinely transactional messages are exempt from the one-click requirement. On Rampsend you add the headers with one flag, unsubscribe_header: true, on any send that isn't strictly transactional.

Why separate streams matter

If both types share one domain, one reputation and one queue, a bad campaign hurts the messages that matter most. Picture a newsletter sent to an old segment: complaints rise, the provider starts filtering your domain, and the next morning your password resets land in spam too. Customers can't log in, support tickets pile up, and the cause is three steps removed from anything your developers changed.

Separation reduces that blast radius in a few ways.

Separate sending subdomains

A common pattern is to send transactional mail from one subdomain and marketing from another, for example mail.acme.com for account and order email and news.acme.com for campaigns. Providers build reputation at the domain level and also consider the organisational domain, so subdomains don't fully insulate you, but they do give each stream its own track record and make problems easier to diagnose. Each subdomain needs its own authentication; see SPF, DKIM and DMARC setup.

Separate From addresses and content

Use distinct From addresses (receipts@ versus news@) so recipients learn which messages to expect from which sender, and so a filter rule someone creates for your newsletter doesn't catch their invoices. Keep receipts free of heavy promotion. A small footer link is fine; a sales banner changes what the message is.

Separate tracking choices

Link tracking rewrites URLs through a redirect. That is useful for campaigns and pointless, or worse, for a password reset or sign-in link, where a rewritten URL can confuse users and some security tools. On Rampsend, track_clicks: false leaves links untouched and track_opens: false skips the open pixel, per message.

Running both from one account

Separating streams doesn't mean running two tools. Two tools usually create the worst gap of all: two suppression lists that don't talk to each other. Someone who complained about your newsletter in one system is still a valid recipient in the other, and the next promotional email sent from the "transactional" tool lands on a person who already said no.

What you want is shared state with separate streams:

  • One suppression list, so a hard bounce or complaint in either stream protects the other.
  • One set of verified domains, with a subdomain per stream.
  • One contact record per person, carrying their marketing consent.
  • Separate tags or labels, so you can report on each stream on its own.

Rampsend is built this way. The same API sends both kinds; you tag each message (for example tags: { "stream": "receipts" }) and choose its From address, tracking and unsubscribe headers. Hard bounces, complaints and unsubscribes are suppressed automatically across the workspace, and suppressed recipients are skipped and not charged. If bounce or complaint rates spike, sending pauses itself before the damage spreads. See how a suppression list works for the detail.

Plans follow the same idea. You can size a plan by contacts if you mostly send campaigns or by emails a month if you mostly send transactional mail, and either way one account covers both. Contacts or emails: how to choose an email plan walks through the choice, and pricing has the details.

A quick checklist

Before you send your next message, ask:

  1. What is its primary purpose: to serve the recipient or to promote something?
  2. If it's marketing, does this person have the consent your jurisdiction requires, and does the message carry an unsubscribe link and one-click headers?
  3. If it's transactional, is it free of promotional content that could change its category?
  4. Is it going out from the right subdomain and From address for its stream?
  5. Are link tracking and open tracking appropriate for its content?
  6. Does every stream share one suppression list?

If you build with an AI assistant, the same rules apply to the email it sends; sending email from an AI agent covers that setup, and the API reference lists every send option mentioned here.

Frequently asked questions

Frequently asked questions

Is a welcome email transactional or marketing?

A plain account confirmation or verification email is transactional. A welcome series that pitches upgrades, features or offers is marketing, because its primary purpose is to promote.

Do transactional emails need an unsubscribe link?

Genuinely transactional messages generally don't, and Gmail and Yahoo exempt them from the one-click unsubscribe requirement. Add one as soon as a message carries promotional content. On Rampsend, unsubscribe_header: true adds RFC 8058 one-click headers.

Can I add a promotion to a receipt?

A small, secondary mention is common, but if the promotion becomes the main point the message can be treated as marketing, with all the consent and opt-out rules that brings. Keep receipts focused on the transaction.

Should transactional and marketing email use different domains?

Using a separate subdomain for each stream, such as mail. for transactional and news. for marketing, gives each its own track record and limits the damage a weak campaign can do. Authenticate each one with SPF, DKIM and DMARC.

Can I send both kinds from one Rampsend account?

Yes. The same API and domains handle both, and one suppression list protects both streams. You can size your plan by contacts or by emails a month; see pricing.

Guides · 6 November 2026 · 6 min read

How an email suppression list works

What goes on an email suppression list, how to handle soft bounces, global vs account lists, and why sending to suppressed addresses hurts deliverability.