Checking usage and statistics

Businesses using the WhatsApp Business Platform are charged per conversation, which includes all messages delivered in a 24 hour session with a particular WhatsApp user.

Through the Monthly usage data, you get to see the number of conversations the phone number had and when; it includes All, Free, and Paid Conversations.

This information is an estimate and can slightly differ from invoices. It can be checked in the 360 Hub (by Partners and Clients), in the Meta Business Manager (by Clients only), via Partner API (by Partners only, which can be used to create personalized dashboards for their clients) and via Webhook notifications (which requires development of an additional counter).

Please note that final information about charges in only available in the invoices sent after the month has ended.

In the 360 Hub

Clients and Partners can see a specific WABA usage in the Insights dashboard. To access it, click in Show details in the specific WABA you wish to use and select Insights on the top menu.

Through the Monthly usage graphs, you get to see the number of conversations the phone number had and when; it includes All, Free, and Paid Conversations.

Here, you can also estimate costs for the future through the Approximate charges graph, which shows the estimation of the costs of charges.

If the client is registered under Direct Payment, you will also be able to see their balance settings in this same page.

In the Partner API

If your clients are registered with direct payment, you can use the check balance endpoint to get usage information.

Please see how to use this here.

In the Meta Business Manager

Clients registered with Embedded Signup can see their conversation estimated insights directly in their Business Manager.

You can see more information about this feature here.

Via Webhook

Every time a message is sent, you can see the conversation information in the webhook. You can build a counter to understand usage and statistics based on this objects.

Please see how this is presented in this specific documentation.