# Insights

Track WhatsApp usage and costs for each client and phone number (channel) through the 360dialog Hub, the Partner API, or webhooks. Usage can be checked regardless of whether the account is on **Direct Payment** or **Partner Payment**. Final charges always come from Meta’s monthly invoice.

There are multiple ways to check it:&#x20;

* [View usage visually in the 360Dialog Hub](#view-usage-visually-in-the-360dialog-hub)
* [Get usage programmatically per channel via API](#get-usage-programmatically-per-channel-via-api)
* [Build your own counters from webhook events](#via-webhook)

{% hint style="warning" %}
Pricing is [message-based](https://docs.360dialog.com/partner/get-started/billing-and-invoicing-guide/conversations). All in-month usage data is an **estimate** and may slightly differ from the final invoice issued by Meta.
{% endhint %}

## View usage visually in the 360Dialog Hub

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

View your conversation history—including all Free and Paid conversations—to track volume over time. You can refine the data displayed by applying filters located in the top-right corner of the dashboard.

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FnlmQE4N2fIdrfqTkLbLW%2FScreenshot%202025-12-22%20at%2015.53.55.png?alt=media&#x26;token=7f908ca9-3d33-4a1a-959c-3d8601a48100" alt=""><figcaption></figcaption></figure>

The **Messages by Category** chart displays the total volume of messages sent during your selected timeframe, broken down into specific Meta categories such as *Utility, Marketing, Marketing Lite*, and *Service*. Complementing this, the **Messaging Costs** graph illustrates your cost breakdown over time, allowing you to track daily expenditure fluctuations and identify which categories are driving your messaging budget. You can use the dropdown menus and filters to refine these views for more granular reporting.

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2F1EiJlPM9K8XVyt0Xabyn%2FScreenshot%202025-12-22%20at%2015.54.19.png?alt=media&#x26;token=61207255-39c8-41b9-a683-854078086c2f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Please be aware that the Approximate Charges displayed in the 360Dialog Hub is financially binding in its totality. The precise amount due will be determined by Meta's invoice at the end of the month, which will serve as the authoritative record of charges.
{% endhint %}

The **Voice Calls** section provides a comprehensive overview of your call performance and usage metrics. At a glance, you can monitor high-level KPIs such as *Total Calls*, *Total Minutes*, *Average Duration*, and the associated *Total Cost* for the selected period. Each metric includes a comparison against the previous cycle to help you identify trends in call volume or expenditure. For a more detailed analysis, the Calls: *Inbound vs Outbound chart* tracks call direction over time, while the *Total Call Duration* graph visualizes fluctuations in minute usage across specific dates. These tools allow you to manage your voice operations effectively and ensure your communication strategy remains cost-efficient.

<figure><img src="https://2248475362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuyAl2S0lSHJaNDXJHo7A%2Fuploads%2FdyRAAlmAL4Raf9C1yNap%2Fimage.png?alt=media&#x26;token=e1736a33-953c-4ea1-9df1-0b4fc13239ca" alt=""><figcaption></figcaption></figure>

## Get usage programmatically per channel via API

Check the status and analysis of message usage separately using the following methods:

* [Get Channel Usage](#get-channel-usage)
* [Get Channel Balance](#get-channel-balance)
* [Get Client Balance](#get-client-balance)

#### Get Channel Usage

Retrieve channel-level pricing analytics for messages delivered within a specific date range. This [endpoint](https://docs.360dialog.com/partner/partner-api/api-reference/balance-and-usage#get-api-v2-partners-partner_id-clients-client_id-channels-channel_id-info-usage) is aligned with Meta’s pricing structure and provides granular breakdowns.

&#x20;**Overview:**

* Returns current pricing breakdowns for a specific phone number (channel) within a WABA for any messages delivered within a specified date range.
* Abstracts all Meta-specific complexity, so partners don’t need to implement or maintain their own integration with Meta’s pricing services.
* Allows partners to proactively monitor pricing without needing direct integration with Meta.
* Includes MM Lite messaging pricing and statistics

**Rate Limits:**

* 10 requests/hour per phone number (**channel**)
* 200 requests/hour per **WABA**

{% hint style="info" %}
This endpoint offers data directly from Meta. Slight discrepancies may occur with existing info/balance endpoints due to varying usage collection and processing schedules.
{% endhint %}

#### Get Channel Balance

Use this [endpoint](https://docs.360dialog.com/partner/partner-api/api-reference/balance-and-usage#get-api-v2-partners-partner_id-clients-client_id-channels-channel_id-info-balance) to retrieve **balance information only** for a specific channel. Usage metrics returned by this endpoint are deprecated and will no longer be returned.

#### Get Client Balance

{% hint style="warning" %}
**Soft Deprecation Notice:** Starting from **July 1, 2025**, the usage portion of this endpoint is **soft-deprecated**.

It previously returned client-level balance and usage data, but is now replaced by **Get Channel Balance** and **Get Channel Usage**.
{% endhint %}

This [endpoint](https://docs.360dialog.com/partner/partner-api/api-reference/balance-and-usage#get-api-v2-partners-partner_id-clients-client_id-info-balance) can be used.

\
**Rate Limits:**

* 5 requests per 30 seconds.

## Via Webhook

Webhook events include message-delivery information and conversation context. You can build counters to estimate usage in real time based on those objects.

## FAQ

#### 1. Why are usage numbers different from my invoice?

Usage data in the Hub and API is based on near-real-time processing. Meta’s invoices are finalized monthly and may include adjustments. Minor differences are expected.

#### 2. Does usage tracking work for both Partner and Direct payment accounts?

Yes. Usage tracking is available regardless of payment method. The only difference is who receives the invoice.

#### 3. What happened to the Get client balance endpoint?

It has been deprecated and will no longer return data after July 1, 2025. Use Get channel balance for balance data and Get channel usage for usage analytics.

#### 4. Can I still see usage per WABA or client?

Yes, but you’ll need to aggregate channel-level results from the Get channel usage endpoint across all channels within the WABA or client.

#### 5. What is the best endpoint to use for billing dashboards?

Always use Get channel usage for accurate and detailed analytics. Combine it with Get channel balance for funds tracking.

#### 6. Why are there different granularity options?

Granularity controls how data is grouped in time: use half\_hour for high-resolution analysis, daily for regular monitoring, and monthly for summaries.

#### 7. Are webhooks sufficient to calculate costs?

You can estimate usage from webhooks, but they are not authoritative. Always reconcile against Meta’s monthly invoice for final billing.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.360dialog.com/partner/partner-hub/checking-usage-and-statistics.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
