How to Read a WhatsApp Campaign Report: Delivery & Clicks
What do the sent, delivered and read statuses in a WhatsApp campaign report tell you, why do reads look incomplete, and how should you interpret clicks and replies? We explain, in plain language, what you need to know to read the numbers correctly and to export the results and carry them into your next campaign.
You sent the campaign, and now the dashboard is full of numbers: sent, delivered, read, clicked. Which one tells you what? A WhatsApp campaign report looks simple at first glance, but every status has its own meaning, and sometimes its own trap. Below we go through the statuses one by one, show how to calculate the rates, and explain what to do once you export the results.
Which message statuses appear in the report?
Every message you send through the WhatsApp Business API has its own ID. Meta reports the message's journey through status notifications, and the numbers in your campaign report come largely from those notifications. The four basic statuses are:
| Status | What it means | Watch out for |
|---|---|---|
| Sent | The message was accepted into Meta's system and is on its way. | It does not show that the message reached the person's phone. |
| Delivered | The message reached at least one of the person's devices. | It does not mean the person has seen the message. |
| Read | The person opened the chat and saw the message. | If the person has read receipts turned off, you may not receive this status. |
| Failed | The message could not be delivered. | Sometimes an error reason comes back, sometimes Meta does not share one. |
Meta's developer documentation is clear on this: the API accepting your request does not mean the message was delivered. Delivery and read information arrives later, separately. That is why it is more reliable to review the report after some time has passed, not five minutes after sending.
What if the same message shows as both delivered and failed?
It is rare, but it happens. According to Meta, if a person uses WhatsApp on more than one device, a message can reach one device and not the other. Any message that comes back as "Delivered" has genuinely reached at least one device.
Why does a message not move to "delivered"?
Messages stuck at Sent or dropping to Failed are what we get asked about most. In some cases Meta does not share the real reason, citing privacy and policy. The main causes listed in its documentation are:
- The person has not been online for a long time. Meta holds a message for offline people for 30 days; if they do not connect in that time, the message never reaches them.
- The person blocked your business number.
- The number is not registered on WhatsApp, the person has not accepted the current terms of use, or they are using a very old app version.
- The person stopped receiving marketing messages from your business.
- Meta did not deliver the message to "protect a healthy experience" because of the per-person marketing message limit it applies.
The last two points matter most. Sending again to someone who has stopped marketing messages does not work, and Meta also says not to retry these people. Removing them from the campaign list is the right way under Meta's rules and in terms of communication consent; we cover that topic separately in our guide to WhatsApp bulk messaging and KVKK (Turkey's personal data protection law).
Retrying lowers your rate. If a message hits the per-person marketing limit, do not resend it right away; Meta recommends waiting at least 24 hours. If you count retries in your delivery statistics, your delivery rate will look lower than it really is.
Why does the read rate look incomplete?
The Read status relies on a signal from the person's phone. Users can turn off read receipts in WhatsApp's privacy settings. In that case, even if they read your message, "read" may not show up in your report.
In short: the read count is not the exact number of real reads, it is a lower bound. If someone does not show as read but replied or tapped the link, you already know they saw the message. That is why we do not use reads alone as a measure of success.
Timing matters too. A delivered message can be read hours or even days later. A report you check an hour after sending will not look the same the next day.
What do clicks and replies show?
Delivery and reads tell you the message arrived. Clicks and replies tell you the person did something. These two are what really say whether the campaign worked.
Clicks
This shows the people who tapped the link or link button in the template. To see what those people did on your site, we recommend adding campaign parameters (such as UTM) to the link; that way traffic from WhatsApp shows up separately in your web analytics tool. The click count may not match the number of site visits exactly, because people who leave before the page loads still count as a click.
Replies
A reply is when the person responds by typing a message or tapping a quick reply button. A reply does two things: it measures interest, and it opens the 24-hour customer service window. Within this window you can continue the conversation without being tied to a template; the details are in our guide to the WhatsApp 24-hour rule.
But be careful. Replies such as "Stop" or "remove me from the list" also count toward the reply total. Before you celebrate the reply number, read what the replies actually say.
What should you base the rates on?
The denominator is the part of the report people misread most. If you calculate each rate against the right step, you can see where the loss happens:
- Delivery rate: delivered messages / messages you tried to send (excluding retries). It shows the quality of your list.
- Read rate: read / delivered. It relates to the message preview and the send time; it comes out low because of people who have read receipts turned off.
- Click rate: people who clicked / delivered. It shows the strength of your offer and button text.
- Reply rate: people who replied / delivered. It shows how well the message starts conversations.
The reason we use "delivered" as the denominator for clicks and replies, not "read", is simple. Read information comes in incomplete, so if you divide by reads, the rate comes out higher than it really is.
"What is a good rate?" There is no answer that fits everyone. Results vary a lot by industry, list and message type, and we do not know of a general benchmark figure backed by a reliable source. The most solid comparison is your own past campaigns: the same segment, a similar time, a similar offer.
We also suggest adding cost to the same table. The template messages you use in campaigns are charged by Meta according to category, and these charges change from time to time. You can find the current structure in our guide to Meta's charges. Tracking what you spend per click or per reply is a far more meaningful measure than the raw read count.
Let's read your report together. We can show you in a demo how to track campaign results message by message.
Book a free demoWhat should you do after exporting the results?
The report screen gives you the summary. The real work is in the per-contact list. When you bring the results into Excel, you can see the status of each number and set up the next campaign accordingly.
- Separate the failed numbers. Remove numbers that are not on WhatsApp or that fail every time; sending to the same number over and over muddies the report.
- Mark people who opted out. People who said "Stop" or turned off marketing messages should not enter a campaign list again.
- Keep the people who clicked but did not convert separate. For people who showed interest but did not buy, you can try a different message.
- Do not send the same message to people who did not engage. For people who received the message but never reacted, change the message, the time or the offer before you reach out again.
After a few campaigns you will have your own table. Findings like "the discount message sent on Tuesday evening got more replies than the one sent on Saturday morning" help you more than any average you hear from outside.
How do you track campaign results in Chatopya?
In Chatopya you see the results of your WhatsApp bulk messaging sends message by message: delivery, reads, replies and link clicks. You can export the results as Excel, split contacts into segments by tag, order history, interest or custom fields, and schedule the next send by time zone.
Consent records, opt-out requests and send history are also kept on record for the KVKK side. We work out the estimated campaign cost together with our team.
Frequently asked questions
What does it mean when a WhatsApp message is sent but not delivered?
The message reached Meta's system but has not yet arrived on the person's phone. The person may be offline, may have blocked your number, or the number may not be registered on WhatsApp; Meta does not always share the reason.
Can I see whether people with read receipts turned off read the message?
Generally no; for these people, "read" may not appear in your report. If the person replied or tapped the link, that tells you they saw the message.
When is a WhatsApp campaign report final?
Delivery and read information keeps arriving after the send; Meta holds a message for offline people for 30 days. Doing a first review after a few days, and using the same waiting period when you compare campaigns, gives more accurate results.
Should I resend failed messages?
It depends on the reason. Do not resend to someone who stopped marketing messages; for a message that hit the per-person limit, Meta recommends waiting at least 24 hours.
Can I export campaign results to Excel?
In Chatopya, yes, you can export campaign results as Excel. With this list you can clean out failed numbers and build a new segment of people who clicked.
Related articles
See your campaign results message by message
Track delivery, read, reply and click results for your bulk sends in Chatopya, export the results to Excel and plan your next campaign by segment.