- a segment that defines the starting audience
- an optional topic that applies subscription preferences
- sender fields such as
from_email,from_name, andreply_to_email - recipient-facing subject, preview text, HTML, and optional text content
- optional variable bindings used when rendering placeholders
template_id or template_version_id. If your application starts from a reusable template, copy the desired template content into the broadcast when you create or update it.
Broadcast lifecycle
A new broadcast starts as adraft. Drafts can be edited, previewed, sent immediately, or scheduled for later.
draft, scheduled, queued, sent, failed, and canceled.
Broadcast content and audience settings can be edited while the broadcast is draft or scheduled. Once it enters queued, Dugble uses the broadcast-owned content snapshot for fanout and it can no longer be edited.
Owned message content
A broadcast can contain fields such as:segment_id, subject, and html are required when creating a broadcast. name defaults to the subject when omitted or blank. Sender fields, topic_id, preview text, text content, and variable bindings are optional.
Optimistic concurrency
Broadcasts include a positiverevision. Updates must send the current revision so concurrent edits do not silently overwrite each other. A successful update increments the revision; using a stale revision returns a conflict.
Audience counts
A broadcast tracks audience and fanout totals such asaudience_count, eligible_count, suppressed_count, queued_count, and failed_count.
These counts distinguish the size of the selected segment from the contacts that were actually eligible and successfully handed to email delivery.
Audience
Learn how segment membership, subscriptions, and suppressions affect eligibility.
Sending
Understand previewing, editing, immediate sends, scheduling, cancellation, and duplication.
Analytics
Interpret delivery and engagement metrics for a broadcast.
Templates
Manage reusable message templates independently from broadcasts.