What Is Transactional Email? Definition and Examples (2026)

A transactional email is an automated message an application sends to one person because of something that person did, or something that happened to their account. Password resets, one-time login codes, order receipts, and shipping updates are all transactional. The recipient expects it (often within seconds) and needs the information in it. It isn't there to promote anything. US law draws the same line: under CAN-SPAM, a message whose primary purpose is to complete a transaction or update an existing relationship is exempt from most of the rules that apply to marketing email.

What is a transactional email?

A transactional email has three traits:

• One recipient. A receipt is for the person who just paid. A login code is for the person trying to sign in.
• Triggered by an action or event. Someone signs up, resets a password, places an order, or their card fails. The send is a reaction, not a scheduled campaign.
• Expected, often urgently. People sit and wait for these. A verification code that arrives two minutes late is often useless, because the person has already given up or asked for another one.

The US Federal Trade Commission's CAN-SPAM guide⁠ gives the legal version. "Transactional or relationship" content is content that:

1. Facilitates, completes, or confirms a commercial transaction the recipient already agreed to
2. Gives warranty, recall, safety, or security information about a product or service the recipient bought or uses
3. Notifies the recipient of a change in the terms or features of an account, subscription, or membership
4. Provides information about an employment relationship or employee benefits
5. Delivers goods or services the recipient already agreed to receive

If a message's primary purpose fits one of those, it's transactional in the legal sense.

Transactional email examples

Here are the ones most products send, grouped by what triggers them.

Authentication email is the most time-sensitive group. If a magic link takes 90 seconds, the user is locked out during their first 90 seconds with your product, which is a bad first impression and a common source of support tickets.

All four groups share the same shape: an event happened, one person needs to know, and they get an email about it.

How is transactional email different from marketing email?

Transactional email serves something the recipient already started, like an order or a sign-in. Marketing email promotes something new, and usually goes to a list when you decide to reach it. That difference changes almost everything about how each one is sent and regulated.

The consent line is where teams get into trouble. A receipt doesn't need a marketing opt-in. But staple a promotion onto it, like "check out our new plan" under a password reset, and part of that email is now commercial. The FTC's test for mixed messages is strict: if the subject line suggests an ad, or the transactional content does not appear mainly at the beginning of the message, the whole email counts as commercial. Keep the two jobs in separate messages.

There's also a deliverability reason to keep them apart. Marketing mail draws unsubscribes and spam complaints. Transactional mail usually draws far fewer, because people expect it. If both share one sending reputation, a bad campaign can pull your password resets into spam.

For the full breakdown, including the EU rules and how to split sending streams, see transactional vs marketing email⁠.

Transactional email vs lifecycle and activation email

There's a third category that sits between the two, and it's easy to overlook: lifecycle email. These are messages triggered by what a user did, or didn't do, with the goal of moving them to the point where the product becomes valuable to them. That point is usually called activation, or "first value."

Examples:

• A welcome email that points a new user at the one setup step that matters
• A nudge 24 hours after signup to someone who hasn't created their first project
• A "you're one step away" email when someone connected a data source but never ran a report
• A trial reminder to a user who hasn't tried the feature paid customers use most
• A usage-limit warning that suggests upgrading before they hit the cap

They look transactional: one recipient, triggered by behavior, often sent from the same app events. But a password reset exists to complete something the user asked for. An onboarding nudge exists to change what the user does next. That's why it usually falls outside the FTC categories above, and why you should treat lifecycle email as marketing: include an unsubscribe link, respect opt-outs, and send it on your marketing or lifecycle subdomain, not the one your login codes use.

They're also measured differently:

Transactional email is judged on speed and reliability. Activation email is judged on whether more users reach first value and convert. A product can run flawless transactional mail and still lose signups who never reach first value, because nothing follows up. The welcome email examples⁠ post shows the trigger and exit logic for this kind of message, and the drip campaign guide⁠ covers how to chain them into a sequence that stops when the user reaches the goal. For one email type that tends to move retention most, see how one simple email type can 10x your user retention⁠.

How is transactional email sent?

Your app decides a message should go out, then hands it to something that delivers it. There are four common setups.

A provider's API or SMTP relay

This is what most teams do. You sign up with a sending provider, and your app makes an HTTPS API call, or connects to the provider's SMTP relay, for each message. The provider handles IP reputation, retries on temporary failures, and bounce and delivery data.

An API is usually easier in a modern web app: you send a request and get back a message ID you can log. SMTP is useful when an existing system or framework already speaks it. Resend, Postmark, and SendGrid all offer both.

Here's where those three start, checked in September 2026 on each provider's pricing page:

Pricing compared

Transactional plan: cheapest paid price

Transactional plan: cheapest paid price

Item	Value
Postmark	$15
SendGrid	$19.95
Resend	$20

For a wider comparison, including log retention and cost at 10,000 emails, see best transactional email services⁠. For a developer-focused comparison of the APIs themselves, see best email API providers⁠.

A cloud building block

Amazon Simple Email Service (SES) is the low-cost option for teams on AWS. New SES accounts start on its Essentials plan at $0.16 per 1,000 emails, and any account can switch to à la carte pricing at $0.10 per 1,000. The trade-off is that SES is a building block. It stores templates, retries temporary delivery failures, and reports bounces and complaints, and Essentials adds a deliverability dashboard with 30 days of message search. You still wire those pieces into your app yourself, along with queues and the logic that decides when to send.

Your own mail server

You can run your own SMTP server, but almost nobody should. A new server starts with no reputation, gets blocked easily, and turns deliverability into a job. When people say "we use SMTP" today, they usually mean a provider's SMTP relay.

A platform with templates and workflows

