email

Transactional vs Marketing Email: How Regulated Senders Separate the Streams

By Art Kukharenko · Published · Updated

Browse email resources

Transactional email facilitates or confirms something the recipient already agreed to; marketing email promotes. Regulated senders keep them on separate subdomains, sending IPs and authentication, so a marketing complaint spike cannot delay a statement, security alert or regulatory notice. Under US CAN-SPAM a mixed message is judged by its primary purpose; under UK ICO guidance, any marketing element can make the whole message direct marketing.

Who this is for: heads of messaging, security engineers and compliance officers at banks, insurers, healthcare organisations and other senders whose notices must arrive. Part of the email and activation infrastructure hub; context in MailOps in 2026.

CAN-SPAM (United States). A commercial message is one whose primary purpose is the commercial advertisement or promotion of a commercial product or service. A transactional or relationship message has as its primary purpose one of five things: to facilitate, complete or confirm a transaction the recipient previously agreed to; to give warranty, recall, safety or security information; to notify a change in terms, features or standing, or give periodic account statements; to give employment-related information; or to deliver goods or services the recipient is entitled to 1. The FTC says such messages are largely exempt from the Act's requirements, though their routing information must stay truthful 2.

The primary-purpose test for mixed messages. Under 16 CFR 316.3, a message mixing commercial and transactional content is treated as commercial if either a recipient reasonably reading the subject line would likely conclude it is commercial, or the transactional content does not appear, in whole or in substantial part, at the beginning of the body. For a mix of commercial and other non-transactional content, the tests are the subject line and what a reasonable recipient would conclude from the body, including placement, proportion and how colour, graphics and type size highlight the commercial content 3.

UK and EU. The UK ICO treats administrative service messages as outside direct marketing, but says that if a service message contains direct-marketing elements, "even if that is not the main purpose", it becomes direct marketing; general branding or logos do not count, and a neutral tone does not avoid the label 4. The EU ePrivacy Directive's consent rule applies to direct marketing by email 5. The safe rule, given the ICO's position, is no promotion at all inside service mail.

Mailbox providers. Gmail and Yahoo require one-click unsubscribe for marketing and subscribed messages and exclude transactional mail 67. Postmark classifies transactional mail as triggered by what users do and broadcast mail as sent by you to many 8.

Why regulated senders separate the streams

  1. Reputation isolation. On a shared IP, the reputation of all senders is affected 9. Amazon SES documents separate dedicated IP pools so that a marketing campaign generating many complaints does not affect transactional delivery 10. Postmark says separating reputation follows best practice recommended by inbox providers such as Gmail, with separate IPs and From domains 8. Apple asks bulk senders for consistent IPs and domains and separate marketing and transactional streams 11.
  2. Regulatory notices must land. If law requires a written disclosure and you deliver it electronically, the consumer must have affirmatively consented to electronic delivery and not withdrawn it (US E-SIGN Act, 15 U.S.C. 7001(c)) 12. Delivery of those notices is then a compliance control, not a marketing metric. They should not share reputation with promotions.
  3. Different legal bases and consent. Service messages rest on contract or legal obligation (GDPR Art. 6(1)(b), (c)); marketing on consent or, where allowed, legitimate interests (Art. 6(1)(a), (f)) 13. Withdrawing marketing consent must not stop a statement.
  4. Audit. Marketing streams need consent evidence; service streams need delivery evidence. Separate logs, retention and access make both defensible.
  5. A subdomain does not buy you out of bulk rules. Gmail counts messages from the same primary domain toward its 5,000 threshold, and bulk status is permanent 6. Splitting subdomains isolates reputation, not obligations.

Domain, subdomain and IP strategy

Scroll horizontally to compare all columns ↔

Comparison — source references are listed below
OptionProsConsFit
Same domain and IPs for everythingSimpleOne complaint spike hits every messageAvoid for regulated senders
Separate subdomains, shared IPsDomain-level reputation separates: Postmaster Tools' Domain reputation covers the exact domain used for DKIM and SPF 14IP reputation is still shared 9Small volumes without dedicated IPs
Separate subdomains plus separate IP poolsIsolates domain and IP reputation; supports separate warm-up and throttlingMore DNS, monitoring and warm-up workDefault for regulated senders; SES, Postmark and self-run MTAs support pools 810
Separate organisational domainsIsolates even bulk-threshold countingBrand and lookalike-domain risk; more to defendHigh-risk or aggressive marketing programmes; judgement call
Marketing on a third-party platform, transactional on own infrastructure (or the reverse)Matches control to riskTwo vendors to governCommon in banks and payers; see Self-Hosted Email Marketing Platforms Compared

Operational notes:

  • Warm each pool gradually; Gmail asks senders to increase volume gradually and keep one From address per category 9.
  • Run transactional traffic on its own queue so a marketing blast cannot delay a one-time passcode.

Authentication per stream

Scroll horizontally to compare all columns ↔

Comparison — source references are listed below
ItemTransactional streamMarketing stream
From and return-path domainDedicated subdomain, e.g. alertsDedicated subdomain, e.g. news
SPFOwn record; subdomains do not inherit the parent's 15Own record
DKIMOwn selector and key; sign with the stream's domainOwn selector and key, rotated independently
DMARCEnforcement (quarantine or reject) once all senders are known; BIMI also needs enforcement on the organisational domain and subdomains 16Start at p=none for new senders, then enforce
Unsubscribe headerNot required by Gmail or Yahoo 67RFC 8058 one-click required
Feedback-ID headerYes, stream-specific, so Postmaster complaints are attributable 17Yes, per campaign
MonitoringPostmaster Tools per domain; delivery errors firstSpam rate below 0.10 percent target 6

