WhatsApp campaign metrics that hold up

To measure a WhatsApp campaign, count delivered and read from WhatsApp's own receipts rather than from sends, treat the read rate as a floor, count reach as distinct people, and report timing at the median and 90th percentile. In groups, two blue ticks appear only once every member has read a message, so per-member detail comes from Message info.

A campaign report is only useful if its numbers survive a sceptical question. Several of the obvious WhatsApp metrics do not: they count the wrong thing, or they count the right thing twice. Here is how to report results that hold up.

What do WhatsApp's ticks actually count?

Sent is what left your side. Delivered and read are what the recipient's phone reported back. Reporting sends as if they were deliveries inflates every campaign. Read delivery and read counts from the receipts themselves, and keep failed sends visible rather than folding them into a total. In a group the ticks only describe everyone at once, so the per-member picture comes from the Message info screen, which lists who it was delivered to and who has read it.

Why is a WhatsApp read rate a floor?

In one-to-one chats, recipients can switch read receipts off in their privacy settings. WhatsApp's help centre says that switch doesn't apply to group chats, but even there, anyone who reads a message in a notification without opening the chat never registers as having read it, and a first message to someone may not send a read receipt back at all. A read rate is therefore the least that happened, and it should be labelled that way rather than compared with an email open rate that is measured differently. Who read your message in a WhatsApp group explains the ticks and the Message info screen behind it.

How should you count WhatsApp campaign reach?

The same person is often in three of your groups. Adding up group sizes counts them three times. Confirmed reach should be distinct people, deduplicated across every group and list the campaign touched — reported as "at least" a number, because it is built from receipts.

Split direct, group and channel

Direct messages, group posts and channel posts behave differently, and an average across them hides that. Report each surface separately so a strong direct campaign does not disguise a weak group one. For group campaigns, go one level further and report each group on its own: sending one message to many WhatsApp groups shows the per-group view.

Measure time, by percentile

How long messages took to be delivered and read matters as much as whether they were. Report time to deliver and time to read at the median and at the 75th and 90th percentiles. An average is dragged around by a few very late readers; percentiles show what most people experienced.

Export the raw material

Dashboards are for looking; exports are for arguing. WavesFlo offers eleven reports across delivery, audience, campaigns, compliance and operations, each as CSV and JSON, including one that lists recent sends the sending limits held back, each with the rule that held it. In the shared inbox, each message carries one of six delivery states rather than two ticks, from sending through played to failed.

Polls are the one place a group tells you what it thinks in numbers. WhatsApp group polls covers writing ones people answer. Comparing tools on reporting? WavesFlo vs Periskope sets out what each measures per group.

A reporting checklist

1. 1Report delivered and read from receipts, and show failures.
2. 2Label read rates as a floor.
3. 3Report reach as distinct people, deduplicated.
4. 4Split direct, group and channel.
5. 5Give timing at the median, 75th and 90th percentile.
6. 6Keep the exports with the report so anyone can check the numbers.

For group campaigns, pair this with per-group rates: the group marketing guide covers why.