Transactional Emails
Transactional emails are one-time emails sent to users based on specific triggers, such as password resets or order confirmations.
To send a transactional email, this must be done with the use of the API.
Typically, you will want to send these emails from an existing application that you built, or via a custom integration with Zapier or Make.
To learn how to use this feature, please see the API documentation for transactional emails.
Unsubscribe Behavior
Transactional emails are fundamentally different from marketing emails like broadcasts and sequences. They include essential service-related messages such as:
- Password reset emails
- OTP/verification codes
- Account confirmation emails
- Order receipts and shipping notifications
- Security alerts
Transactional emails will always be delivered, even if the recipient has unsubscribed from marketing emails. This is by design and follows industry standards (CAN-SPAM, GDPR) which distinguish between marketing communications and service-related transactional messages.
However, transactional emails will still be blocked in the following cases:
- Redacted subscribers: If a subscriber has been redacted (GDPR data deletion), transactional emails will not be sent to comply with data protection regulations.
- Global suppression list: If an email address is on the global suppression list (typically due to hard bounces or invalid addresses), transactional emails will not be sent.
