Use the acceptance-time range.
WhatsApp outbound metrics follow messages accepted in the selected range. A receipt arriving later updates that cohort, so the most recent period remains provisional.
Track the messages.
Read the outcome.
Inspect delivery and failure patterns across WhatsApp traffic. Keep reads, replies and confirmed customer actions as separate measures.
See the pattern.
Inspect the cause.
Follow performance down to the message.
WhatsApp analytics
Delivery over time
26,917accepted97.6%delivery rate
73.9%
133 of 180 · 14:00–15:00 UTCof failures in this hour
order_update
By template
14:00–15:00 UTC| Template | Accepted | Failed | Share |
|---|---|---|---|
| 1,101 | 133 | 73.9% | |
| 601 | 32 | 17.8% | |
| 300 | 15 | 8.3% |
Follow the cohort.
Allow for late receipts.
Understand outbound delivery and incoming conversation activity.
Investigate the recorded failure.
Inspect the message log for a failed template, expired service window or provider response. A chart locates a problem; the message record provides the specific evidence.
Avoid treating observations as a funnel.
A read receipt can exist without a delivered receipt. Group observations count messages rather than every recipient. Join confirmed business actions separately when measuring campaign value.
Scale without
losing control.
Organize teams in workspaces, control API access, and trace changes through audit logs.
HarborOrganizationWorkspacesProductionSandbox
Delivery agent
API key · Customer operations teamALAlex Lee AdminPermissions updated
Audit log
Production- Workspace
- Production
- Resource
- Delivery agent
- Read accessRead & write
Team Customer operationsActor role AdminOutcome SucceededTime 22 Sep, 09:42:18 UTC
Succeeded