Conversation Analytics for the WhatsApp Business API
Conversation analytics is the practice of measuring how your business talks to customers on WhatsApp — how many messages you send and receive, which category each falls into, whether they were delivered and read, and what they cost. On the WhatsApp Business API, where you are billed per delivered template message by category, good analytics is the difference between a channel you can forecast and one that quietly drains budget. This page defines the term precisely, explains the metrics that matter, and flags the mistakes Indian businesses most often make when reading their WhatsApp numbers.
In one line
Conversation analytics reports your WhatsApp message volume, category mix (marketing/utility/authentication), delivery and read rates, and cost per delivered message — the data you need to forecast spend, spot deliverability problems, and prove ROI.What conversation analytics actually measures
At its core, conversation analytics turns raw WhatsApp message logs into decisions. A complete view covers four dimensions. First, volume: how many messages you sent and received over a period, broken down by day, campaign, or template. Second, category mix: the share of your traffic that is marketing, utility, or authentication — the split that drives most of your cost. Third, engagement and deliverability: sent, delivered, read, and failed rates, plus reasons for failure such as invalid numbers or users who have not opted in. Fourth, cost: what you spent, mapped back to category and campaign so you can see cost per delivered message and cost per outcome. Read together, these tell you not just how much you are messaging, but whether that messaging is landing and whether it is worth the spend.
- Volume: messages sent and received, by day, template, and campaign
- Category mix: marketing vs utility vs authentication share
- Deliverability: sent, delivered, read, and failed rates
- Cost: spend per category, per campaign, and per delivered message
Why category mix drives your bill
Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message, priced by category. Marketing messages carry the highest rate, utility messages a lower one, and authentication messages their own rate on Meta's India rate card. That makes category mix the single most important number in your analytics. Two businesses sending the same total volume can have very different bills purely because one leans on marketing broadcasts while the other is mostly order updates and OTPs. Conversation analytics that separates spend by category lets you see this clearly — and often reveals easy wins, such as reclassifying a message that qualifies as utility instead of paying the marketing rate for it. The 24-hour service window, where you can reply to a customer-initiated conversation, remains free and is a window for support, not a billing unit.
How it works in practice
Analytics data flows from the WhatsApp Business API itself. Every message carries a status lifecycle — accepted, sent, delivered, read, or failed — and each delivered template message is tagged with its billing category. A platform like InfiQ ingests these events, joins them to the template and campaign that produced them, applies Meta's live rate card, and presents the result as dashboards you can filter by date, template, or category. On top of the raw counts, the useful layer is derivation: delivery rate as delivered over sent, read rate as read over delivered, cost per delivered message, and blended cost per conversation started. Because InfiQ applies transparent ₹ pricing (ex-GST), the cost figures you see in analytics reconcile directly against your invoice rather than sitting in a separate silo.
Common mistakes when reading the numbers
The most frequent error is treating the 24-hour window as a billing unit and reasoning about cost per conversation — an outdated model that leads to wrong forecasts under per-message billing. Another is judging a campaign on send volume alone: a broadcast that sends 50,000 messages but is blocked or unread by a large share is expensive noise, not reach. Businesses also conflate categories, assuming all traffic is priced equally and being surprised when a marketing-heavy month costs far more than a utility-heavy one. Finally, quality is easy to ignore in a volume dashboard: a falling read rate or a rising block rate is an early warning that your template quality rating is slipping, which can eventually cap your messaging limits. Good conversation analytics surfaces these signals before they become problems.
- Reasoning about cost per conversation instead of per delivered message
- Celebrating send volume while ignoring delivery and read rates
- Assuming every category costs the same
- Missing quality-rating warning signs like rising block rates
Frequently asked questions
What is conversation analytics on WhatsApp?+
How does billing relate to conversation analytics now?+
Is the 24-hour window still relevant?+
Which metrics matter most?+
Why does category mix change my cost so much?+
Can conversation analytics help me forecast spend?+
What does a falling read rate signal?+
Does InfiQ provide conversation analytics?+
See your WhatsApp numbers clearly
Book a demo and an InfiQ specialist will walk you through conversation analytics on your own traffic — category mix, deliverability, and cost forecast, in ₹ per-message pricing.