Skip to main content

WhatsApp campaigns and analytics

WhatsApp Business separates one-shot Broadcasts from ongoing Campaigns, with audience in Contacts and performance in Analytics. Understanding each surface prevents duplicate sends and clarifies which metric to trust for leadership reporting.

Video

Video coming soon for this topic

Who can do this​

Marketing admins with WhatsApp Business permission.

Before you begin​

What you'll accomplish​

  • Broadcast or campaign executed
  • Analytics reviewed against send size
  • WA contact list reconciled with CRM

Step-by-step procedure​

Broadcasts vs Campaigns​

SurfacePathBest for
Broadcasts/whatsapp-business/broadcastsSingle template blast to a list
Campaigns/whatsapp-business/campaignsMulti-step or recurring WA programs

Run a broadcast (quick path)​

  1. Broadcasts → Create.
  2. Choose approved template + audience.
  3. Schedule or send; monitor delivery.

Run a campaign​

  1. Campaigns → Create.
  2. Configure steps, templates, and triggers per UI.
  3. Activate; monitor in Analytics.

Analytics & Contacts​

  1. Analytics (/whatsapp-business/analytics)—delivery, read, reply, failure breakdowns.
  2. Contacts (/whatsapp-business/contacts)—WA-specific audience; sync issues show here first.
  3. Export or screenshot for weekly marketing standups.
  4. Tie revenue outcomes to Reports — Messaging.

Extended guidance​

Executives often ask for read rate—pair Analytics with CRM outcome fields (replies tagged in Inbox). When Contacts counts diverge from Smart Lists, reconcile opt-outs and invalid numbers before blaming templates. Run broadcast post-mortems: template, audience, time window, failure codes.

Practice scenarios​

Compare one Broadcasts send vs one Campaigns program on the same cohort (different weeks)—document metric differences for leadership.

Sandbox validation​

Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.

Team rollout checklist​

Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.

Keep learning​

Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.

Verify your work​

  • Send count in Analytics matches intended audience (± blocks)
  • Failed rows investigated (invalid WA, template pause)
  • CRM contacts updated after replies

Tips​

tip

Compare Broadcasts for announcements vs Campaigns for drips—do not duplicate both for the same cohort same day.

Troubleshooting​

| Analytics empty | Send still processing; refresh | | High failure rate | Template paused by Meta; reapprove | | Contact not in list | Missing WA opt-in or wrong number format |

See also​