Read statistics
Know how many members received and read each message, per community, through the reach block of a delivery.
A few hours after a send, Groupilot measures its WhatsApp read receipts, community by community, and exposes them in the reach block of each delivery. Reference: Messages.
Where it is
GET /v1/jobs/{job_id}/deliveriesEach delivery (one per community) carries:
{
"id": "…",
"community_whatsapp_id": "1203630…@g.us",
"community_name": "Webinar Marie - 09/11",
"number": 1,
"status": "sent",
"state": "sent",
"sent_at": "2026-11-08T19:55:02+01:00",
"reach": {
"members_at_send": 412,
"delivered_count": 398,
"read_count": 301,
"read_rate": 73.1,
"measurement_status": "consolidated",
"measured_at": "2026-11-09T20:00:00+01:00"
}
}The same block comes back from the MCP tool list_job_deliveries.
Fields
| Field | Meaning |
|---|---|
members_at_send | Recipients at send time: members of the community minus the sending number |
delivered_count | Members whose phone received the message |
read_count | Members who opened it |
read_rate | read_count divided by members_at_send, in percent, one decimal |
measurement_status | pending (not measured yet), partial (measured, still moving), consolidated (final, measured again at +72 h), unknown (could not be measured in time) |
measured_at | Time of the last measurement |
Every field is null until the first measurement runs, a few hours after the send. Treat pending and partial figures as provisional.
How to read it
- It is a floor. Members who turned read receipts off count as delivered, not read. Groupilot never claims more than WhatsApp confirms.
- Compare messages of the same occurrence with each other rather than against an absolute target: the message sent at 19:55 with the mention of everyone is the one to watch.
members_at_sendis the real audience of that message, which can be smaller than the final size of the community for early messages.- Sequence messages are measured; one-off messages too when WhatsApp returns an id for them.
In the app
The Messages tab of an event shows the read rate next to each sent message once measured, with "measured on 48 of 52 sends" when some communities could not be measured. Aggregates only use consolidated measurements.