WhatsApp Studio

Understand WhatsApp metrics, budgets and delivery exceptions

Separate verified delivery, spending estimates, provider charges and attribution.

How to do it

  1. Open Analytics to filter the message-creation cohort by UTC dates, phone number, campaign and status. Inspect delivery, read, reply, opt-out and interactive-reply counts, agent outcomes, AI attempts and attributed original Orders.
  2. Use Analytics Builder for BU-timezone reporting, historical trends, saved analyses, source-level permissions, dimensions and drill-downs. WhatsApp messages, conversations, AI usage, consent, verified charges and attributed Orders are separate sources.
  3. Open Usage & billing to set reviewed rates and spending controls. Atomic reservations protect daily, monthly and campaign budgets during concurrent sends. Quiet hours and recipient caps apply to marketing.
  4. Import confirmed Meta statement lines with unique provider references, dates, categories, countries and currencies. Reimporting a line does not duplicate the charge. Delivery billing metadata alone is not a final monetary charge.
  5. Read the definitions: message cohorts show observed lifetime engagement; customers may disable read receipts; interactive replies are not arbitrary URL clicks; a SupaGent answer is not a confirmed AI resolution.
  6. Business pulse links delivery exceptions and overdue response SLAs back to Studio. Settings retains failed webhook jobs for retry. An Uncertain send requires checking Meta or waiting for its callback before sending a replacement.

Check your result

Estimated costs and verified actual charges remain separate. Attribution attaches to the original Order once; cancellations and returns do not retain attributed revenue.

Good to know

Revenue attribution uses the last eligible delivered WhatsApp touch in the configured window and does not prove causation. CSV export is capped at 10,000 messages per filtered request and requires the export permission. Missing provider or cost data is shown as pending, not fabricated.

Still need help?

Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.

Contact SupaChrome support