True story: an e-commerce client sends order confirmations and newsletters from the same address. One day someone marks the newsletter as spam. Gmail lowers the IP reputation. Suddenly order confirmations start landing in spam. Customers call: “I didn’t get my confirmation!” Chaos.

This isn’t a theoretical scenario. I’ve seen it happen several times. And every time, the cause was the same — mixing transactional emails with marketing ones.

First — what are we even talking about?

A transactional email is one the user expects because they just did something. Registered? They get a confirmation. Bought something? They get an invoice. Forgot their password? They get a reset link.

A marketing email is one you want to send, but the user doesn’t necessarily expect it. Newsletter, promotions, “Hey, we haven’t seen you in a while”…

Sounds simple? In theory, yes. In practice… there are a few traps.

The law doesn’t joke (especially GDPR)

This part is clear:

Transactional emails you send because you must — the user entered into a contract with you and has the right to get a confirmation. You don’t need separate consent. The user can’t “unsubscribe” from order confirmations.

Marketing emails you send because you want to — the user must agree to this. Consciously. Preferably double opt-in. And every email must have an unsubscribe link.

The trap everyone falls into

You have an order confirmation. You think: “I’ll add a promo banner, after all the customer will open this email anyway.”

Stop. At this moment, your transactional email became a marketing email. And you just sent marketing to someone who didn’t give consent.

Penalty? Up to 4% of global revenue. Plus reputation loss, because customers will start reporting spam.

Why technical separation is crucial

Imagine a queue at the post office. You have an urgent letter (transaction confirmation) and 1,000 flyers (newsletter).

If you throw everything into one window, your urgent letter will wait behind the flyers. And if someone says the flyers are spam — the whole queue gets blocked, including the urgent letter.

What does this mean in practice?

Aspect Transactional Marketing
Speed Immediate (seconds) Can wait (minutes, hours)
Open rate 60-80% 15-25%
Spam tolerance ~0% <0.1%
Priority Critical Normal

One spam complaint in a marketing campaign? It happens. One in transactional emails? You have a problem.

How to separate them?

Simplest: Use separate subdomains.

mail.example.com → transactional emails
news.example.com → newsletter and promotions

Each subdomain builds its own reputation. Problems with one don’t affect the other.

Even better: Use separate providers.

Transactional emails through MailingAPI (optimized for speed and deliverability), marketing through something else. Full separation.

Gray areas — because life isn’t black and white

Abandoned cart

First email: “Hey, you left something in your cart” — you could argue it’s a reminder, so transactional.

Second email with a discount code: That’s 100% marketing. Requires consent.

My advice? Treat all abandoned cart emails as marketing. Safer.

Product recommendations

“Others also bought…” after purchase — marketing. “Complete the set” in order confirmation — gray area, but you’re taking a risk.

Rule: if you have doubts, it’s marketing.

NPS survey

24h after order: “How do you rate your shopping?” — could be transactional.

Monthly to everyone: “Fill out a survey” — marketing.

Quick test: is it a transactional email?

Ask yourself three questions:

  1. Did the user just do something? (No → marketing)
  2. Are they expecting this email? (No → marketing)
  3. Is there anything promotional in it? (Yes → at least partially marketing)

If you answered “yes, yes, no” — congratulations, it’s a transactional email.

How we do it at MailingAPI

MailingAPI was built with transactional emails in mind. That means:

  • Priority queue — Your order confirmation doesn’t wait behind someone’s newsletter
  • Delivery SLA — 99% of emails in less than 10 seconds
  • Automatic retry — if the recipient’s server doesn’t respond, we try again
  • Infrastructure-level separation — transactional and marketing traffic on separate pools

We support marketing too, but honestly? If you mainly send newsletters — there are better tools. We’re best at what’s critical: confirmations, alerts, password resets.

Checklist before sending

For transactional emails:

  • [ ] It’s a response to a user action
  • [ ] The user expects this email
  • [ ] Zero promotional content
  • [ ] Sending from a separate subdomain

For marketing emails:

  • [ ] You have documented consent
  • [ ] There’s an unsubscribe link (and it works!)
  • [ ] Separate IP/subdomain from transactional
  • [ ] Frequency matches expectations

Final thoughts

Separating transactional from marketing emails isn’t pedantry. It’s protecting your business. One bad day in marketing shouldn’t mean your customers stop receiving order confirmations.

Want to see how it works in practice? Create a free account and test it yourself.