WhatsApp Cloud API Analytics: How to Get Message, Cost and Template Data

To get WhatsApp analytics from the Cloud API, send a GET to your WhatsApp Business account ID with one of Meta’s analytics fields: analytics for messages sent and delivered, or pricing_analytics for message volumes and costs. Template performance has its own path, /<WABA_ID>/template_analytics, for each template’s sent, delivered, read and click counts. All of them use the same access token you send messages with.

This guide shows which field answers which question, the request format with working examples, the limits that trip people up (a 1-year lookback, a 7-day window for reads and clicks, data in UTC), and what to move to now that conversation_analytics is gone from 1 November 2026.

Which analytics field answers which question

Meta’s analytics live on the WhatsApp Business account, which Meta now calls the Messaging account (the ID didn’t change). Pick the field by the question you’re asking. The first group are fields you request with ?fields=; template and group analytics are separate paths under the WABA ID, such as GET /<WABA_ID>/template_analytics.

If you only need a quick look, the same kind of data is in Insights in WhatsApp Manager, with no code. The API is for pulling numbers into your own dashboards, finance sheets or alerts.

How the request works

Most fields use Graph API field expansion: you ask for the field on your WABA ID and chain filters onto it with dots. Times are UNIX timestamps in seconds.

That example asks for daily sent and delivered counts for October 2026 (1 October to 1 November, UTC) across every number on the account. The response holds an analytics object with data_points, each with start, end, sent and delivered.

• Filter by number with .phone_numbers(["919800000000"]). Leave it out to include every business number on the account.
• Filter by country with .country_codes(["IN","AE"]), using 2-letter codes.
• Split by message kind with .product_types([0,2]): 0 is template messages, 2 is non-template messages, and 100 is messages customers sent you.

Costs and volumes with pricing_analytics

This is the field finance teams want. It reports messages delivered in the date range, with VOLUME (how many) and COST (approximate charges in your Messaging account’s currency). A monthly breakdown by category for Indian numbers looks like this:

Two details matter since Meta’s pricing changes of 1 October 2026. SERVICE now means 1:1 non-template messages, and FREE_CUSTOMER_SERVICE means those delivered within the number’s free tier of 1,000 service messages a month. REGULAR also includes utility messages sent inside a customer service window and service messages beyond the free tier. Which messages are free is explained in is the WhatsApp API free?.

Volume tiers

Add TIER, PRICING_CATEGORY and COUNTRY to dimensions and data points affected by volume pricing get a tier such as 0:750000. The number after the colon is the top of your current tier for that country and category; subtract volume from it to see how far you are from the next one. Tiers apply only to utility and authentication templates. Marketing shows 0:MAX, and free messages have no tier.

Template analytics: reads, clicks and cost per template

Template analytics tell you how each template performs: SENT, DELIVERED, READ, CLICKED and COST. Before you can read them, you confirm template analytics on the Messaging account, in WhatsApp Manager or with one call:

• Up to 10 template IDs per request, daily data only, and a 90-day lookback.
• Reads and clicks are tracked for only 7 days from the day a message is sent. Meta says the read and click counts for those messages then reset to zero, and no further updates are recorded, so save them before then.
• Clicks cover URL buttons and quick-reply buttons, and only for marketing and utility templates. unique_url_button counts distinct WhatsApp accounts that clicked.
• Cost comes back as amount_spent, cost_per_delivered and, if the template has a URL button, cost_per_url_button_click.
• Not available for accounts owned by or shared with businesses in the EU or Japan, or with numbers using those countries’ calling codes.
• Turn off click tracking for one template with POST /<TEMPLATE_ID>?cta_url_link_tracking_opted_out=true&category=<CURRENT_CATEGORY>. Send its current category: a different one sends the template back to review.

Template data is in UTC by default, and a start or end that isn’t midnight UTC is moved back to midnight. Add use_waba_timezone=true to get days in your account’s time zone; start and end must then be dates such as 2026-10-31. Tips for better templates are in WhatsApp template messages.

Moving off conversation_analytics

Meta ended conversation-based pricing on 30 June 2025 and charges per delivered message instead. The old conversation_analytics field, which counted conversations, is no longer available from 1 November 2026. If a dashboard or script still calls it, it’s broken now.

Don’t try to compare old conversation counts with new message volumes in one chart; they measure different things. Start a new series from July 2025, when per-message pricing began.

Limits and gotchas

• Lookback: since 1 December 2025, messaging and pricing analytics go back 1 year (it used to be 10 years). Template and template group analytics stay at 90 days, and group analytics need a start within the last 90 days. Save monthly snapshots if you want longer history.
• Approximate: Meta says analytics may differ from invoices because of small variations in processing. Reconcile spend against your invoice or your provider’s statement.
• Only what’s there now: responses include only the numbers and templates linked to the Messaging account at the time of the request. Deleted templates and moved numbers drop out.
• Several Messaging accounts on one number: under Meta’s new account model, a message counts in the analytics of the Messaging account it was sent from. If your token can send for more than one, the messaging_account_id on each send decides which one.
• Access: you need a token with access to that Messaging account, the same kind you send messages with. See finding your WABA ID if you’re not sure which ID to call.

A simple reporting setup

For most teams, three scheduled calls cover it:

1. Daily, 02:00 UTC: pricing_analytics for yesterday with dimensions(["COUNTRY","PRICING_CATEGORY","PRICING_TYPE"]), saved to your database. This is your spend trend.
2. Daily: template_analytics for templates sent in the last 7 days, so reads and clicks are saved before Meta resets them to zero after 7 days.
3. Monthly: pricing_analytics with MONTHLY granularity, compared with the invoice. Flag any gap larger than you’d expect from rounding.

Delivery problems for single messages don’t belong here: they come through the status webhook as they happen. See WhatsApp Cloud API webhooks for statuses and WhatsApp API error codes for failures.

Analytics in Automate AI, without the API

If you send through Automate AI, each campaign already shows who it was sent to, delivered to, read, replied, failed or clicked, so you don’t need Meta’s analytics fields for that. What each tab means is in WhatsApp campaign delivery reports.