The transactional-versus-marketing distinction is treated as a definitional curiosity in most guides. It is not. Mixing the streams is the most common cause of deliverability collapse for early-stage products. This guide covers the practical rules that decide which side a given email lives on and what changes operationally between them.
Transactional email is one-to-one and triggered by a user action. Marketing email is one-to-many and triggered by you. If a single individual just did something on your product and you are emailing them about it, it is transactional. If you decided to email a list of people, it is marketing. The boundary is blurry only because most providers are lazy about enforcing it.
Transactional: triggered by user action, one-to-one, urgency-sensitive (under 30 seconds expected), implicit consent (the user acted), separate sending stream, full message retention common, suppressions for hard bounces and complaints, no required unsubscribe link in many jurisdictions but recommended. Marketing: triggered by sender, one-to-many, schedule-flexible, explicit consent required (CAN-SPAM, GDPR, CASL), separate sending stream, engagement-driven reputation, mandatory one-click unsubscribe, mandatory list-unsubscribe header at scale.
| dimension | transactional email | marketing email |
|---|---|---|
| Trigger | User action or account event. | Sender decision, schedule, or campaign. |
| Recipient shape | One person, one event. | A list, segment, or audience. |
| Consent basis | Implied by the action in many cases. | Explicit opt-in or lawful marketing basis. |
| Latency expectation | Seconds matter. Auth and billing sends are product paths. | Minutes or hours usually matter less than list health. |
| Unsubscribe | Often optional, but suppressions still apply. | Required. One-click and list-unsubscribe are table stakes at scale. |
| Startup examples | Magic links, receipts, verification, payment failure. | Launch updates, newsletters, lifecycle nudges, winback. |
Order receipts that include a 10% off code: transactional with marketing inside. Welcome emails: transactional in spirit, often sent from the marketing stream. Trial expiration nudges: transactional notice for an account state. Lifecycle drips: marketing, even when they feel transactional. Product update emails: marketing. The test: would a reasonable user interpret this email as a direct response to something they just did? If yes, transactional. If no, marketing.
Send from separate streams. Both Postmark and Loops support this natively; SendGrid does too on higher tiers. Use a different from-domain or subdomain for marketing if you want full reputation isolation (e.g., transactional from mail.yourdomain.com, marketing from updates.yourdomain.com). Apply the right consent model: explicit opt-in for marketing, implicit-by-action for transactional. Honor unsubscribe within 24 hours and treat list-unsubscribe header as mandatory.
Putting promotional copy in receipts (legally fine in some jurisdictions, but pollutes the transactional stream). Sending broadcast updates from the transactional API key (kills sender reputation when an unsubscribe complaint hits). Sending verification emails through the marketing platform (delivery latency too high). Treating "welcome email" as one type when there are five different welcome contexts (trial signup, waitlist confirmation, newsletter subscription, demo request, invite acceptance) that span both sides.
See the Welcome email examples page for templates by signup context, the Lifecycle email marketing examples for triggered marketing, and the Onboarding email sequence examples for hybrid sequences that touch both streams.