What Is a Transactional Email? (+ Examples)
A transactional email is a one-to-one message triggered by something a specific person did — a purchase, a signup, a password reset — and sent automatically to that individual. It carries information they are expecting, not a promotion, which is why it is exempt from marketing consent rules and why it must be delivered fast and reliably.
Transactional vs. marketing email: the real difference
The line is not about the software you use or whether the email looks designed. It is about who initiated it and what it contains. A marketing email goes to a segment of people on a schedule you choose, and it exists to sell. A transactional email goes to one person at the moment they triggered it, and it exists to complete something they started.
| Attribute | Transactional | Marketing |
|---|---|---|
| Trigger | A user action or account event | Your campaign calendar or a segment rule |
| Audience | One recipient | A list or segment |
| Consent required | No opt-in needed (it is expected) | Explicit opt-in in most jurisdictions |
| Unsubscribe link | Not required, and usually inappropriate | Required |
| Typical open rate | Very high — often 40–60%+ | Roughly 20–35% for a healthy list |
| Latency expectation | Seconds | Minutes to hours is fine |
| Usual send path | API or SMTP relay from your app | Campaign builder |
16 transactional email examples
If you are auditing your product, this is the list to check yourself against. Most teams are missing four or five of these.
- Account creation confirmation — welcome plus the one action you want them to take first.
- Email address verification — the click that proves the mailbox exists.
- Password reset — the highest-urgency email you send; it must arrive in under a minute.
- Magic link / one-time code — same urgency, even less tolerance for delay.
- Order confirmation — itemized, with totals, taxes, and a support path.
- Payment receipt — often a separate email from the order confirmation, and often needed for expense reports.
- Shipping notification with tracking — the single most-forwarded transactional email in ecommerce.
- Delivery confirmation — a natural moment to ask for a review.
- Failed payment / card expiring — dunning emails are transactional and are pure revenue retention.
- Subscription renewal notice — legally required in some regions for auto-renewals.
- Refund or cancellation confirmation — skipping this generates support tickets.
- Appointment or booking confirmation and reminder.
- Invitation to join a workspace or team.
- Security alert — new device sign-in, password changed, MFA enabled.
- Export or report ready for download.
- Form or support ticket acknowledgement with a reference number.
Why transactional email is technically different
Transactional mail is generated by your application, so it leaves through a different door than your campaigns. Two common paths:
- SMTP relay. Your app connects to a hosted SMTP server with credentials and hands off the message. This is the fastest route to production because almost every framework and CMS already speaks SMTP — you change four config values and you are live. Our SMTP relay setup guide walks through the exact host, port, and authentication settings.
- HTTP API. You POST a JSON payload with recipient, template ID, and variables. Slightly more work to integrate, but you get structured responses, per-message IDs, and easier retry logic.
Whichever you choose, the key architectural decision is the same: never send transactional mail from the same sending reputation as your bulk marketing. If a promotional blast trips a spam filter, you do not want password resets caught in the blast radius. Separate subdomains — something like mail.yourdomain.com for campaigns and notify.yourdomain.com for app mail — keep the two reputations independent.
Ports and configuration you will actually need
| Port | Encryption | When to use it |
|---|---|---|
| 587 | STARTTLS | The default modern choice for authenticated submission |
| 465 | Implicit TLS/SSL | Widely supported; use if 587 is blocked by your host |
| 2525 | STARTTLS | Fallback when a cloud provider blocks 587 and 465 |
| 25 | Usually unencrypted | Server-to-server relay only — blocked on most app hosts |
Alongside the port, authentication records need to be in place before your first send: SPF to authorize the sending host, DKIM to sign the message, and DMARC to tell receivers what to do when the first two fail. IGSendMail configures SPF, DKIM, and DMARC automatically when you add a domain, which removes the most common source of transactional email landing in spam.
Writing transactional emails that do their job
These emails are read closely, often within seconds, frequently on a phone, and sometimes in a hurry. Write accordingly.
- Put the payload above the fold. The tracking number, the reset button, the six-digit code — before any branding, before any nav bar.
- One primary action. A password reset email with a newsletter promo in it is a password reset email that fails.
- Write a subject line that is a statement of fact. Your order #4821 shipped beats Great news from us! every time.
- Include an expiry. If a link dies in 30 minutes, say so in the body, not just in the fine print.
- Give a human exit. A reply-to address that a person monitors, or a direct support link.
- Make plain text real. Some recipients and many security scanners read only the text part. If your text alternative is a stub, your email looks suspicious.
The rules on promotion inside transactional mail
This is where teams get themselves in trouble. Under CAN-SPAM, a message is transactional based on its primary purpose. Add enough promotional content and the email is reclassified as commercial, which means it now needs an unsubscribe link and a physical address. Under GDPR the analysis differs but the instinct is the same: the recipient consented to service messages, not to marketing.
A practical rule that keeps you safe and keeps the email effective: the transactional content occupies the top two-thirds and any related suggestion sits below it, is clearly secondary, and relates to what they just did. A shipping email that recommends care instructions for the item shipped is fine. A shipping email that leads with a 40%-off sitewide banner is a marketing email wearing a costume. This is general guidance, not legal advice — check with counsel for your jurisdiction and industry.
Monitoring: what to watch after you ship
- Delivery latency. Track time from trigger to accepted-by-receiver. Anything over 60 seconds for auth emails will generate tickets.
- Hard bounce rate. Transactional bounces mean a bad address entered a paid or activated account — that is a signup-flow bug worth fixing at the source.
- Spam complaints. Complaints on transactional mail are rare and are a red flag that promotional content has crept in.
- Per-template failure rate. One broken template can silently kill a whole flow; alert on volume dropping, not just on errors.
If any of these start drifting, work through the fundamentals in our guide to improving email deliverability before you start changing copy — authentication and reputation issues explain most sudden drops.
Frequently asked questions
What is an example of a transactional email?
A password reset email is the clearest example: one person requested it, it goes only to them, and it contains information they are waiting for. Order confirmations, shipping notifications, receipts, and account security alerts are equally common examples.
Do transactional emails need an unsubscribe link?
No. Because the recipient triggered the message and it is not promotional, an unsubscribe link is not required and would be confusing — you cannot opt out of receiving your own receipts. The moment you add substantial marketing content, though, the email may be reclassified and unsubscribe rules apply.
Can I send transactional emails through a marketing platform?
Yes, provided the platform offers an SMTP relay or API endpoint for app-triggered mail. Use a separate sending subdomain so your campaign reputation and your application reputation stay independent.
Why are my transactional emails going to spam?
The usual causes are missing or misconfigured SPF, DKIM, and DMARC records, sending from a shared reputation damaged by marketing volume, or a thin plain-text alternative. Fix authentication first, then separate the sending domain.
What is the difference between transactional and triggered marketing email?
Both are automated, but a triggered marketing email — an abandoned cart reminder, for instance — exists to persuade and requires marketing consent. A transactional email exists to deliver information the recipient already expects.
Need reliable app mail without babysitting a mail server? Get started with IGSendMail — SMTP relay, automatic SPF/DKIM/DMARC, and 99% inbox deliverability from $19/mo.