# 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.

<Verdict tone="mint" title="The short answer">
If a person's action triggers it and one person gets it, it's **transactional**. If you decide to send it, on your schedule, to a group, it's a **broadcast**.
</Verdict>

## Which one sounds like your email?

<PickOne
  a={{
    name: "Transactional",
    tone: "mint",
    title: "It's transactional if…",
    lead: "It's one message to one person, sent because of something they did.",
    points: [
      "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",
    ],
    chips: [
      "Welcome email",
      "Password reset",
      "Order confirmation",
      "Receipt",
      "Invitation",
      "Comment notification",
    ],
  }}
  b={{
    name: "Broadcast",
    tone: "yellow",
    title: "It's a broadcast if…",
    lead: "It's the same message to many people, sent because you decided to.",
    points: [
      "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",
    ],
    chips: [
      "Newsletter",
      "Product announcement",
      "Release notes",
      "Promotion",
      "Terms of service update",
      "Daily digest",
    ],
  }}
/>

## Side by side

<Compare
  a={{ name: "Transactional", tone: "mint" }}
  b={{ name: "Broadcast", tone: "yellow" }}
  rows={[
    ["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.

<Rules
  a={{ name: "Transactional", tone: "mint" }}
  b={{ name: "Broadcast", tone: "yellow" }}
  items={[
    { when: "It's sent automatically, with no human involved", pick: "a" },
    { when: "It's sent right after someone does something", pick: "a" },
    { when: "It's sent because someone filled out a form", pick: "a" },
    { when: "It needs the person's urgent attention or action", pick: "a" },
    { when: "It has to arrive within about ten minutes", pick: "a" },
    { when: "A person writes it and schedules it", pick: "b" },
    { when: "It goes to a stored list of recipients", pick: "b" },
    { when: "Recipients can choose not to receive it", pick: "b" },
    { when: "You expect fewer than 20% of people to open it", pick: "b" },
  ]}
/>

<Note tone="yellow" title="Some messages sit in the middle">
Event updates, legal notices and activity digests can go either way. Look at their other traits: does a person trigger it, is it urgent, does it go to a list? Those decide it.
</Note>

## 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

<div className="decide-pair">

<div>

**Transactional**

```bash
curl "https://api.postmarkapp.com/email" \
  -X POST \
  -H "X-Postmark-Server-Token: server token" \
  -d '{
    "From": "you@yourdomain.com",
    "To": "friend@example.com",
    "Subject": "Your receipt",
    "TextBody": "Thanks for your order!",
    "MessageStream": "outbound"
  }'
```

</div>

<div>

**Broadcast**

```bash
curl "https://api.postmarkapp.com/email" \
  -X POST \
  -H "X-Postmark-Server-Token: server token" \
  -d '{
    "From": "updates@yourdomain.com",
    "To": "everyone@example.com",
    "Subject": "What’s new in 4.0",
    "HtmlBody": "...",
    "MessageStream": "broadcast"
  }'
```

</div>

</div>

<Note tone="mint" title="Not naming a stream?">
Postmark sends through your default transactional stream, **outbound**. Always name the stream for broadcasts.
</Note>

## What do you want to do next?

<Paths
  items={[
    {
      title: "Best practices for bulk broadcast sending",
      body: "How to send to a list and still land in the inbox.",
      to: "/guides/best-practices-for-broadcast-sending",
      tone: "yellow",
      icon: "Layers",
    },
    {
      title: "15 best practices for transactional email",
      body: "A checklist for the emails people are waiting for.",
      to: "/guides/transactional-email-best-practices",
      tone: "mint",
      icon: "Mail",
    },
    {
      title: "Watch: Message Streams",
      body: "A two-minute video on how streams work in your account.",
      to: "/videos/message-streams",
      tone: "blue",
      icon: "Sparkles",
    },
    {
      title: "How to create and send through message streams",
      body: "Set up a stream and send through it.",
      to: "https://postmarkapp.com/support/article/how-to-create-and-send-through-message-streams",
      tone: "slate",
      icon: "Globe",
    },
    {
      title: "Why broadcasts need an unsubscribe link",
      body: "What Postmark adds for you and how to manage opt-outs.",
      to: "https://postmarkapp.com/support/article/1217-why-broadcasts-require-an-unsubscribe-link",
      tone: "red",
      icon: "Inbox",
    },
  ]}
/>
