Skip to content

← All articles

Transactional or marketing email: where is the line?

The distinction seems obvious: the receipt is transactional, the newsletter is marketing. In a real application, the boundary is blurrier. A weekly digest, a cart reminder, a new-feature alert: which side do they fall on? The answer changes what the law requires, how email providers treat your messages and which tools you may use.

This article is general information, not legal advice. For borderline cases, the final decision rests with your compliance officer or a lawyer.

A definition that helps you decide

An email is transactional when the person expects it because they just did something or because they have an account with you, and it gives them information they need to have: confirmation, receipt, password reset, login code, security alert, notice about their account or subscription.

An email is marketing when its purpose is to promote something: a product, an offer, an event, a newsletter, a reminder to buy.

A simple test: if the person did not receive it, what would they be missing? Without the login code, they cannot sign in. Without the newsletter, they miss nothing essential.

Examples, on each side

Email Where to put it
Password reset link, verification code Transactional
Order confirmation, receipt, invoice Transactional, as long as it contains no promotion
Security alert (sign-in from a new device) Transactional
Subscription renewal or payment failure notice Transactional (factual information about an account or subscription)
Notification of an action in the app ("Jean commented") Transactional if the person asked for these notifications
Weekly activity digest Gray area: depends on the content and on what the person asked for
"You forgot something in your cart" Marketing: a solicitation, not the confirmation of a transaction
Welcome offer after a sign-up Marketing
Satisfaction survey sent after a purchase Gray area: often treated as marketing
Newsletter, promotion, product announcement Marketing

The right-hand column is not a legal verdict: it is a starting point. What decides is the actual content of the message, not the label you give it.

The trap of the hybrid message

The most frequent case is not an email that is clearly marketing: it is a transactional email to which a promotion has been added. A receipt with a "Our new products" banner, a sign-up confirmation that offers a discount code, a shipping notice followed by suggested products.

Canada's anti-spam legislation looks at the purpose of the message, and the definition includes "one of its purposes". A message with one commercial purpose more than a simple confirmation no longer benefits from the exception that dispenses with consent: see CASL and transactional email. And email providers also judge the content: a receipt that looks like a promotion is filed as one.

The safest rule: keep your transactional emails purely transactional. If you want to promote something, do it in a separate message, sent to people who have consented.

Why it matters

The law. The consent and unsubscribe requirements are not the same depending on the type of message (see the article above).

Reputation. People who receive marketing they did not expect click "spam". Those complaints are counted against the domain and the sending addresses. If your promotions and your login codes leave from the same domain, complaints about the former can hurt the delivery of the latter. Gmail, for example, asks senders to keep the reported spam rate below 0.3%.

Tools. A transactional sending service is not a newsletter tool. Duva's terms prohibit sending newsletters, promotions or bulk messages without prior written agreement, because those uses have a very different risk profile and share the reputation of the sending addresses. For a newsletter, use a tool designed for it, with subscription and unsubscribe management.

Separating the streams

If your business sends both types of email, separate them:

  1. Different domains or subdomains. For example, notifications.example.ca for transactional and newsletter.example.ca for marketing. Each has its own authentication (SPF, DKIM, DMARC) and its own reputation: see SPF, DKIM and DMARC: setting up a sending domain.
  2. Different tools, or at least separate streams in the same tool.
  3. Different sender addresses, which the person recognizes: "notifications@" is not "promotions@".
  4. Separate consent. Creating an account is not consenting to receive promotions: ask for an explicit checkbox, not pre-checked, and keep proof (date, source, wording). This consent to receive commercial messages (CASL) comes on top of the privacy rules (Law 25, PIPEDA) on what you do with the addresses: see Law 25 and email.

"Subscription" messages

Between the two, there are messages the person has subscribed to: weekly digest, price alerts, community notifications. They are neither receipts nor promotions. A few good practices:

  • Easy unsubscribing, visible in the message.
  • The List-Unsubscribe and List-Unsubscribe-Post headers, which let Gmail and other clients display a one-click unsubscribe button. Gmail requires them for marketing and subscribed messages from senders of more than 5,000 messages per day to Gmail. Duva's API accepts both headers.
  • Content faithful to what the person asked for. An activity digest that gradually turns into a promotion is exactly the kind of drift that produces complaints.

A checklist

For each email your application sends:

  1. Write down its purpose in one sentence. If there is more than one, it is a hybrid message.
  2. Ask yourself what the person would be missing if they did not receive it.
  3. Remove any promotion from a transactional email.
  4. Put each email in a stream: transactional, subscription, marketing. One stream, one domain, one sender.
  5. Check consent for anything that is not strictly transactional.
  6. Watch complaints per stream. A rise in one stream is the signal that it is drifting toward something else.

Sources