The details of each mechanism are in Email Authentication in 2026.

Decision table: which stream does this message belong to?

Scroll horizontally to compare all columns ↔

Comparison — source references are listed below
MessageStreamBasis to recordUnsubscribe linkNotes
Password reset, one-time code, login alertTransactionalContract or legal obligationNoNo promotional blocks 14
Order, payment or transfer confirmationTransactionalContractNoCAN-SPAM transaction category 1
Periodic statement, balance informationTransactionalContract or legal obligationNoAccount statement category 1
Change to terms, rates or featuresTransactionalContract or legal obligationNoDo not append offers 4
Legally required disclosure delivered electronicallyTransactionalLegal obligation plus recorded e-delivery consentNoWithdrawal switches to paper 12
Wellness or product promotion by a health plan or providerMarketingConsent or authorisation where requiredYesCheck HIPAA marketing rules, 45 CFR 164.501 and 164.508(a)(3); see HIPAA Marketing Rules
Receipt with a "you may also like" blockMarketing or mixedConsent for the promotional partYes if marketingUK (ICO): whole message is direct marketing 4; US: primary purpose 3
Survey or review request after a purchaseTreat as marketing unless counsel decides otherwiseLegitimate interest or consentYesConservative practice, not a legal rule
Newsletter, offer, win-backMarketingConsent, soft opt-in or legitimate interest by jurisdictionYesOne-click header required at Gmail and Yahoo 67

Governance: making separation stick

  • Tag every template with a stream and block promotional components in service templates with a lint step in the release pipeline.
  • Use separate API keys, queues and dashboards per stream so an outage or runaway campaign cannot cross over.
  • Apply suppression by purpose: a marketing opt-out never blocks service mail, while a hard bounce or spam complaint blocks the address. See Consent Withdrawal Across Channels.
  • Review placement per stream, not blended; see Inbox Placement vs Delivery Rate.
  • Treat adding promotion to a service template as a change needing compliance review.

Checklist

  • List every message type and assign it a stream using the decision table.
  • Remove promotional content from service and regulatory templates.
  • Put each stream on its own subdomain, and its own IP pool where volume allows.
  • Publish SPF, DKIM and DMARC per subdomain; give each its own selector.
  • Add RFC 8058 headers to marketing only; add stream-specific Feedback-ID headers to both.
  • Run transactional mail on a separate, prioritised queue.
  • Define suppression semantics per purpose and test them.
  • Register each domain in Postmaster Tools and Microsoft SNDS; alert per stream.
  • Record the legal basis and delivery evidence kept for each stream, and review the stream map twice a year.

If you need transactional and marketing streams, consent state and audit trail under your own control, start with the deployment qualification. Back to the email hub.

Frequently asked questions

What is the difference between transactional and marketing email?

Transactional email facilitates or confirms something the recipient already agreed to, such as a receipt, password reset, statement or security notice. Marketing email has the primary purpose of advertising or promoting a product or service. The distinction drives which legal rules apply, whether unsubscribe is required and how providers treat the mail.

Do I need separate domains for transactional and marketing email?

No law requires it, but providers recommend separation: Apple asks bulk senders to separate the streams, SES documents separate IP pools, and Postmark uses separate IPs and From domains. For regulated senders the practical answer is separate subdomains, and separate IP pools where volume allows, each with its own authentication and monitoring.

Can I add promotions to a transactional email?

In the US, adding promotion risks turning the message into a commercial email under the primary-purpose test, which looks at the subject line and whether transactional content comes first. Under UK ICO guidance, any marketing element can make the whole message direct marketing. The safe approach is no promotional content in service mail.

Do transactional emails need an unsubscribe link?

CAN-SPAM largely exempts transactional or relationship messages from its opt-out requirement, and Gmail and Yahoo require one-click unsubscribe only for marketing and subscribed mail. A purely service message therefore does not need one, but a message that contains marketing does, and UK guidance may treat it as direct marketing.

Does a separate subdomain avoid Gmail's 5,000-message bulk sender rule?

No. Gmail counts messages from the same primary domain toward the 5,000 threshold, and a sender that reaches it is permanently considered a bulk sender. Subdomains separate reputation at the domain level, but obligations such as DMARC, alignment and one-click unsubscribe for marketing still apply.

Sources

  1. 15 U.S.C. 7702, definitions (commercial and transactional or relationship messages) Open source
  2. FTC, CAN-SPAM Act: A Compliance Guide for Business Open source
  3. 16 CFR 316.3, Primary purpose Open source
  4. ICO, Identify direct marketing — ; Key concepts Open source · Additional source
  5. Directive 2002/58/EC (ePrivacy), Article 13 Open source
  6. Google, Email sender guidelines FAQ Open source
  7. Yahoo, Sender FAQs and best practices Open source · Additional source
  8. Postmark, Message Streams Open source
  9. Google, Email sender guidelines Open source
  10. AWS, Dedicated IP pools in Amazon SES Open source
  11. Apple, iCloud Mail bulk sender requirements Open source
  12. 15 U.S.C. 7001, E-SIGN consumer disclosures Open source
  13. GDPR Article 6 Open source
  14. Google, Postmaster Tools dashboards Open source
  15. Microsoft Learn, How email authentication works in Microsoft 365 Open source
  16. BIMI Group, Implementation guide Open source
  17. Google, Sender requirements and Postmaster Tools FAQ Open source

Put this evaluation into practice.

Assess your deployment requirements

This article is general information, not legal advice.

Further reading

Published: · Updated:

Publication date recorded for the approved release. Editorial updates do not establish legal approval or a customer result.

Need help?

Ask the PrivyCDP Assistant