WhatsApp campaign analytics

Read the available send outcomes and provider receipts before deciding what to change. Campaign counts describe observed messaging activity, not revenue, a completed purchase or proof that a particular message caused a reply.

WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.

What each reported number can and cannot tell you

Campaign summaries show sent and failed counts. Delivered and read counts depend on the corresponding recorded receipt timestamps; an absent read receipt is not proof that the person ignored the message. Exclusions are not successful sends.

The summary success rate is sent divided by sent plus failed, rounded to a percentage; it is not a delivery, read, reply or conversion rate. Queued values are an estimate from stored campaign totals and current send/failure counts, not a completed-send result.

Replies follow the seven-day attribution rule: the most recent qualifying campaign send before the inbound reply, with only the first previously unreplied recipient row credited. The timestamp/rule is an attribution convention, not causal proof or a verified sale.

A/B recipient assignment is stable and hash-based, not a fresh random draw on every retry. Current per-variant “sent” summaries count assigned recipient rows, not only confirmed sends; do not use those labels as validated delivery denominators or statistically significant winner claims.

Permission and the customer-service window

Obtain explicit permission for the WhatsApp messages the recipient expects and honor opt-outs. The customer-service window opens or resets with each user message and lasts 24 hours. Outside it, use an appropriate approved template; template approval does not replace consent or guarantee delivery.

Limits before enabling

No native message-link click, purchase revenue, ROI, statistical significance or automatic winner-selection claim. Provider receipts and incomplete retrieval can affect totals; reconcile the actual campaign records before external reporting.

Illustrative workflow review

  1. Campaign reviewer: Compare observed send/failure records with available delivery and read receipts.
  2. Outcome review: A reply count uses a fixed attribution rule; it does not prove a sale or a winning variant.

No native message-link click, purchase revenue, ROI, statistical significance or automatic winner-selection claim. Provider receipts and incomplete retrieval can affect totals; reconcile the actual campaign records before external reporting.

Setup

Define the task

Review sent, failed and excluded recipients separately.

Confirm inputs

Check receipt timestamps and the defined success-rate denominator.

Review the outcome

Interpret reply attribution and A/B counts conservatively before changing a campaign.

Questions

Is the displayed success rate a conversion rate?

No. The campaign summary uses sent / (sent + failed), rounded to a percentage. It is not a purchase, delivery, read or reply conversion rate.

What does the 24-hour window permit?

Obtain explicit permission for the WhatsApp messages the recipient expects and honor opt-outs. The customer-service window opens or resets with each user message and lasts 24 hours. Outside it, use an appropriate approved template; template approval does not replace consent or guarantee delivery.

Which Repli costs should we review?

WhatsApp CRM and Marketing start on Growth: US$12/month · ₹999/month in India. AI credit, purchased team seats and Meta/provider message charges are separate. Email and Store remain admin-only beta; Commerce is not a new purchasable plan.

Related guides

WhatsApp broadcast automation

WhatsApp audience segmentation

WhatsApp opt-in and consent records

WhatsApp CRM

Repli pricing

Official references

WhatsApp Business Platform pricing — Delivered-message billing depends on recipient market and category; consult the current rate card and account invoice.

Cloud API getting started — Account and number prerequisites; Meta controls availability and approval.

WhatsApp Business Messaging Policy — Consent, acceptable use and messaging restrictions still apply.