Some tools add a template editor, a dashboard, and workflow logic on top of sending, so non-engineers can edit messages and conditions. You give up some low-level control and save yourself from building that tooling.

Whichever you choose, your app still owns a few things: deciding when a message should send, making sure a retry doesn't send it twice, and storing the provider's message ID so support can trace a "never got my email" ticket.

How do you keep transactional email out of spam?

A well-written email can still land in spam if the technical setup is wrong. For transactional mail, that means locked-out users. Four habits cover most of it.

Authenticate your domain with SPF, DKIM, and DMARC

These DNS records prove to receiving servers that you're allowed to send for your domain. Since February 2024, Gmail requires every sender to personal Gmail accounts to use SPF or DKIM, and senders of about 5,000 or more messages a day (counted across your domain and its subdomains) to use all three plus DMARC alignment. Yahoo has similar rules.

• SPF lists the servers allowed to send mail for your domain.
• DKIM adds a cryptographic signature so the receiver can confirm the message came from you and wasn't altered.
• DMARC tells receivers what to do when neither SPF nor DKIM passes for your From domain, and lets you ask them for reports. Start at p=none, read the reports until you've accounted for every legitimate sender, then tighten to quarantine and reject.

The step people skip is alignment. For DMARC to pass, SPF or DKIM has to pass for a domain that matches the one in the visible From address. By default, a subdomain of the same parent counts as a match, so mail.yourdomain.com aligns with yourdomain.com. If a provider signs DKIM with its own domain and uses its own bounce domain for SPF, neither aligns and DMARC fails. The fix is to verify a custom sending domain with your provider so the DKIM signature carries your domain.

Send transactional mail from its own subdomain

Put transactional mail on one subdomain, such as txn.yourdomain.com, and marketing on another, such as news.yourdomain.com. Marketing mail tends to draw more complaints and unsubscribes. On separate subdomains, a rough campaign is less likely to drag down the reputation your receipts and resets depend on.

Whether each subdomain needs its own SPF and DKIM setup depends on the provider. Amazon SES lets subdomains inherit a verified parent domain, while others may ask you to add txn.yourdomain.com as its own sending domain. DMARC works the same everywhere: a subdomain inherits the parent domain's policy (or its sp tag) unless you publish a DMARC record on the subdomain itself.

Separate streams inside transactional mail

As you grow, split authentication mail from receipts and activity alerts using your provider's message streams, tags, or separate configurations. When something goes wrong, you can see which stream it's in.

Handle bounces and watch speed

Remove addresses that hard-bounce, keep the From name recognizable, and measure time to inbox for your login codes. Slow auth email is a common reason users get locked out.

If transactional mail is landing in spam right now, the email deliverability guide⁠ walks through diagnosis step by step.

Where Dreamlit fits

Dreamlit, the company behind this blog, doesn't sell a sending API. If you need password resets and receipts, pick a provider above.

Dreamlit takes activation email off your plate. Our experts find where users drop off, run the emails that turn signups into paying users, and own the results. You get a weekly report on what moved. It's built for products with 500 or more signups a month.

Transactional email handled? Get a free activation audit to see where new users stall after signup.

References

• FTC: CAN-SPAM Act compliance guide for business⁠
• ICO: How do we comply with the PECR electronic mail marketing rules?⁠
• Google: Email sender guidelines⁠
• Google: Email sender guidelines FAQ⁠
• Yahoo Sender Hub: Best practices⁠
• RFC 7208: SPF⁠
• RFC 6376: DKIM⁠
• RFC 7489: DMARC⁠
• Resend pricing⁠
• Postmark pricing⁠
• SendGrid Email API pricing⁠
• Amazon SES pricing⁠
• Amazon SES: Creating and verifying identities⁠

---

Frequently asked questions

What is a transactional email in simple terms?

A transactional email is an automated message your app sends to one person because that person did something or because something changed on their account. Password resets, login codes, receipts, and shipping updates are all transactional. The person expects it, often within seconds, and it carries information they need rather than a promotion.

What are examples of transactional emails?

Common examples are email verification, password resets, one-time login codes and magic links, new-device security alerts, order confirmations, receipts and invoices, failed-payment notices, shipping and delivery updates, and activity alerts such as a mention, a finished export, or a usage threshold.

What is the difference between transactional and marketing email?

Transactional email is triggered by one person's action or account event and delivers information they need. Marketing email exists to promote something or bring people back, whether it goes to a whole list or to one person after they do something. The difference changes the legal rules, the unsubscribe requirement, and how inbox providers judge each stream.

Do transactional emails need an unsubscribe link?

Under the US CAN-SPAM Act, messages whose primary purpose is transactional or relationship content are exempt from the opt-out and postal-address requirements, though they still cannot use false or misleading routing information. If the subject line suggests an ad, or the transactional part is not mainly at the beginning, the FTC treats it as commercial and the full rules apply.

Is a welcome or onboarding email transactional?

A welcome email that only confirms the account and gives access details can be transactional, and so can a plain notice of the date a trial ends. Onboarding nudges, upgrade prompts, and trial reminders that push a feature or a purchase are triggered by user behavior but exist to change that behavior, so treat them as marketing: include an unsubscribe link and send them on your marketing or lifecycle stream.

How fast should a transactional email arrive?

Within seconds. People wait on screen for login codes and password resets, so anything past a minute reads as broken and they retry or give up. Use a provider built for transactional sending, keep your domain authentication clean, and watch for queue delays.

Should transactional and marketing email use the same domain?

Send them from separate subdomains, for example txn.yourdomain.com and news.yourdomain.com. That helps inbox providers see separate reputation signals, so a marketing campaign that draws complaints is less likely to push password resets and receipts into spam.