Building a campaign
Pick an audience
Select recipients by tag, by a recent CSV import, or by combining filters (e.g. tag =
vip AND region = IT).Choose a template
Only approved templates are selectable. Map each template variable to a contact field so the message personalizes per recipient.
Preview the audience
Before sending, review a sample of actual recipients to confirm variable mapping is pulling the right data.
Schedule the send
Send immediately or schedule for a future date/time, in UTC or the recipient’s local time zone (requires contact time-zone data).
Delivery and safety
Once launched, a campaign’s messages are queued and delivered through the same fan-out engine used by journeys and the transactional API. It respects your WhatsApp Business Account’s current messaging-tier rate limits automatically, so a large campaign won’t get your number throttled or flagged. Two safety mechanisms apply automatically to every campaign:- Deduplication — the same broadcast will not be sent to a contact twice within a 12-hour window, even if you accidentally launch it more than once.
- Opt-out enforcement — contacts who’ve replied
STOP(or a localized equivalent) to a previous marketing message are excluded from the audience automatically.
Category and cost
Because campaigns almost always useMARKETING-category templates, they’re billed at Meta’s highest per-conversation rate. Getting the category right — and understanding when Meta might silently re-categorize a template — directly affects what a campaign costs. See Marketing templates for the rate ordering across categories.
Monitoring a live campaign
Once a campaign is sending, the dashboard tracks delivery rate, read rate, click-through on buttons/links, and conversion against a goal you define. Settings → Usage rolls delivered-template spend and free service-window traffic up into per-campaign cost attribution across 7-day, 30-day, and month-to-date windows — see Meta Usage & Cost Monitor for how those estimates are built.Campaigns vs. Journeys
Campaigns are a one-shot, audience-wide send with a single template. If you need multi-step logic — wait, branch, react to a button click — that’s a Journey instead. Both draw from the same contact and template data, so segmenting an audience once with tags works for either.See also
- Broadcast Engine — the full campaign-creation and fan-out reference.
- Templates — approval and category rules for the message a campaign sends.
- Meta Usage & Cost Monitor — spend estimation model.
- Contacts — tags and segmentation used to build an audience.