Broadcasts
Send a one-shot email, webhook, push, or combination to consented customers or segments.
What a broadcast is
A Broadcast is a one-shot send to everyone who matches your audience. You can include email, webhook, push, or any combination. At least one channel stays selected. Use broadcasts for launches, announcements, and one-time campaigns. For multi-step follow-ups, use Automations.
Open Engage → Broadcasts.
Grow+ (Advanced Engage): conversion goals, holdout / A/B arms, recipient local-time schedule, quiet-hours deferral, and marketing topics require Grow or above. Indie can still send basic broadcasts. See Plans & entitlements.
Create and launch
The editor walks through six steps: Compose, Channels, Message, Schedule, Audience, and Review.
- Compose a name, and optionally a description and tags. On Grow+ you can also set a Conversion goal and a Holdout weight (%) here.
- Channels. Choose email, webhook, push, or several. You cannot clear the last channel.
- Message. Write the content for each selected channel. Reuse content blocks for shared footers and fragments.
- Schedule. Choose Send on launch or Schedule for later.
- Audience. Pick segments and, when topics mode is on (Grow+), a marketing topic.
- Review, then Send now or Schedule.
A conversion goal (Grow+) is the event that counts as success within a window of days. When the goal is a purchase, revenue is net webhook gross in that window, including renewals and refunds. The goal locks when the broadcast launches so reporting stays comparable.
Holdout weight (Grow+) is a share of recipients who receive nothing on any selected channel, so you can compare them with people who did. Remaining weight goes to the message. Analytics can show arms under A/B variants.
Drafts stay editable until you launch. Scheduled broadcasts can be cancelled from the broadcast detail page before they go out.
A person who matches the audience receives each selected channel they qualify for. Email and push to the same person are two deliveries, and each counts toward the Engage message allotment. Several devices on one push delivery still count as one message.
Schedule timezone
When you schedule for later:
| Option | Behavior |
|---|---|
| Each recipient's local time | Grow+. Expands at launch so every Customer gets that clock time in their timezone (app default timezone if theirs is unknown) |
| Same time for everyone | Interpreted in the app default timezone from Frequency Cap settings |
Quiet hours (Grow+, under Frequency Cap) can defer a delivery that would land in the quiet window. They do not drop the send, and they apply to email, webhook, and push.
Emails per hour
On the schedule step, Emails per hour is optional. Leave it empty to send as fast as the provider accepts. A number from 1 to 100,000 admits that many provider submits per UTC hour and holds the rest until the next hour. Recipient-local time and quiet hours still decide the earliest send. The pace is fixed at launch. Drafts can change it. Pause does not.
Pause and resume
From a launching or sending broadcast, Pause holds the remaining queue. Resume continues at the same hourly pace, so the backlog does not go out all at once. Stop sending cancels the broadcast and skips anyone who has not gone out. A paused broadcast can still be stopped.
Audience
- With no segments selected, Rheo targets customers who pass the audience check for the channels you picked.
- Select one or more Segments to narrow the audience. Segments live under Customers → Segments.
- When marketing topics mode is on, assign the broadcast's topic so only people granted for that topic are eligible. Those people also need an email address.
| Channels on the broadcast | Who is in the audience |
|---|---|
| Includes email (alone, or with webhook and/or push) | Consented customers with an email address that is not suppressed |
| Push without email (push alone, or push plus webhook) | Customers with an active push subscription in this environment. Delivery still requires granted marketing consent |
| Webhook only | The email audience: an address, granted consent, and no suppression |
If the broadcast includes email and push, someone without a registered device still receives the email and webhook. The push for that person is skipped.
Templates and messages
Engage → Templates holds reusable starters for each channel. Use a template copies that content into the broadcast. Editing the broadcast afterward does not change the library template. See Templates.
Merge tags
Email subject and body, webhook JSON strings, and push title, body, link, and data use the same tags. Flow copy uses the same default spelling. See Variables in copy.
{{key}}is replaced with the Customer value when it is present and not empty{{key | default: "fallback"}}uses the quoted fallback when the value is missing or empty{{key | default: fallback}}is the same when the fallback has no spaces{{key | "fallback"}}is the same quoted fallback
Built-in keys include email and app_user_id. Delivery keys unsubscribe_url and preferences_url resolve to signed per-recipient links at send time—add them to your footer (HTML, visual blocks, or a content block). Rheo does not append a hidden footer after you compose. The provider still receives a List-Unsubscribe header for one-click unsubscribe in the mailbox.
Customer attributes (for example first_name) are available when your app stores them on the Customer. Keys are flat names. Dotted paths are not resolved.
Before launch, Rheo warns if the rendered email body is missing an unsubscribe or preference center link. Warnings do not block sending.
The composer supports:
- Visual mode: drag blocks into a layout
- HTML mode: edit the HTML directly
Switching back to Visual after HTML edits that diverge from the layout can discard those HTML-only changes. The composer warns you first.
Subject and body accept merge tags.
Send test email delivers a personalized preview through your connected provider. Test sends do not enroll contacts or count toward broadcast analytics. For test-environment traffic, destinations may be limited by the test destination allowlist.
Webhook
Set the endpoint, optional headers, and a JSON object payload. String values can include merge tags. Fields mode edits a flat object of strings, numbers, and booleans. Nested objects and arrays stay in raw mode.
You can mark a header as secret. Rheo stores that value encrypted. Reserved names (Content-Type, User-Agent, X-Rheo-Delivery-Id, X-Rheo-Test) are not taken from your list. Rheo sends those itself.
Send test webhook POSTs the rendered payload. You can sample a Customer or type email, app user id, and attributes by hand. The test request includes X-Rheo-Test: 1.
In production the endpoint must be https on a public host.
Push
Set a title, body, optional link (a URL or app deep link), and a data JSON object. Title, body, link, and string values in data can include merge tags. Title and body are required.
Send test push delivers to the selected customer's registered devices in the current environment. A customer with no active subscription cannot receive the test.
After launch
Broadcast detail shows delivery counts, and for email also opens, clicks, unsubscribes, and frequency-cap skips, plus conversion metrics when a goal was set. If you configured a holdout, compare arms under A/B variants.
Engage → Overview counts accepted sends and deliveries for every channel. Open rate, click rate, and the open-time heatmap are email. When more than one channel has sends in the range, By channel lists accepted sends.
From the terminal
List, create, schedule, send, pause, resume, and export recipient rows with rheo engage broadcasts in the CLI. Set pacePerHour on the create or update JSON body (omit it or send null for unlimited). broadcasts export writes a CSV. Send now requires an owner or admin key. Editors can draft and schedule.
Related
- Set up Engage — Provider, push credentials, quiet hours, frequency cap
- Automations — Multi-step journeys
- Customers — Segments and consent on profiles
- CLI —
rheo engage broadcasts