Broadcast Emails
Broadcast emails allow you to send one-time messages to your subscribers. This guide covers creating, testing, scheduling, sending, and analyzing broadcast emails.
Broadcasts are organized per Channel. You cannot send a broadcast to subscribers from another channel. Make sure you’re in the correct channel before creating a broadcast.
Broadcasts Overview
The Broadcasts section shows all your email campaigns in a table format, displaying the broadcast ID, name, recipient count, status, engagement metrics, and both the sent and creation dates.


From this page, you can:
- View all broadcasts for the current channel
- Create new broadcasts
- Filter by status (Draft, Scheduled, Sending, Sent)
- Search broadcasts by name
- Monitor engagement metrics (Open Rate, CTR, Unsubscribe Rate, Bounce, Spam)
Sent vs Created
The list shows two dates, and for scheduled sends they are rarely the same:
- Sent: when the broadcast actually went out to subscribers. Empty (
—) for anything not yet sent. - Created: when the broadcast was first drafted.
A broadcast drafted on the 1st and scheduled to go out on the 14th shows both dates, so the engagement rates on the same row can be read against the date recipients actually received the email.
Bounce and Spam columns sit alongside the existing rates, both expressed as a percentage of total recipients. Rates are shown once a broadcast has finished sending; before that the columns read N/A.
Creating a Broadcast
Step 1: Choose Content Format
Click New Broadcast to open the format selection dialog:


Choose from four options:
- Rich Text (Recommended): A visual editor perfect for newsletters and announcements
- HTML: Direct code editing for custom designs
- Drag and Drop: Build the email from blocks in the Drag-and-Drop Email Builder
- Start from Template: Begin with a professionally designed template
Step 2: Content Tab
After selecting your format, you’ll see the broadcast creation wizard with four tabs. The Content tab is where you compose your email:


