Short answer: use transactional email for messages a user action triggers and expects (password resets, receipts, alerts), and marketing email for messages you choose to send to many people (newsletters, promotions). Send them from separate streams or subdomains so a marketing complaint never delays a password reset.
The two categories
Transactional email is triggered by a specific user action and expected by the recipient: password resets, order confirmations, receipts, security alerts. Marketing email is initiated by you, at scale, and the recipient did not take an action that caused this specific message: newsletters, promotions, re-engagement campaigns.
Why mixing them is risky
Marketing email gets spam complaints at a much higher rate than transactional email — that's just the nature of unsolicited-feeling content versus something the user asked for. If both share a sending domain or IP, a complaint spike on a promotional campaign can drag down deliverability for your password reset emails too. That's the failure mode that actually costs money: a user can't log in, and support tickets pile up.
How to separate them properly
- Separate subdomains at minimum —
mail.yourdomain.comfor transactional,news.yourdomain.comfor marketing. - Separate IPs if volume justifies it, so reputation is fully independent.
- Separate sending accounts or API keys in your provider, so a runaway marketing job can never accidentally touch the transactional stream.
- Different monitoring thresholds — a 0.3% complaint rate might be fine for a promo, but should trigger an alert instantly for transactional mail.
A quick test
Ask: "if this email doesn't arrive, does the user notice something broke, or do they just not see an offer?" The first is transactional. Protect it accordingly.