Broadcasts
A broadcast brings a customer selection, an email and a send time together for one campaign. Use it for a launch, a newsletter or a reason to return. Brief maxinja on the outcome, then review the audience, message and cost before committing the send.
For a message your product triggers for one person, use a template. For a journey with triggers, waits and decisions, use a workflow.
Decide who it is for
Choose New broadcast and select the contact schema. That schema stays with the broadcast. Choose a saved segment to narrow the audience, or deliberately select all contacts in the schema. A segment must belong to that schema.
The Audience tab lets you change the selection before preparation starts. maxinja can also build a condition specific to this campaign. Read its plain-language summary and check representative contacts: an audience count alone cannot tell you whether the relationship, purchase or behavior is the one you intended.
The count you see while planning is an estimate of matching records. Consent, missing addresses, duplicate addresses and suppression can reduce the eventual send. The saved selection becomes fixed when campaign preparation begins; contacts who qualify afterward are not added to that run.
Write the email
Open Composer, or choose Add content if the broadcast has no email yet. The audience already determines the recipient: the email expects one contact from the selected schema. Use that contact's data and relationships for fixed personalization, and Adaptyle when the message needs generated copy for each person.
Review the sender, subject, preview text, body, links, language and unsubscribe behavior. Add valid sample data and generate a successful preview. A broadcast cannot proceed with a missing sender, empty subject or body, an incompatible recipient, or missing required preview data. Warnings such as an unnamed campaign or an intentionally broad audience are different from errors that block sending.
A successful preview checks one example. It does not prove every customer's data is complete or every generated email will pass its checks. Preview examples with sparse data, different interests and different languages before scaling.
Choose when it goes
New broadcasts start with Composer and Send. The Send tab brings together the audience, content and schedule.
| Choice | What happens |
|---|---|
| Send now | Queues preparation and sending after confirmation. It does not mean every message has already left. |
| Schedule for later | Sets the earliest dispatch time. Preparation may begin before that time. |
| Save as draft | Saves your work without scheduling a send. |
After the first choice, the full navigation includes Audience, Composer, Schedule, Emails and Metrics. Composer and Schedule are editable in a draft and become read-only when scheduled. A broadcast is a one-time campaign, not a recurring schedule.
Preparation, review and dispatch
maxclicks separates preparation from delivery. It fixes the audience selection and campaign revision, renders recipient messages, applies the applicable content checks, then releases eligible messages for dispatch. A scheduled campaign can start preparation early so its content is ready for the send time. Treat preparation as the point after which audience edits close, even if the scheduled delivery time is still ahead.
The revision preserves the template, sender, brand materials, audience query, tracking settings and quality policy used for that run. Editing shared materials afterward does not silently replace the version being prepared. Generated content goes through the required pilot and continuing quality checks; a failed check can hold the campaign before more messages are released. See Adaptyle for the distinction between a preview and campaign qualification.
Check the estimate
The composer's Estimate separates generation, possible corrections, pilot and continuing reviews, sending and campaign costs where applicable. Read the assumptions as well as the total. An unknown cost is not zero, and a duration without enough measured evidence is not a promised completion time. More recipients, richer context, different models and regeneration can change the usage.
Use a representative preview to inform the estimate. Keep exact prices, dates and eligibility rules in ordinary copy or Liquid when they must remain exact for everyone. See billing.
Cancel or stop a send
The sending banner on Metrics offers Cancel send before preparation starts. Cancellation clears that schedule and returns the broadcast to an editable state so you can revise and schedule again.
Once preparation has started, the action is Stop sending. It cancels remaining work; messages already being dispatched may still be delivered. A stopped campaign cannot be resumed. Check its Emails tab before planning a follow-up so you do not resend to people who already received it.
Stopping a send cannot recall an email or reverse rendering costs already incurred. Scheduled campaigns can begin preparing before their delivery time, so check the current banner rather than assuming the clock alone determines whether cancellation is still available.
Who actually receives it
The selection establishes who is in scope. Sending rules determine which messages may leave.
- Marketing requires a contact subscribed to email and, if the template names a communication topic, subscribed to that topic. The email includes the required unsubscribe behavior. Any applicable address suppression blocks marketing.
- Transactional does not require marketing subscriptions or a topic. Delivery-failure suppressions still block addresses that hard bounced or repeatedly soft bounced.
- Contacts without an address are excluded. Addresses are normalized and deduplicated within the broadcast, so two selected contacts sharing an address do not produce two messages to it.
Consent and suppression remain send-time controls. The frozen audience is not permission to ignore an unsubscribe that arrives while the campaign is preparing. See contacts and email types.
Watch it land
Emails is the recipient-level record. Use it to distinguish preparation, accepted sends, failures and cancellations, then open a message to inspect its activity. Sent means the email provider accepted the message; delivered is a later event. Neither confirms inbox placement or that a human read it.
Metrics summarizes the funnel and rates for the campaign: sent, delivered, opened, clicked and unsubscribed, alongside delivery and reputation signals. A send failure reason appears on the same tab. Investigate a small affected sample before deciding to send again.
| What interrupted the campaign | What it means for your next decision |
|---|---|
| Insufficient credits | Preparation or dispatch can wait for available credits. Review the wallet and usage; do not create a duplicate campaign just because progress paused. |
| Quality checks | Remaining messages may be held. Review the reason and correct the content, settings or qualification evidence. Quality recovery rechecks eligible unsent work; it does not recall sent messages. |
| Provider rejection or invalid recipient data | Inspect the affected email and its reason. A temporary, safely retryable provider rejection differs from a permanent rejection. |
| Unknown provider acceptance | The system avoids blindly sending the message again. Reconcile its delivery before arranging another send. |
| Stopped campaign | Remaining messages are cancelled. There is no general resume for a stopped send. |
A retry or recovery is not permission to repeat every recipient. Previously accepted messages and attempts whose acceptance is uncertain are protected from automatic redrive.
Related
- Send a broadcast: a practical review sequence.
- Sending to large audiences: selection, preparation and scale.
- Email editor: content and preview controls.
- Segments: reusable audience conditions.
- Broadcasts API reference: the public API contract.