Blog
Technical guides on transactional email for developers. Implementation patterns, authentication, and best practices.
Every guide on this site follows the same rules: no invented statistics, pricing claims hedge to the vendor's official page, and every "best for" is scoped to a use case instead of a universal endorsement. Where a topic depends on a vendor's current packaging, the article says so in the text rather than burying the hedge.
The guides are deliberately durable - DNS records, token lifetimes, webhook strategies, suppression policy - because those lessons outlive the vendor of the month. Pick a lane below:
What each category assumes
- Deliverability fundamentals assume you own DNS and can publish records the same day you read about them. If someone else controls DNS, each guide includes a handoff paragraph for exactly that situation.
- Architecture decisions assume the product is in production or about to be; the trade-offs described there only matter once the event stream is real.
- Implementation patterns assume comfort with your language's HTTP client. We avoid framework-specific worship: protocol details survive framework churn.
- Choosing a provider assumes you can pilot - if you cannot, the decision method described in the selection guide covers a time-boxed capture-first alternative for teams under constraint.
Where the blog connects to the rest of the site
Guides deliberately share a spine with the rest of the site: the fixtures and decision criteria used in the checklists appear on the comparison pages and in the about-page pilot protocol. Read any matchup after the fundamentals and the shared vocabulary makes each page faster to absorb.
When a vendor changes packaging - a free tier shifts, a plan renames, billing-provider support changes - the affected blog guides get the same review as rankings; corrections carry dates. If you spot an outdated assertion, the contact page explains how we reconcile what was written today with what the vendor ships today.
Accessibility and rendering
Where guides show HTML or JSX email patterns, the code must work in the rough world of real clients: Gmail's address-based ID quirks, dark-mode color faults, and text-only fallbacks that remain legible. There is a newsletter-grade revision planned for the password-reset guide with client-by-client QA notes drawn from our own fixtures.
Deliverability fundamentals
Start here if a password reset or receipt ever landed in spam: authentication, reputation, and the controls that actually move placements.
- SPF, DKIM, and DMARC: Email Authentication Explained - 12 min read
- Email Deliverability Best Practices for Developers - 12 min read
- Transactional Email Deliverability: A Provider-Neutral Guide - 14 min read
Architecture decisions
Protocol and stream-boundary choices that shape cost and operational ownership before any vendor is named.
Implementation patterns
Concrete flows - tokens, links, billing-event triggers such as Stripe, Paddle, or Lemon Squeezy events, and fixture guidance.
- How to Build Password Reset Emails That Actually Work - 10 min read
- Stripe Email Integration: Transactional Email Informed by Payments - 11 min read
- SaaS Onboarding Email Sequences That Convert - 13 min read
Choosing a provider
Shortlists and selection criteria, including the two-week pilot protocol we run before changing vendors.
- The Complete Guide to Transactional Email in 2026 - 15 min read
- How to Choose a Transactional Email Tool - 10 min read
A 30-day plan for cleaning up transactional email
- Week 1 - inventory: list every message type, its trigger, owner, and volume. The list is usually roughly double what the team remembers.
- Week 2 - authenticate: align SPF, DKIM, and DMARC on dedicated sending subdomains; separate transactional from campaign traffic before anything else.
- Week 3 - fixtures: build and replay one representative fixture per message class - reset, invoice, payment failure, duplicate event, hard bounce.
- Week 4 - instrument and decide: wire webhook processing with idempotency and suppression, then choose a provider from the selection guide with a two-week pilot rather than a form fill.
Whoever keeps the verification checklist (authentication headers, message IDs, suppression tests, rollback plan) owns the migration - that document outlives the tooling debates.
The Complete Guide to Transactional Email in 2026
Everything developers need to know about transactional email. Infrastructure, authentication, deliverability, and best practices.
Transactional vs Marketing Email: Key Differences for Developers
Understanding the difference between transactional and marketing email. Infrastructure, legal requirements, and choosing the right tools.
Email Deliverability Best Practices for Developers
Technical guide to email deliverability. DNS configuration, authentication, reputation management, and monitoring.
How to Build Password Reset Emails That Actually Work
Technical guide to implementing password reset emails. Security best practices, token generation, expiration, and email template design.
SPF, DKIM, and DMARC: Email Authentication Explained
Technical guide to email authentication protocols. How to configure SPF, DKIM, and DMARC for your transactional email with DNS examples.
API vs SMTP: Which to Use for Transactional Email
Technical comparison of REST API and SMTP for sending transactional email. Performance, error handling, and implementation examples.
Stripe Email Integration: Transactional Email Informed by Payments
Trigger-pattern guidance for wiring Stripe payment events into email flows, with notes for Paddle and Lemon Squeezy similarities.
SaaS Onboarding Email Sequences That Convert
Behavioral sequencing patterns for trial-to-paid onboarding, including the fixture thinking that keeps products honest.
Transactional vs Marketing Email: Key Differences for Developers
Consent, suppression, infrastructure, and the practical plumbing that separates product messages from campaign mail.
Transactional Email Deliverability: A Provider-Neutral Guide
A systematic guide to deliverability evidence, pricing normalization, and a two-week pilot for transactional mail.
How to Choose a Transactional Email Tool
A practical selection shortlist - 13 providers compared, decision tables, and pricing caveats that hedge to official sources.
Frequently asked about this material
Are these guides vendor-neutral?
They cite vendors for factual context and link official pages, but the protocol content - authentication, fixtures, suppression boundaries - applies regardless of provider. Where vendor-specific behavior matters, it appears on the relevant comparison page rather than being woven into generic advice.
How do the guides treat pricing numbers?
As claims in motion. Tiers, quotas, and free allowances change often enough that any static number would mislead - so written figures are hedged ("starting about") and anchored to the vendor's official pricing page. Treat any written figure as a prior to re-verify, not as a quote.
Do the guides include code?
Yes, where protocol or fixture logic needs specificity: DNS records, token-generation patterns, idempotent webhook handlers, and payload inspections. Code is deliberately portable across vendors because integration boundaries - not vendor names - are the hard part.
What redesigns or revisions are planned?
The password-reset guide is next in the render-QA lineage (client-by-client testing notes), and the billing-trigger patterns guide will gain Stripe-first fixtures with notes for Paddle and Lemon Squeezy equivalence. Reader corrections - including production-war stories - accelerate everything the queue; see the contact page.