Analytics | Developer Documentation

Investigate a difference between WhatsApp reports

Start with the exact totals that disagree and the systems that produced them. A CRM dashboard, webhook log, website report and billing record may count different things. This guide helps you reconcile their scope; it does not assume a universal ChatArchitect analytics endpoint or identical Meta and CRM totals.

Write down each report's definition

The campaign metrics guide maps customer tasks to available data sources. For a campaign, also use the measurement plan and template register so each report refers to the intended send.

Trace a small set of attempts

Choose identifiable attempts around the disputed period. Keep the business number, recipient, time and available message references together. Compare the sending history with the reported results and the recipient's actual conversation where a permitted test is appropriate.

Events already matched to one attempt describe its progress; they are not automatically additional messages. Check how your implementation treats repeated events and updates. Use the integration's documented correlation rules rather than assuming every identifier field is interchangeable. The API Quick Start provides the known sending and callback examples.

Check filters, missing stages, repeated attempts and export boundaries before expanding the investigation. Write down whether the difference is explained by a report definition, an identifiable attempt or an unresolved gap. Availability, timing and completeness of a particular report require confirmation with its owner.

Keep billing and business outcomes separate

A delivered or read message does not establish a sale, completed order or billable total. Compare actual charges with ChatArchitect billing records and the agreed plan terms. For an order or visit, use the system that records that action and its attribution rules.

For support, provide the report names, period, time zone, counting units, filters, redacted sample and available attempt references. This preparation does not promise direct Meta Ads, analytics exports, click events or a new dashboard through ChatArchitect.