WhatsApp conversation analytics ends 1 November 2026: what to change

Meta's 27 October 2026 changelog deprecates the conversation_analytics field on the WhatsApp Business Account. The analytics guide, marked updated 27 October when checked on 31 October, says the field becomes unavailable beginning 1 November 2026. The change was announced before its effective date; this article does not claim the field had already stopped working on 31 October.

Conversation-based pricing was retired on 30 June 2025, but older reports or integrations can still request the conversation_analytics field. Search stored Graph API queries, dashboard jobs, exports and partner integrations for that exact field name. A failed or blank report after the removal date should not be interpreted as zero messages or zero charges.

Meta documents analytics for sent and delivered messaging activity, and pricing_analytics for the delivered-message pricing breakdown. Pricing analytics can group by country, phone number, pricing category, pricing type or tier, and can request cost or volume metrics. Query the relevant WhatsApp Business Account ID with a start, end and granularity. The field is already documented; Meta does not describe a new 1 November rollout for it.

Do not rename a conversation-count chart to message volume. One conversation and one delivered message are different units. Rebuild the report's denominator, labels and comparisons. Meta calls pricing analytics approximate, so reconcile financial totals to the billing record or invoice rather than treating an API chart as the final charge.

Inventory each scheduled query that contains conversation_analytics and record its owner, account ID, permissions, time range and downstream dashboard. Decide whether the report is about message activity, pricing volume or cost before rewriting it. Meta's pricing_analytics request requires a start and end Unix timestamp plus DAILY, HALF_HOUR or MONTHLY granularity; country, phone, category, type and tier are optional dimensions.

Reporting migration

Audit the old field, then compare evidence

Conversation counts and delivered-message pricing need different labels, units and checks.

01

Inventory

Find every scheduled query that requests conversation_analytics.

02

Select

Choose message activity or pricing metrics for each report.

03

Reconcile

Compare the new unit and approximate cost with billing evidence.

Run a limited read-only comparison using a known historical period. Check row counts, account scope, country, currency, time zone and category labels. Meta's guide limits pricing analytics to the associated Messaging account and describes approximate costs. It also says cost data is unavailable for Messaging accounts using a Solution Partner's credit line; ask the partner for the appropriate billing evidence in that case. Do not fabricate a cost from missing data.

The Meta analytics documentation describes an API reporting contract. It does not establish that a particular Whats91 customer dashboard uses conversation_analytics, that Whats91 has already changed a report, or that a customer's billing will change on 1 November. No Whats91 customer account, dashboard, query or invoice was inspected for this article.

Account owners should check their current Graph version, permissions, data availability and billing arrangement in their own environment. Preserve the last trustworthy historical export if a conversation-based comparison is still required. Treat a missing response, unavailable cost metric or changed unit as a review item rather than silently filling it with zero.