[WhatsApp](/products/whatsapp)

# See what happened. Know what to improve.

Follow message delivery, customer response and the outcome your business cares about. Bring campaigns and service conversations into a measurement model that keeps the meaning of each event clear.

[Start your first exchange](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fwhatsapp%2Fonboarding)

[Read the analytics guide](/docs/guides/whatsapp/tracking-and-metrics)

## Set up with your agent

[Read the agent setup guide](/docs/ai/set-up-your-agent)

Copy this prompt into your coding agent:

```text
Bird connects customer communications, data and automation. Help me build with Bird using my coding agent.
1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available.
2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup.
3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step.

First task: Inspect WhatsApp message records and metric definitions. Separate acceptance, delivery, read receipts, replies, customer outcomes and billing; do not treat a read as a conversion or a missing cost as free.

Use this Bird page as the starting context: https://bird.com/products/whatsapp/analytics
Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links.
```

From messaging signals to business results

Conversation activity

Scope

Outbound message cohort

Observations

Delivery, reads and replies

Example data

Sample activity for an example conversation report.

Original source

Campaign or conversation identity.

Customer action

Relevant reply or destination activity.

Business event

Confirmed order, booking or resolved case.

Reconcile the result

Keep unknown observations, refunds and duplicate events visible in the measurement model.

Example report with sample activity.

## Read each signal for what it tells you.

Separate API admission, Meta acceptance, delivery, reads and incoming replies. Inspect the cohort and reporting window before comparing a campaign or service team.

## Keep unknown visible

A missing callback or pending observation is different from a confirmed failure. Reconcile with message records when investigating a gap.

## Use the right denominator

Inbound and outbound activity, group messages and recipient counts are different measures. Compare like-for-like populations.

## Connect messaging to the system of record.

Use a durable campaign, conversation or lead identity to associate the interaction with an actual order, booking or resolved case.

## Capture the source

Retain the original acquisition context when it is available. Keep an ad referral separate from a website UTM and an internal campaign identifier.

## Track the complete outcome

Include cancellations, refunds and unresolved cases where they change business value. Avoid reporting a click or read as revenue.

**Message signals and the business result Example**

| Observation | What it tells you |
| --- | --- |
| Delivered | The provider reported delivery |
| Read | A read receipt was observed |
| Replied | The customer sent a message |

Order #4821

Confirmed by your store

Join the conversation to the actual order before measuring its value.

## Make the next action easier to choose.

Reconcile the Bird send charge and applicable Meta fee against billing records. Use message cost projections for investigation while keeping the billing ledger authoritative.

## Include the correct Meta event

Applicable Meta fees can be recorded from delivered or read callbacks. Do not assume only the delivered event can carry the charge.

## Find what needs attention

Review failed actions, slow replies, template feedback and the journey step where customers stop. Assign an owner to the improvement.

## WhatsApp analytics questions

### Why might a read appear without a delivered status?

Provider observations can arrive in different shapes or orders. Preserve the separate read timestamp and documented message-state behavior rather than inventing a missing delivery event.

### Which record should we use for financial reconciliation?

Use the billing ledger as the financial authority. Message cost fields are useful projections and can be incomplete while processing catches up.

### Does a missing cost mean the message was free?

No. Unknown or unresolved cost is distinct from an explicit zero. Reconcile the applicable charges before drawing a conclusion.

### Can WhatsApp metrics prove campaign revenue by themselves?

No. Join the conversation or campaign to a confirmed business event using an appropriate identity and attribution model.

## Connect the complete journey

- [WhatsApp analytics guide](/docs/guides/whatsapp/tracking-and-metrics): Follow the setup, operating decisions and verification steps.
- [WhatsApp marketing](/products/whatsapp/marketing): Create relevant campaigns and help customers respond.
- [Click-to-WhatsApp ads](/products/whatsapp/click-to-whatsapp): Connect an ad to a conversation, lead or purchase.
- [WhatsApp API](/products/whatsapp/sending): Connect messages, replies and delivery events to your application.
- [WhatsApp resource library](/products/whatsapp/resources): Explore implementation guides, explained answers and comparisons.
- [WhatsApp platform](/products/whatsapp): Explore the connected product and choose the next capability.

## Turn message observations into better decisions.

Start with a controlled exchange, inspect delivery and replies, then connect the result to the order, booking or case that matters.

[Talk to a WhatsApp specialist](/demo?product=whatsapp&source_page=%2Fproducts%2Fwhatsapp%2Fanalytics)