Reconciling your WhatsApp bill with the Beacon Messenger log
Meta retired conversation analytics on 1 November 2026. How to match the pricing analytics and your invoice to the per-message log in Beacon Messenger.
On 1 November 2026 Meta switched off the conversation analytics report in WhatsApp Manager and the API field behind it. Since the move to per-message pricing, conversations have not been the thing you are billed for, so the old report increasingly showed numbers that did not relate to the invoice. Its replacement is pricing analytics: a breakdown of delivered messages by pricing category, which is what the invoice is actually built from. If you have been reconciling a Shopify store's WhatsApp spend against the conversation chart, that chart is gone, and this is a good moment to set up a reconciliation that works.
This post walks through matching three things: the Meta invoice, the pricing analytics in WhatsApp Manager, and the message log in Beacon Messenger. They count different events, so they will never be identical. The point is knowing exactly why they differ, so a real problem stands out from an expected gap.
Three counters, three different events
Meta bills per message, and the billable event is delivery. A template that is accepted but never delivered, because the phone is off for a week or the number is not on WhatsApp, costs nothing. Pricing analytics counts those delivered messages and sorts them into categories: marketing, utility, authentication and service. The invoice is the delivered count in each category multiplied by the rate for your market, less whatever free allowances applied. The current rates and the free entry point rules are on Meta's pricing page, and the October 2026 changes to utility and service pricing are covered in our earlier post.
Beacon Messenger counts something else. Every automation run writes one row to the message log with a status. Sent means Meta accepted the message; delivered and read are later updates from Meta's status webhooks; failed means Meta rejected it or could not deliver it; skipped means the app decided not to send at all, because the order had no phone number, consent was missing, or the monthly cap was reached. The plan cap counts sent messages: 50 on Free, 500 on Starter, 2,500 on Growth and 10,000 on Pro, and a message over the cap is skipped and logged rather than sent. The dashboard post explains the four home page numbers in detail.
So the app's sent count is an upper bound on what Meta can bill for that app's traffic, the delivered count is the number that should resemble the invoice, and skipped and failed should appear on the invoice as nothing at all.
| Counter | Counts | Moment it increments | Appears on the Meta invoice? |
|---|---|---|---|
| Beacon: sent | Messages Meta accepted | At send time | Only if later delivered |
| Beacon: delivered or read | Messages Meta confirmed on the phone | When the status webhook arrives | Yes, once each |
| Beacon: failed | Rejected or undeliverable | At send or on the failure webhook | No |
| Beacon: skipped | Never sent | At automation time | No |
| Meta: pricing analytics | Delivered messages by category | Delivery, Meta's clock | This is the invoice's source |
Doing the reconciliation
- Pick the invoice period. Meta invoices by calendar month in the business account's time zone. Note that time zone; the Beacon log shows times in your Shopify store's time zone, and a message sent at 23:50 on the last day of the month can be delivered in the next period on Meta's clock.
- In WhatsApp Manager, open Insights and the pricing analytics view for the same period. Write down the delivered count per category. For a store that sends order notifications only, almost everything will be utility, with marketing for any promotional templates and nothing in authentication or service.
- In Beacon Messenger, open the message log and filter to the same dates. Count rows with status delivered or read. Those are the messages that should match the utility and marketing lines, depending on each template's category.
- Compare per category. The app's templates carry the category Meta assigned when the template was approved, so group the log rows by template and map each template to its category.
- Investigate differences in the order given in the next section. Most reconciliations come out to a handful of messages apart, and every one of them has a mundane explanation.
Why the numbers differ, in the usual order
- Late delivery. A message sent on the 31st and delivered on the 1st is in the next month's analytics and invoice but in this month's Beacon log. The reverse happens at the start of the period. Look at the last and first days.
- Other senders on the same number. Pricing analytics counts every message delivered from the phone number, whatever sent it. If an agent replied from the WhatsApp Business app, a chat tool, or a test from the Meta API explorer, those are on the invoice and not in the Beacon log, which only records what the app itself sent.
- Free entry point conversations. A customer who reaches you from a click-to-WhatsApp ad or a Facebook Page call-to-action gets a window in which messages are free. They are delivered, so they appear in Beacon as delivered and in pricing analytics as delivered, but the invoice line for them is zero. Meta's analytics show these separately.
- Status webhooks that never arrived. If the app's webhook endpoint was unreachable for a while, deliveries during that time were never recorded, and the rows stay at sent. Meta still billed them. A cluster of sent rows with no later status on a single day usually means this.
- Failed after acceptance. A message can be accepted and then fail, for instance when the number turns out not to be on WhatsApp. Beacon records it as failed; Meta does not bill it. If you compared sent rather than delivered, these inflate the app side.
- Category changes. Meta can recategorise a template, typically from utility to marketing, and the new category applies from that moment. A template that was utility for the first half of the month and marketing for the second shows up on two lines in pricing analytics and one group in the log.
What Beacon Messenger does not do, and why
The app does not read Meta's analytics APIs, and it does not store the pricing information that Meta includes in each status webhook. That is deliberate. Meta's own analytics are the source of truth for what you are charged, and a second copy of that data inside the app would drift from the first whenever Meta corrected a rate or reclassified a template, which happens several times a year. The app's job is to tell you, per order and per message, what it tried to send and what happened, with the Shopify order number attached. The invoice tells you what that cost. The reconciliation is where the two meet, and it is better done once a month against the real numbers than approximated inside the app.
What the app does guarantee is the boundary. Nothing it skips can reach the invoice, nothing it sends is hidden from the log, and the monthly cap is a hard stop on the Beacon side, so a runaway automation cannot produce a surprise on the Meta side either. If you are sizing plans for the season, the Black Friday volume post does that arithmetic.
A monthly routine that takes ten minutes
- On the second or third of the month, when late deliveries have settled, export pricing analytics for the previous month.
- Count delivered and read rows in the Beacon log for the same month, grouped by template.
- Subtract messages from other senders on the number, then compare per category. Expect to be within a few messages.
- File the two numbers together. When Meta changes a rate or a category, as it did in October, you will have a clean baseline to compare against.
If the reconciliation turns up messages the app sent that you did not expect, the per-order log is the place to find out which automation and which order produced them. Beacon Messenger is free to install, and the message log is included on every plan.
Frequently asked questions
Why does Beacon Messenger's sent count not match my Meta invoice?
Because they count different events. Sent means Meta accepted the message; the invoice counts messages that were delivered. Compare the app's delivered and read rows to the invoice instead, and expect small differences from late deliveries at the month boundary and from messages sent to the same number by other tools.
Where do I see WhatsApp message costs now that conversation analytics is gone?
In WhatsApp Manager under Insights, in the pricing analytics view, which lists delivered messages by pricing category for a period. The same data is available through the WhatsApp Business Management API. Conversation analytics was retired on 1 November 2026 because billing has been per message rather than per conversation since 2025.
Does Beacon Messenger show me what each message cost?
No. It records what it sent, to which order, and what status Meta reported, but it does not copy Meta's pricing data or read Meta's analytics. Costs come from WhatsApp Manager, where rates and categories are kept current. Use the log to explain the invoice, not to replace it.
Are skipped and failed messages billed by Meta?
Skipped messages never left the app, so they cannot be billed. Failed messages were rejected or could not be delivered, and Meta bills on delivery, so they are not billed either. Only messages that reached the phone, shown as delivered or read in the log, appear on the invoice.
More guides
- WhatsApp Business app drops order tools: move orders to Shopify
- A customer replied STOP to a WhatsApp order message. Now what?
- WhatsApp marketing templates leave the Cloud API in October 2027
- WABA to Messaging Account: what changes for Shopify WhatsApp
- Order paid later, refunded or edited: which WhatsApp messages send
- Edited your WhatsApp automation? What queued messages send
- How to add a WhatsApp chat button to your Shopify store (2026)
- How to send Shopify order confirmations and shipping updates over WhatsApp with the official Cloud API
- Cash on delivery on Shopify: confirm orders over WhatsApp before you ship
- Recovering abandoned checkouts on Shopify with WhatsApp, the compliant way
- Why WhatsApp apps get your number banned: linked device vs API
- How a "free" WhatsApp app for Shopify ends up charging you
- Por qué una app de WhatsApp "gratis" para Shopify te cobra
- Pushdaddy or SuperLemon alternative: WhatsApp apps compared
- How to verify Shopify WhatsApp notifications were delivered
- Chat button still on your store after uninstalling the app?
- WhatsApp API pricing changes on Oct 1, 2026: Shopify impact
- Setting up the WhatsApp Cloud API with Meta's MCP and an AI agent
- WhatsApp chat outside business hours: what shoppers should see
- WhatsApp product sharing on Shopify: tracking dark social
- WhatsApp template rejected? Fixing Shopify order templates
- One WhatsApp number or two? Shopify notifications & support
- Shopify Canvas and Beacon Messenger: what works today
- Shopify now collects WhatsApp marketing consent at checkout. Here is what it changes
- Split shipments on Shopify: how many WhatsApp updates to send
- WhatsApp's 250-a-day messaging limit and your Shopify store
- WhatsApp, SMS or email for Shopify order notifications?
- WhatsApp is down: what happens to your Shopify order notifications
- Shopify orders with no phone number: why WhatsApp messages get skipped
- Shopify rollout discounts and WhatsApp order messages
- Add a Track order button to WhatsApp order messages
- Which Shopify orders trigger a WhatsApp message?
- The abandoned checkout timer restarts every time the shopper comes back
- Blank names, twelve-item orders: what WhatsApp merge fields fall back to
- Who looked at your customers' phone numbers? The access log behind a WhatsApp app
- Send a WhatsApp test message before your first order: what the Connect and Test buttons check
- Disconnect, update credentials, app secret: what each does
- COD reply not tagged: how Beacon Messenger matches replies
- WhatsApp template language: why name alone is not enough
- Finding one WhatsApp message in the Beacon Messenger log
- WhatsApp automation is On but nothing sends: a checklist
- Mapping WhatsApp template variables to Shopify order fields
- Every WhatsApp chat button setting in the Shopify theme editor
- WhatsApp template examples for Shopify: order, shipping, COD, cart
- The Share on WhatsApp block, setting by setting
- WhatsApp order messages when customers speak several languages
- Reading the Beacon Messenger dashboard: sent, delivered, failed, skipped
- Shopify batch fulfilment: what happens to 250 WhatsApp shipping messages
- WhatsApp template status: approved, pending, paused, disabled, and what sends
- WhatsApp quality rating: the field on the Connected number card
- COD returns (RTO) on Shopify: confirm orders on WhatsApp first
- WhatsApp error codes on failed messages: a reference
- WhatsApp display name: what customers see on your order messages
- Shopify Messaging WhatsApp automations vs Beacon Messenger
- OXXO, bank transfer and pay-later orders: when the WhatsApp confirmation goes out
- How many WhatsApp messages will Black Friday send? Sizing your plan
- WhatsApp usernames and BSUIDs: what changes for Shopify order messages
- Track with Shop vs WhatsApp shipping updates on Shopify
- Meta changed my WhatsApp template from utility to marketing
- Shopify's new app security review: what Beacon Messenger can access
- A shopper cancels their own Shopify order: what WhatsApp sends
- Customer erasure in 5 days: what the WhatsApp log keeps
- WhatsApp INR billing deadline: Indian Shopify stores
- WhatsApp template headers: text, image or document?
- Gift orders on WhatsApp: buyer's phone or the recipient's?
- WhatsApp order messages at night: when each one sends
- Downgrading a WhatsApp app plan after peak season: what changes
- Shopify subscription renewals and WhatsApp order messages