# WhatsApp metrics and reporting

Customer.io tracks metrics for your WhatsApp messages so you can understand how your audience interacts with them. You can view WhatsApp metrics in campaign dashboards and the delivery log.

## WhatsApp message metrics[](#whatsapp-message-metrics)

The following metrics apply to WhatsApp messages. Some metrics, like **Opened**, behave differently for WhatsApp than for email because they rely on WhatsApp-specific signals like read receipts.

Metric

Description

Drafted

We generated the message but haven’t sent it yet. The message requires manual action if you use *Queue Draft*.

Sent

The message left Customer.io and was passed to the delivery provider.

Delivered

The delivery provider confirmed that the message reached the recipient.

Opened

The recipient read the message. For WhatsApp, this is based on **read receipts**, not a tracking pixel. If a recipient turns off read receipts in their WhatsApp settings, we can’t track this metric.

Clicked

The recipient tapped a tracked link in the message.

Failed

The message didn’t leave Customer.io. This typically happens when a required variable is missing or a template isn’t approved.

Converted

The recipient completed your [conversion goal](/journeys/campaign-conversions/).

 Read receipts and the Opened metric

WhatsApp’s **Opened** metric relies on read receipts, which recipients can turn off in their WhatsApp privacy settings. If read receipts are off, Customer.io won’t receive an open signal for that message. This is different from email, where open tracking uses a tracking pixel.

## Reply tracking[](#reply-tracking)

Customer.io doesn’t track replies for WhatsApp messages. This means that you can’t use replies as a conversion goal or typically respond to inbound messages through Customer.io without a webhook-based workflow.