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 example, a coffee shop can announce a new roast to customers who recently bought coffee. The audience rule decides which customers qualify; the email can use each customer's purchase history to explain the offer. You choose one send time for that campaign.

Start with Send a broadcast for a walkthrough. You need a contact schema with customer records, a verified sender, and the appropriate email consent.

Decide who it is for

Choose New broadcast and select the Contact schema. Choose a saved segment to narrow the audience, use New segment to define one, or deliberately select All contacts in this schema. A segment must belong to that schema. The audience page keeps the chosen schema read-only after creation.

Choose Next, select an editor and sending mode, then Next to create the campaign and open Composer. Give it a recognizable name and description in the header, such as “New roast — recent customers”.

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.

After the first choice, the full navigation includes Audience, Composer, Schedule, Emails, Quality review 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.

Check the date and time displayed in the app before confirming. The schedule is one campaign dispatch time; it does not create a separate send time for each recipient’s time zone.

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.

Review a quality hold

A quality hold protects the remaining audience while a generated email needs attention. Open Quality review to see rejected Pilot review and Ongoing review results for the current campaign revision. Use Refresh reviews to reload the list and the paging controls to inspect other reviews. Critical failure, Human review needed and Human approved distinguish the available action and any recorded human decision.

1. Choose Review email on the rejection.
2. Read the judge’s concern beside the exact rendered message. Open Email text, Source information and authored instructions, and Approved reference before personalization to check what the message was allowed to say.
3. If a noncritical concern is mistaken, explain why this exact email is acceptable, confirm that you personally reviewed it, and choose Approve this reviewed email. This requires a signed-in account with editing access and a reason of 10–4,000 characters.
4. Read the result. Approval may clear that hold, but other reviews, failures or campaign checks can still prevent sending.

Approval applies only to the reviewed email and judgment in the active revision. It does not approve every future generation. Critical grounding, safety, privacy and consent failures cannot be approved here; correct the campaign for a new reviewed send. If the review is stale, reload it. A stopped or completed campaign and an email already attempted cannot receive a new approval through this action.

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.

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 channel-wide suppression blocks marketing, and a topic opt-out also blocks that address for the selected topic.
• 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. An individual email’s Sent status means provider acceptance; Delivered is a later event. Neither confirms inbox placement or that a human read it.

Metrics summarizes the campaign’s linked email records and event counts: Sent, Delivered, Opened, Clicked and Unsubscribed. Its funnel’s Sent total includes email records still pending or marked rejected/failed; it is not a count of confirmed provider acceptances. Opened and Clicked each count emails with at least one recorded event. Rates use different denominators: the Messages clicked card shows click-to-open, while the workspace overview shows click rate. Use report definitions for the formulas. A send failure reason appears on the same tab. Investigate a small affected sample before deciding to send again.

Retry eligible failed recipients

A finished campaign can still have remaining work. In Metrics, the banner shows the remaining-recipient count. When eligible failed rows exist, a member with Write permission sees Retry with the number of eligible recipients. Confirm Retry recipients to queue those rows, then watch Emails and Metrics again.

This retries failed rows in the active revision that have no attempted send or confirmed provider message. It does not repeat sent or unconfirmed messages, cancelled rows, or recipients already excluded during preparation. Rows with an existing rendered email return to dispatch; rows without one return to preparation. Quality, consent, suppression and capacity checks still apply. The count queued can change if another action changed the campaign while you reviewed it.

Choose Close remaining work when you intend to end that unfinished work instead. This closes the remaining send permanently while preserving sent messages and their delivery records. A stopped campaign cannot use the retry action. Duplicating a campaign creates a new delivery intent rather than retrying only the remaining rows.

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.

Read an individual email’s status

A status summarizes the current recorded outcome. Open the email’s Activity for its history; the status is not a mutually exclusive event bucket or simply the latest event. Rejection and sending errors take priority, followed by bounce, complaint, click, open, delay, delivery and sent evidence. A delayed email can therefore still have delivery activity in its history.

A row showing Sent · details removed, Failed · details removed or Cancelled · details removed preserves an outcome after its private details were removed. It does not offer the former message to inspect. The absence of details is not a reason to send it again.

Reuse or remove a campaign

Use the row menu on Broadcasts to Duplicate a campaign. The copy keeps its audience configuration and email content but starts unscheduled, with new sending history. Rename it and review the current audience, dates, links and sample before sending. Duplication does not exclude people who received the original.

Delete removes the campaign’s configuration, recipient-run associations and campaign reporting. Sent emails and their delivery history are retained. Deletion is permanent and cannot recall messages.

The server refuses deletion while the campaign is actively sending or its current work is still held by a worker. Cancel or stop the send and wait for it to settle first. After confirmation, Deletion queued means cleanup was accepted, not completed. Deletion is waiting means unresolved work still needs reconciliation. The workspace remains closed to ordinary runtime work during cleanup; follow the displayed message until deletion completes before starting another operation.

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.