Broadcast is available to every organization. You manage it through the API or the Broadcast section of the dashboard. See Set up Broadcast for the prerequisites.
Broadcast or transactional sending
Use transactional sending when your application triggers a message for one person, such as a password reset or an order confirmation. Use Broadcast when you send one message to a list: the content comes from a single template, and contact properties personalize it for each recipient.
Transactional sending takes the recipients and the content in each request. See Send your first email and Bulk email sending. Broadcast sends a published template version to contacts stored in Nuntly, optionally narrowed by a segment and a topic, now or later. Every broadcast message carries an unsubscribe link and the one-click unsubscribe headers.
Both types respect the suppression list. Only Broadcast respects unsubscribes.
How the pieces fit together
1
Add contacts
A contact is an email address in your organization. You can store custom contact properties on it.
2
3
Write a template
A template holds versions of your content. You publish a version to make it the active one.
4
Create and send a broadcast
A broadcast ties a sender address, a template, and an optional segment and topic together. You send it now or later.
5
Follow delivery
The broadcast moves through a status lifecycle. Each recipient has a send record, and the email events for a recipient carry the broadcast id.
Next steps
Set up Broadcast
Domain choice, domain requirements, and API key permissions
Create and send a broadcast
Scheduling, statuses, recipients, and events
Contacts, segments, and topics
Manage your list and choose who receives a broadcast
Templates
Versions, publishing, and what freezes when
Unsubscribe and suppression
The unsubscribe link, one-click unsubscribe, and the suppression list