Contents

Transactional emails and notifications are messages sent in response to a user action or a system event: sign-up confirmation, a sign-in code, a receipt, an order status, a payment reminder. They must arrive fast and stay out of spam. That takes properly configured SPF, DKIM and DMARC records, a separate domain or stream for marketing campaigns, a sending queue and delivery monitoring.

Here is how such messages differ from campaigns, how to ensure deliverability, how to choose a channel and how to structure a notification system.

How do transactional emails differ from campaigns?

A transactional email goes to one person in response to an event and is expected; a marketing campaign goes to many people, often without immediate interest from recipients. So they have different requirements for speed, consent and sender reputation.

Trait Transactional Marketing
Trigger A user action or event A company decision
Recipient expectation Waiting for it now Not waiting
Speed Seconds Not critical
Marketing consent Usually not required Required
Reputation impact High engagement Risk of spam complaints

Send them separately — from different subdomains or streams — so complaints about campaigns do not drag down delivery of sign-in codes and receipts.

How do you keep emails out of spam?

Deliverability rests on proving you own the domain and on a good sender reputation. Mailbox providers check the domain's technical records and watch complaints, bounces and engagement.

example.com.          TXT  "v=spf1 include:_spf.mailprovider.com -all"
mail._domainkey       TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
_dmarc.example.com.   TXT  "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"

Checklist:

  1. SPF — lists the servers allowed to send mail for your domain.
  2. DKIM — emails are signed with a key that proves authenticity.
  3. DMARC — a policy for emails failing checks and reports on spoofing attempts.
  4. Separate subdomains — for transactional email and campaigns.
  5. Clean lists — non-existent addresses are removed after the first hard bounce.
  6. A recognisable sender and subject — users identify the email at once.

A brass bell on a dark wooden wall Photo: Unsplash

Which channel should a notification use?

Choose the channel by urgency and importance. Urgent and important goes where it will be seen immediately; detailed and documentary goes to email; non-critical stays inside the app.

  • email — receipts, documents, confirmations, detailed digests;
  • push notifications — order statuses, messages, reminders in a mobile app;
  • SMS — verification codes and critical events when no other channel exists; expensive — see bot and spam protection on SMS pumping;
  • messengers — statuses and reminders if the customer connected a bot — see Telegram bots and Mini Apps for business;
  • in-app notifications — anything that does not need immediate attention.

How do you structure notifications in an app?

As events and channels multiply, notifications move into a separate module: business logic announces "an event happened", and the module decides who gets what, through which channel and in what form, respecting user preferences.

  • email and message templates live outside the code and are translated into every language;
  • sending goes through a queue with retries — see job queues;
  • users manage channels and notification types in their settings;
  • important events fall back to another channel if the first fails;
  • similar notifications are combined into a digest so users are not flooded.

How do you monitor delivery?

Monitor delivery through the sending service's statistics and your own metrics: how many emails are delivered, how many bounce or get complaints and how long it takes from event to receipt. A sudden change in these numbers is a reason to investigate immediately.

  • delivered and bounced share by mailbox provider;
  • spam complaints — close to zero for transactional email;
  • time from event to sending — a growing queue shows up immediately;
  • DMARC reports on attempts to send mail in your name;
  • an alert if sign-in codes stop being delivered.

How to set up monitoring: monitoring and logging; on storing addresses and consent: personal data on a website.

In short

  • Transactional emails respond to events and must arrive within seconds.
  • Separate them from marketing campaigns by subdomain or stream.
  • SPF, DKIM and DMARC are the mandatory foundation of deliverability.
  • Choose the channel by urgency: email, push, SMS, messenger, in-app.
  • Send through a queue, respect user preferences and monitor delivery.

FAQ

  • Can emails be sent from your own server?

    Technically yes, but email from a new server with no reputation often lands in spam. A dedicated sending service that manages reputation and provides delivery statistics is more reliable.

  • Is consent required for transactional emails?

    Emails required to fulfil an order or run an account usually need no separate marketing consent. But adding advertising turns them into marketing emails, which require consent and an unsubscribe option.

  • How do you check how an email looks in different clients?

    Use email preview services and send test emails to popular mailbox providers. Email layout differs a lot from ordinary web layout, so build templates from proven components.