How to export analytics on the WhatsApp Business API
Your WhatsApp numbers generate a steady stream of data — messages sent, delivered and read, template performance, per-category message cost, and conversation volumes by day. This tutorial shows you exactly how to export that analytics data from your InfiQ dashboard into a clean CSV or scheduled report you can hand to finance, feed into a BI tool, or reconcile against your Meta billing. Every step below is written for the official WhatsApp Business API as it works today, including per-delivered-message billing by category. No code is required for the standard export; a short API method is included at the end for teams who want to automate it.
What you'll do
Open Analytics in InfiQ, set your date range and the number/WABA you want, pick the metrics (delivery, template performance, cost by category, agent activity), preview the table, then Export to CSV or XLSX — or schedule a recurring email export. Match your date range to Meta's IST reporting window so costs reconcile, and export by message category since WhatsApp now bills per delivered message, not per conversation.Before you start: what you can export and what it means
InfiQ surfaces the same underlying metrics Meta exposes for the WhatsApp Business API, organised so a marketer can read them without an engineer. Knowing what each column represents saves you from exporting the wrong report. The most requested exports fall into four groups, and you can combine them or pull them separately depending on who's asking for the data.
- Messaging & delivery: messages sent, delivered, read and failed, plus delivery rate and read rate by day, template or campaign.
- Cost by category: spend split into marketing, utility and authentication — this matters because since 1 July 2025 WhatsApp bills per delivered message by category, not per 24-hour conversation.
- Template performance: approvals, block rate, per-template delivery and read rates, and quality signals so you can spot a template dragging down your number's rating.
- Team & conversation activity: inbound conversations, first-response time and agent handling volumes if you run shared-inbox support on the number.
Step 1 — Open Analytics and choose the right scope
Sign in to your InfiQ dashboard and open the Analytics section from the left navigation. Before touching any filter, set the scope so the export only contains what you need. If you manage more than one number or more than one WhatsApp Business Account (WABA), the wrong scope is the single most common reason an export looks wrong later.
- Select the WABA and the specific phone number you want to report on — an all-numbers export mixes cost centres and is hard to reconcile.
- Confirm the timezone shown is IST (or your reporting timezone); Meta aggregates on UTC internally, so a mismatch shifts day boundaries.
- If you only need one campaign, jump to the Campaigns view instead and export from there for a tighter, pre-filtered dataset.
Step 2 — Set the date range and the metrics to include
Use the date-range picker to bound your export. Reports are almost always requested for a billing month, a campaign window or a quarter, so pick a preset (Last 7 days, This month, Last month) or a custom range. Then choose which metric groups to include. Exporting only the columns you'll actually use keeps the file readable and stops finance from asking what an unfamiliar column means.
- Match the date range to your billing cycle if the export is for cost reconciliation — align the last day to the same cutoff Meta uses so totals line up.
- Toggle on cost-by-category if the export is going to finance; toggle it off for a purely marketing delivery report.
- Add template or campaign as a breakdown dimension when you want per-template rows rather than a single daily rollup.
- Leave a wide range only when necessary — very long ranges produce large files that are slower to generate and harder to scan.
Step 3 — Preview, then export to CSV or XLSX
InfiQ renders the filtered data as an on-screen table before you download anything. Read the preview: check that the row count and the top-line totals look sane, that the date column runs end to end with no gaps, and that delivery and read numbers are plausible against what you expected from the campaign. Once the preview is right, use the Export button and choose your format. CSV is best for importing into a warehouse or BI tool; XLSX keeps formatting for a report you'll email as-is.
- Click Export and pick CSV for machine use or XLSX for a share-ready sheet.
- Open the file once to confirm the header row, timezone and currency (₹, ex-GST) are what you expect before forwarding it.
- For a repeatable report, use Schedule export to have InfiQ email the same CSV to a distribution list daily, weekly or monthly — no need to log in each time.
Step 4 — Reconcile the numbers and read them correctly
An export is only useful if you interpret it correctly. The biggest change to keep in mind is billing: WhatsApp moved off per-conversation pricing on 1 July 2025 and now charges per delivered message by category. The 24-hour service window still exists — free-form customer-care replies inside it aren't charged today, though this is free only until 30 September 2026, as service messages become chargeable from 1 October 2026 — but it is a service window, not a billing unit. So read your cost export by category and by delivered message, and treat the 24-hour window as the reason some service messages currently show zero cost rather than as a line item.
- Cross-check the total delivered-message count and category split against your Meta billing statement for the same window.
- Expect small timing differences at the edges of a month — a message sent at 23:59 IST may land in the next UTC day in Meta's own view.
- Use delivery and read rates, not just send counts, to judge campaign health; a high send count with a low delivery rate often signals a quality or opt-in problem.
Optional — automate the export with the API
If you want analytics flowing into a dashboard without anyone clicking Export, pull the same figures programmatically. This is the only part of the tutorial that needs a developer. Use your InfiQ API credentials to request the analytics endpoint for a given number and date range, then write the response into your own warehouse or BI job on a schedule. The API returns the same metric groups you see in the dashboard, so a report you validated by hand can be reproduced exactly in code.
- Generate an API key in Settings and keep it server-side — never expose it in client code.
- Request analytics for a specific WABA, phone number and date range, then map the category cost fields into your reporting schema.
- Schedule the job to match your dashboard refresh, and log the row counts so a silent gap in the data is easy to catch.