Getting Started
Transactional or broadcast?
A password reset and a product announcement are both email, but they're different kinds of email, and Postmark treats them differently. Here's how to tell which one you're sending.
Which one sounds like your email?
It's transactional if…
It's one message to one person, sent because of something they did.
- It's sent automatically, with no one pressing send
- It goes out right after the person does something, like signing up or buying
- It's urgent, and the person expects it within minutes
- You're legally, practically or contractually required to send it
- Welcome email
- Password reset
- Order confirmation
- Receipt
- Invitation
- Comment notification
It's a broadcast if…
It's the same message to many people, sent because you decided to.
- A person writes it and sends or schedules it
- It goes to a stored list of recipients
- People can choose not to receive it
- You expect fewer than 20% of people to open it
- Newsletter
- Product announcement
- Release notes
- Promotion
- Terms of service update
- Daily digest
Side by side
| Transactional | Broadcast | |
|---|---|---|
| Sent to | A single recipient | Multiple recipients at once |
| Triggered by | Something a user does, or doesn't do | You, on your schedule |
| Unsubscribe link | Not required | Required. Postmark adds one to every broadcast message |
| Sending infrastructure | Dedicated transactional IPs | Separate, parallel broadcast IPs |
| MessageStream value in the API | outbound | broadcast |
| SMTP server | smtp.postmarkapp.com | smtp-broadcasts.postmarkapp.com |
Quick check
If one of these is true for your email, here's where it points.
- It's sent automatically, with no human involvedTransactional
- It's sent right after someone does somethingTransactional
- It's sent because someone filled out a formTransactional
- It needs the person's urgent attention or actionTransactional
- It has to arrive within about ten minutesTransactional
- A person writes it and schedules itBroadcast
- It goes to a stored list of recipientsBroadcast
- Recipients can choose not to receive itBroadcast
- You expect fewer than 20% of people to open itBroadcast
Why they stay apart
Postmark runs transactional and broadcast email on separate infrastructure, and the two never mix, including their sending IPs and From domains. That keeps the email people are waiting for from being treated like marketing.
- Faster delivery for urgent email. When both kinds share IPs, inbox providers can mistake time-sensitive messages for bulk and delay them.
- Reputation stays separate. Lower engagement on a newsletter can't hurt your password resets.
- Unsubscribes stay tidy. Opt-outs are managed per stream, so someone leaving your newsletter still gets their receipts.
Choose the stream when you send
Transactional
Code
Broadcast
Code
What do you want to do next?
- Best practices for bulk broadcast sendingHow to send to a list and still land in the inbox.
- 15 best practices for transactional emailA checklist for the emails people are waiting for.
- Watch: Message StreamsA two-minute video on how streams work in your account.
- How to create and send through message streamsSet up a stream and send through it.
- Why broadcasts need an unsubscribe linkWhat Postmark adds for you and how to manage opt-outs.
Last modified on