Basic Fields:
- Name: Internal reference for easy identification (e.g., “Newsletter #12”). Leave it blank and the broadcast takes its subject, so lists and page titles always read as something
- Subject (Required): The email subject line recipients will see
- Preview Text: Text shown alongside the subject in email clients
- Reply-To: Optional custom reply address
- Tags: For internal organization
Rich Text Editor Features:
- Font selection and text color
- Formatting (bold, italic, underline, strikethrough)
- Links and images, uploaded or picked from File Assets
- Lists (bulleted and numbered)
- Text alignment
- Undo/redo
3.1+
Insert from a plugin: when a plugin with an insert page is on in the channel (for example Polls), the rich text and HTML editors show Insert from a plugin. Pick the plugin, choose what to insert in the dialog (for example a poll), and click its insert button. The rich text editor keeps the inserted HTML as one piece that you can move or delete. The HTML editor puts it at the cursor. Broadcast cleans the HTML first. You need permission to write emails in the channel.
The Inbox Preview shows how your email will appear in recipients’ inboxes as you type.
Step 3: Settings Tab
Configure tracking and delivery options:


Tracking Options:
- Track opens: Inserts an invisible pixel to record when emails are opened (note: some email clients block tracking pixels)
- Track clicks: Rewrites links to track click-through rates
Email Server Options:
- Use any email server (load balanced): Distributes emails across all active servers
- Optionally select specific servers for this broadcast
Custom Email Headers:
Add or override email headers for specific requirements. Header values support Liquid variables, so you can include dynamic subscriber data. For example, to set a custom List-Unsubscribe header that points to your own domain:
List-Unsubscribe: <https://example.com/unsubscribe/{{ subscriber.data.unsubscribe_token }}>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
All standard Liquid variables are available in header values, including {{ subscriber.email }}, {{ subscriber.data.* }}, and {{ unsubscribe_url }}. Static header values (without Liquid tags) are passed through unchanged with no overhead.
3.5+
Web Version:
Turn on Publish a web version to give the email a public page with its own permanent URL, in the channel’s web archive. The page goes live when the broadcast is sent. You can set the URL, the page title, the description and a social image, and add a “View in browser” link to the email. See Web Versions and Archive.
Step 4: Audience Tab
Select who will receive your broadcast:


Targeting Options:
- All Subscribers: Send to everyone on your list
- Segments: Target specific groups based on your segment rules
You can select multiple segments: subscribers matching any selected segment will receive the broadcast.
Excluding segments:
Below the audience, the Exclude list removes people: nobody in a ticked segment gets the broadcast, even when they are in the audience above. Use it for a list of people who must never get a campaign, such as competitors. With All Subscribers, the exclusion applies to everyone.
- A segment in the audience cannot also be excluded. Ticking one disables the other box.
- A segment with no subscribers shows a warning, because it excludes nobody. Check its rules.
- The Review tab names the excluded segments and how many people they take out. The send dialog, the schedule screen and the broadcast’s Audience card name them too, and every recipient count uses them.
- A retry of a failed broadcast keeps its exclusions.
- A segment that an unsent broadcast excludes cannot be deleted. Remove it from the broadcast’s exclusions first.
Note
Check an exclusion segment’s rules before you rely on it. Several rules joined with Match ALL can match nobody: no address contains eleven different domains. The segment builder warns when a group counts 0 but people match one of its rules. See Segments.
Step 5: Save or Send
- Save Draft: Save your progress to continue later
- Autosave: Enable automatic saving as you work (toggle at bottom of screen)
- Proceed through the wizard tabs using Next buttons
Testing a Broadcast
Before sending to all subscribers, test your broadcast. From the broadcast detail page, click the dropdown arrow next to Send now:


Click Send test email to open the test dialog:


Enter an email address you have access to and click Send test to verify:
- Email formatting and layout
- Links work correctly
- Personalization displays properly
- Content appears correctly across email clients
3.1+
A test email has no real subscriber. Plugin links in it, such as poll buttons, are test links: a click shows “This is a test email” and saves nothing. Plugin merge tags are empty.
Broadcast Detail Page
After creating a broadcast, view its details and preview:


The detail page shows:
- Recipients: Estimated number of subscribers who will receive the broadcast
- Audience: Selected targeting (All Subscribers or specific segments)
- Tracking: Which tracking options are enabled
- Email Preview: Gmail-style preview of how your email will appear
- Email Servers: Which servers will send this broadcast
- Details: Broadcast ID and creation date
Previewing Personalized Content
2.52+
The preview has no real subscriber, so it fills in your Liquid with mock data. Liquid logic such as {% if %}, {% else %} and {% assign %} runs the same way it does when the email is sent, so the tags never show as text in the preview.
Above the preview, the Preview data panel lists each subscriber variable that the email reads, with a mock value:
- A checkbox for a key that the email only tests as true or false, for example
{% if subscriber.data.city_oakville == true %}. Every checkbox starts off. - A list for a key that the email compares with values, for example
"pro"and"free". For a standard field, such as{% if first_name == "Sam" %}, the list also has the sample value and starts with it. - Checkboxes for tags that the email tests with
contains, for example{% if subscriber.tags contains "vip" %}. - A text field for a variable that the email shows, such as
{{ first_name }}. Standard fields start with sample values (Alex Rivera, alex@example.com). Custom data starts as the key name in brackets, for example[city]. When the email tests a variable and also shows it ({% if subscriber.data.city %}You live in {{ subscriber.data.city }}{% endif %}), clear the field to see the email without that branch. - A text field for a number that the email compares with
>,<,>=or<=, for example{% if subscriber.data.age > 18 %}. Type a number to choose the branch.
Change a value and the preview updates. Use this to see each version of the email before you send it. The mock values are highlighted in green, after any Liquid filters, so {{ first_name | upcase }} shows ALEX highlighted. The panel never reads real subscriber data, and the values are not saved.
A value that you type goes into the email the way subscriber data does when the email is sent: filters such as escape, times and size see the value itself, and simple HTML such as <b> renders. Scripts, forms and other unsafe HTML are removed from typed values.
Variables that the email sets itself with {% assign %} or {% capture %} are not in the panel: they follow from the values you choose. Links render as placeholders (#unsubscribe, #preferences, #confirmation).
The preview has only the variables that the email gets when it is sent. A broadcast or sequence email has no {{ channel_name }} or {{ confirmation_url }}, so the preview shows them empty. A transactional email has only the standard fields and the links. A confirmation email has the standard fields, custom_data, {{ channel_name }} and the links.
If the email has a Liquid syntax error, the preview shows the email as written, under a red notice with the error.
A rich-text email that uses Liquid gets the same preview and panel. The Preview tab of the HTML code editor also fills in Liquid with mock data, with the default values and no panel.
Sending a Broadcast
Send Immediately
Click Send now to immediately queue your broadcast. The system will:
- Validate all broadcast settings
- Queue emails for all targeted recipients
- Begin sending through configured email servers
- Display real-time progress
Broadcast refuses to send a broadcast with no one to send to, for example when its segment matches nobody or the channel has no active subscribers. Instead of marking it sent, it shows This broadcast has no subscribers to send to and leaves it as a draft. Check the Audience tab, or that the channel has active subscribers. The same check applies to sends from the API, the CLI and Ask AI.
2.49+
For a broadcast sent to a topic, the message names the topic: This broadcast is for the topic “Webinars”, and no subscribers have that topic on.
Schedule for Later
Select Schedule send from the options dropdown to:
- Set a specific date and time
- Schedule across different time zones
- Plan campaigns in advance
A broadcast with no recipients can still be scheduled, since its segment may fill up before the send time. If it still matches nobody when the time comes, it moves to Failed with the reason, rather than going out to no one.
Broadcast Statuses
A broadcast moves through these statuses. The badge next to its name on the detail page always shows the current one (both Future scheduled and Scheduled read “Scheduled” on the badge), and the Filter by status list in the sidebar gives quick counts for the four you look at most.
| Status | Meaning | What you can do |
|---|---|---|
| Draft | Being created or edited | Edit, send, schedule, duplicate, archive, delete |
| Future scheduled | Waiting for its scheduled time | Cancel the schedule, which returns it to draft |
| Scheduled | Handed to the sending job, about to start | Pause, abort |
| Queueing | Recipients are being assembled | Pause, abort |
| Sending | Emails are going out now | Pause, abort |
| Paused | Stopped part-way through, by you | Resume, abort |
| Sent | Finished, every recipient was processed | Duplicate, archive |
| Partial failure | Finished, but some recipients failed | Duplicate, archive |
| Failed | Stopped by a channel or server error (e.g., revoked API token) | Resume, duplicate, archive |
| Aborted | Stopped permanently, by you | Duplicate, archive |
Note
Sent and Partial failure are both finished states, and both expose full delivery stats. The difference is only whether every recipient succeeded. Treat a partial failure as a completed send with something worth investigating in Email Metrics, not as a send that needs repeating.
Archiving is separate from status. An archived broadcast keeps whatever status it had and is simply hidden from the default list.
Controlling a Send in Progress
Once a broadcast is sending you are not stuck watching it. The detail page swaps its buttons for the controls that apply to the current state.
Pausing
While a broadcast is scheduled, queueing, or sending, the header shows Pause, with Abort send in the dropdown beside it.


The status changes to Paused at once. The sending job checks the status about four times each second, so a few emails that were already on their way may still go out: at full speed, at most about 8. A broadcast that waits for room on its email server sends nothing more. Emails already handed to your email server cannot be recalled.
A broadcast that waits for room in its server’s hourly limit stays Sending. It is not stalled: its page shows Waiting for room on the email server and the time of the next send, and it continues by itself. See Email Server Rate Limits.
Pause when you spot a broken link or a wrong merge tag and want to stop the bleeding while you decide what to do.
Resuming
A paused broadcast shows Resume instead.


Resuming re-queues the send and picks up where it stopped, so subscribers who already received the email do not get a second copy. It needs the channel’s sender and email server settings to still be valid, and it will refuse with an error if they are not.
Warning
Pausing does not let you edit the content. A broadcast that has started sending is locked, so half your list would get the old version and half the new one. If the content is wrong, abort, fix a duplicate, and send that to the remainder.
Aborting
Abort send stops the broadcast permanently and moves it to Aborted. There is no resume from there, and emails already sent stay sent. Use it when you want the send stopped for good rather than paused.
Failed Broadcasts and Resume
A broadcast enters the Failed state when it encounters a channel or server level error and cannot continue sending. Common causes include a revoked API token for your email provider or a disabled email server.
When a broadcast fails, a Resume button appears on the detail page. After fixing the underlying problem (re-authorizing your provider account, re-enabling the server, etc.), click Resume to continue sending.
Resume picks up where the broadcast stopped. Recipients who already received the email will not get it again. The send uses the same content and targeting as before, read as it is now: people who joined since are included, and people who unsubscribed, turned the topic off, or were suppressed since are left out. Addresses the email provider permanently rejected are not tried again.
If an SMTP server permanently rejects a single recipient’s mailbox (for example “550 5.1.1 user unknown”, or a full or disabled mailbox), only that recipient is marked failed and the broadcast keeps going. If any recipient failed this way, the broadcast ends as Partial failure. A rejection that isn’t about the mailbox, such as a policy, spam or sender-not-allowed rejection (5.7.x), still stops the broadcast as Failed, because it would hit every recipient. Fix the cause and click Resume.
2.49+
If an SMTP server permanently rejects a single recipient’s mailbox (for example “550 5.1.1 user unknown”, or a full or disabled mailbox), only that recipient is marked failed and the broadcast keeps going. If any recipient failed this way, the broadcast ends as Partial failure.
When the reply says the address does not exist, Broadcast also treats it as a hard bounce, the same as a bounce webhook from your email provider. The subscriber is deactivated and added to the channel suppression list, their history reads “Bounced (Unsubscribed) [Send]”, and the bounce webhooks fire. This applies to the codes 5.1.1, 5.1.2, 5.1.3, 5.1.6 and 5.1.10, and to a reply with no code that plainly says the user or mailbox does not exist. A full or disabled mailbox (5.2.x) or an unclear reply fails the recipient for this broadcast only.
A rejection that isn’t about the recipient’s mailbox stops the broadcast as Failed, because it would hit every recipient. That includes a policy, spam or sender-not-allowed rejection (5.7.x), a problem with the sender’s address (5.1.7 or 5.1.8), and a reply that names the sender. Fix the cause and click Resume.
Resume is available on Failed and Paused broadcasts. If you need to change the content or targeting instead, duplicate the broadcast. A plain duplicate is a new broadcast, so it goes to everyone again, including people who already received the original. To send a corrected copy only to the people the failed send missed, use a retry.
Retrying a Failed Broadcast
- On the Failed broadcast, click Duplicate.
- On the copy, open the subscriber targeting (Segments).
- Tick Target only subscribers the last broadcast (name) did not reach yet. Addresses the email provider rejected are left out.
- Change the content if you need to, then send.
A retry follows these rules:
- It reaches the subscribers the failed send did not reach yet. It uses the failed send’s own audience (segments and topic), even if the failed send was itself a copy of an older broadcast with another audience.
- Nobody gets it twice. People reached by the failed send, or by any other retry of it (including a second retry of the same failed send), are left out.
- The audience is read as it is now, the same as Resume. People who joined since are included. People who unsubscribed, turned the topic off, or were suppressed since are left out.
- Addresses the email provider permanently rejected during the failed send (for example “550 5.1.1 user unknown”, or a full or disabled mailbox) are left out. Sending to them again would bounce again and hurt your delivery.
If nobody is left, Broadcast refuses to send: “Everyone this retry is for already got "name” or has unsubscribed since. Nobody is left to send to.“ If the failed broadcast was deleted, the retry reaches nobody, and the refusal says so: "The broadcast this retry belongs to was deleted, so it has nobody to send to.”
The Audience card of a retry says Only people who missed it and Retry of with the failed broadcast’s name (or Retry of #id, deleted: reaches nobody). The Recipients count on a retry is the retry set. The send check, scheduled sends and the AI tools use the same count.
For every broadcast, the Send Broadcast? dialog says how many subscribers it goes to: “It goes to N subscribers.”
Recipient Counts
The Recipients card on a sent broadcast reads “X of Y delivered”, where Y is the recipient total recorded when the send began. It is the denominator behind every rate on the page.


These two numbers can drift apart. If subscribers unsubscribed or were deactivated between the moment the total was recorded and the moment they were reached, the recorded total stays higher than the number of actual recipients, and every rate is computed against a denominator that is too large.
The circular arrow on the Recipients card fixes this. It resets the total to the real recipient count.


Warning
Recalculating is irreversible and permanently changes the broadcast’s analytics. Only do it when you are confident the recorded total is wrong, since a broadcast that genuinely failed to reach people should keep the higher denominator: those recipients were real, they just did not get the email.
Analytics and Reporting
After sending, these metrics become available:
- Open Rate: Percentage of recipients who opened the email
- Click Rate (CTR): Percentage who clicked links
- Unsubscribe Rate: Recipients who opted out after this broadcast
- Delivery Rate: Successfully delivered vs. total sent
- Bounce Rate: Emails that couldn’t be delivered
2.49+
Mail captured by a test server is not in the open and click figures. Nobody received it, so the opens and clicks of the test inbox are left out, and the open and click rates are a percentage of the recipients whose mail was not captured. The broadcast page, the broadcasts list and its export, the delivery chart, the link statistics and the API all use the same figures. Bounce, spam and unsubscribe rates are still a percentage of every recipient.
Recent Activity
A sent broadcast with tracking enabled shows Recent Activity: one row per recipient, with a column for each event.


| Column | What it shows |
|---|---|
| Recipient | The email address. Where that address is a subscriber in this channel, it links to their profile. |
| Status | The most significant outcome for that recipient: Bounced, Spam, Unsubscribed, Clicked, Opened or Delivered. A bounce or complaint reason appears underneath. |
| Delivered | When the email reached the recipient. See the note below on where this time comes from. |
| Opened / Clicked | When each event happened, or — if it didn’t. |
Where a recipient both engaged and failed (opened the email and later marked it as spam), Status shows the failure, since that is the more important fact.
2.49+
Mail sent through a test server has the status Captured, not delivered, above every other status, Bounced and Spam included. Nobody received it. The test inbox can load the tracking pixel and follow links, so a captured row can show an open or a click that no real person made. A broadcast with captured mail also has a Captured filter, and the other event filters leave captured rows out.
Where the Delivered time comes from
Delivery is reported by your email provider, through the delivery webhook you configure for it. Opens and clicks are different: Broadcast records those itself, from the tracking pixel and rewritten links, so they need no webhook at all.
That means a provider which doesn’t send delivery events (or one whose webhook isn’t set up yet) leaves Broadcast with no delivery time of its own to show. Since an email cannot be opened or clicked without having arrived, an open or a click is taken as confirmation that it was delivered, and the send time stands in for the delivery time. Those times are shown with a dotted underline, and hovering one says that the provider reported no delivery time.
A recipient who neither opened nor clicked, on a channel with no delivery webhook, still shows —: nothing has confirmed that the email arrived. If a whole broadcast reads that way, check the webhook configuration for that channel’s email server, see Webhooks.
A bounce is never treated as a delivery, so a bounced recipient’s Delivered column stays empty.
Sorting: click Recipient, Delivered, Opened or Clicked to sort by that column; click again to reverse it. By default the most recently active recipients come first, so whoever just clicked is at the top. Recipients with no activity in the sorted column always sort to the end.
Two controls narrow the table:
- Search recipient: matches any part of an email address. Enter a full address to check one person, or a domain such as
northwind.comto see everyone from one organisation. - Event filters: All, Opened, Clicked, Bounced, Spam, and Unsubscribed limit the table to a single event type. Useful for questions like “who bounced?” without paging through every recipient.
2.49+
A broadcast with mail captured by a test server also has a Captured filter.


The search, the event filter and the sort all combine, so you can ask for “everyone at northwind.com who clicked, most recent first”. All three stay applied as you page through results.
Exporting the activity
Export CSV, at the end of the filter row, downloads the table you are looking at. The search, the event filter and the sort all carry into the file, so filtering to Bounced and exporting gives you exactly the bounced recipients.


The file has one row per recipient and a column for each event, along with the timestamps and any bounce or complaint reason:
| Column | What it contains |
|---|---|
| Recipient | The email address |
| Delivered, Opened, Clicked, Bounced, Spam, Unsubscribed | Yes or No for each event |
| Delivered At, Opened At, Clicked At, Bounced At | When each happened, blank where it didn’t |
| Failure Reason | The bounce or complaint reason, where the provider gave one |
2.49+
The file has one more column at the end, Status: the same status as the table, for example Clicked, or Captured, not delivered for mail a test server captured. New columns are added at the end, so a script that reads columns by position keeps working.
On a captured row, Delivered, Opened, Clicked, Bounced and Spam and their times are blank, even when the test inbox opened the email or followed a link: the row says what its status says. Unsubscribed and Failure Reason are kept.
Dates are ISO 8601 in UTC (2026-07-26T14:30:00Z), while the dashboard shows times in your browser’s time zone. Exporting needs the same permission as viewing the broadcast: the table already shows every recipient’s address on screen, so the file discloses nothing new.
The export covers one broadcast. To compare sends, export the broadcasts list instead, see below.
Exporting the Broadcasts List
Export CSV, beside the search box on the broadcasts list, downloads one row per broadcast with the figures the list shows: a performance summary across sends rather than a per-recipient dump.


As with every export in Broadcast, you get what the list is currently showing: the search, the tag filter, the status filter and the Active/Archived tab all carry into the file.
| Column | What it contains |
|---|---|
| ID, Subject, Status | Identifying the broadcast |
| Created At, Sent At | Blank Sent At for anything not yet sent, see Sent vs Created |
| Recipients | How many the broadcast went to |
| Open Rate %, Click Rate %, Unsubscribe Rate %, Bounce Rate %, Spam Rate % | The same figures as the list columns |
| Tags | Comma-separated, in one cell |
A rate reads N/A rather than 0.0 where there is nothing to measure: a broadcast that has not sent, or a rate whose tracking is switched off. A zero would claim a real measurement of nothing.
This export contains no recipient data, so it needs only permission to view broadcasts: it is the report to hand a client.
Managing Broadcasts
The options dropdown next to the main button changes with the broadcast’s status, so you only ever see actions that apply.
| Action | Available when | What it does |
|---|---|---|
| Edit | Draft | Reopens the composer. A broadcast that has started sending is locked |
| Schedule send | Draft | Sets a date and time instead of sending now |
| Cancel schedule | Future scheduled | Returns the broadcast to draft |
| Duplicate | Draft or finished (Sent, Partial failure, Failed, Aborted) | Creates a fresh draft copy named “Copy of …”, carrying over the content, subject, and settings |
| Archive | Draft or finished | Hides it from the default list without deleting it |
| Unarchive | Archived | Returns it to the default list |
| Delete | Draft | Removes it permanently |
Duplicating is the safe way to iterate. Because the copy is always a new draft, you can rework a broadcast that has already gone out without any risk of touching the original or its analytics.
To work through many at once, select broadcasts with the checkboxes on the list page and use the bulk Archive and Unarchive actions.
Best Practices
Content:
- Write compelling subject lines (aim for under 60 characters)
- Use preview text to complement your subject
- Keep content focused and valuable
Deliverability:
- Maintain clean subscriber lists
- Monitor bounce and spam rates
- Use proper sender authentication
Testing:
- Always send a test email before broadcasting
- Verify on multiple email clients
- Check all links work correctly