Skip to main content
Broadcast sending is built around a simple workflow: prepare broadcast-owned content, preview the rendered message, then send now or schedule delivery for later.

​
Prepare the broadcast

A broadcast owns its sender and message content. While it is draft or scheduled, you can update fields such as its name, segment, topic, sender details, subject, preview text, HTML, text, and variable bindings. Updates require the current revision. A successful update increments it; a stale revision returns a conflict instead of overwriting another edit. Reusable templates are separate resources. The Broadcast API does not accept template references. If you want to start from a template, copy the desired template content into the broadcast.

​
Preview before sending

Preview renders the broadcast-owned subject, preview text, HTML, and text without queueing a message. You can provide preview variables that override the broadcast’s base variable_bindings:
Placeholders use triple braces, such as {{{FIRST_NAME}}}. Previewing does not change the broadcast state or materialize recipients.

​
Send now

Send a draft without a future scheduled_at to queue it immediately for asynchronous fanout. Once the broadcast enters queued, its owned content becomes the delivery snapshot and can no longer be edited.

​
Schedule or reschedule

Provide a future scheduled_at value to schedule a draft. A broadcast already in scheduled can be rescheduled with another future timestamp. Updating other fields on a scheduled broadcast does not remove its schedule.

​
Cancel

Cancellation depends on the current state:
  • scheduled → draft: clears the schedule so the broadcast can be edited or scheduled again.
  • queued → canceled: stops remaining fanout work. Messages already handed to email delivery cannot be recalled.
Other states return a conflict.

​
Duplicate for reuse

Duplicating a broadcast creates a new draft with the source audience settings and exact owned message content. You may supply a new name. If the name is omitted or blank, Dugble uses <source name> Copy. The duplicate is independent of the source and receives its own lifecycle and revision.

​
Delete

Only draft and canceled broadcasts can be deleted. Other lifecycle states must finish or be canceled through the supported flow first.

​
After fanout starts

Dugble materializes the audience, applies eligibility rules, and queues an individual email message for each eligible recipient. Recipients can then progress independently through normal email outcomes such as delivery, bounce, complaint, or failure. Use the broadcast recipient list for per-recipient state and Analytics for aggregate results.