On this page

The Campaigns tab lets you launch a broadcast from wherever you are and watch it deliver, with the same delivery protection as the web. The form is deliberately compact: template, audience, sender, personalisation and optimised delivery. This guide walks through it and the report that follows.
Broadcasts on mobile: first 5 of 8 steps
- 1Open the Campaigns tab and tap New
- 2Enter a Campaign Name
- 3Under Template
- 4Under Audience
- 5Under Personalization
Before you start
- An approved template (created on the web).
- Segments or tags for the audience (created on the web).
- Your role must allow broadcasts (Admin or Owner, or a custom role with Broadcasts at full).
Steps
- Open the Campaigns tab and tap New broadcast.
- Enter a Campaign Name (for example "Holiday Promo").
- Under Template, search approved templates and pick one. Marketing, utility and authentication categories are shown; carousels with per-card variables and authentication templates are not offered for broadcasts.
- Under Audience, choose a segment or one or more tags. Recipients shows the deliverable count after suppression (opt-outs, blocked, invalid, US numbers for marketing).
- Under Personalization, confirm the variable mapping and fallbacks.
- Choose Send from if you have more than one number.
- Turn on Optimized delivery to send each contact at their best time within the allowed window, or leave it off to send now.
- Check Estimated cost, then tap Send Now.

Choosing the audience on the phone
Segments and tags are the two audience types the app offers, and both come from the web. A segment is a saved filter (for example, customers of a service who consented to marketing and were active in 90 days); tags are labels applied by flows, imports and agents. Pick one segment or one or more tags; the recipient count updates after suppression so the number you see is the number that will be sent. If the count is far below the segment size, the report's suppression reasons explain why, usually opt-outs and US numbers for a marketing template.
Optimized delivery and timing
With Optimized delivery on, each recipient is scheduled for the time they have historically read and replied fastest, within the allowed window and outside quiet hours, so a campaign started at lunch may deliver to some people that evening. Leave it off for time-sensitive offers. There is no date picker on the phone; scheduling for a specific future time is done from the web wizard, which also offers A/B tests and retargeting cohorts.
After sending
The report updates live: sent, delivered, read, replied, failed and held, with reasons per recipient. Replies attributed to the campaign open in the inbox with the campaign shown in the thread, so the follow-up happens where the customer is. Pause and resume are available while the campaign runs; cancel stops the remaining recipients and keeps the counts of what was already delivered.
What you will see
The broadcast appears in the Campaigns list with live counts: sent, delivered, read, replied, failed and held. Tap it for the report: per-recipient states with the reason for any failure or hold (Meta's error code in plain words), pause, resume and cancel actions, and the replies attributed to the campaign, which open in the inbox.
Delivery protection on mobile
Sends run on the server, not the phone, so closing the app changes nothing. Pacing (50 per second on a green number, less on yellow or red or coexistence), holds for 131049 and template pauses, and the daily messaging limit apply exactly as on the web. The broadcast stuck guide explains each held state.
Personalisation on the phone
The Personalization step shows each template variable with the contact field it maps to and the fallback used when the field is empty. Mappings are set on the template in the web builder and reused here, so a first-name variable already points to the contact's first name; you only need to check that the fallback reads naturally in the sentence. Media headers use the sample uploaded with the template unless the template mapping specifies a per-recipient document, which is a web-side setting. If a variable is unmapped, the form asks for a static value before Send Now becomes available, which prevents a broadcast going out with an empty gap in the text.
Costs and limits before you send
Estimated cost multiplies the deliverable recipients by Meta's rate for the template's category and each recipient's country, and counts utility recipients with an open window at zero. The daily marketing limit is checked too: if the audience is larger than the remaining allowance, the form tells you how many will go today and how many will be held for the next window. Sending anyway is allowed; the held recipients follow automatically without a second campaign.
Settings and options
| Field | What it does | Default |
|---|---|---|
| Campaign Name | Label in reports | Required |
| Template | Approved template to send | Required |
| Audience | Segment or tags | Required |
| Personalization | Variable mapping and fallbacks | From the template's mapping |
| Send from | Sender number | Default channel |
| Optimized delivery | Per-contact best time | Off |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| "No segments yet" or "No tags yet" | None created | Create them on the web under Contacts |
| Couldn't load templates | Connection or no approved templates | Tap Try again; check Templates on the web |
| Recipients far below the segment size | Suppression | See why a recipient was suppressed |
| Broadcast shows held recipients | Meta pacing, limits or 131049 | Normal; they resume automatically |
| Send Now is disabled | Role or missing field | Check the role and required fields |
The first broadcast guide covers the full web wizard including scheduling and A/B tests.