# WhatsApp Reports

WhatsApp Reports help you validate send results across Netmera, Meta (WhatsApp), and end-user engagement.

Use them to confirm delivery, investigate failures, and monitor reads over time.

{% hint style="info" %}
To populate **Delivery (Success)** and **Read** metrics, you must configure Meta WhatsApp webhooks. See [WhatsApp Integration](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/whatsapp/whatsapp-integration).
{% endhint %}

### What you see on the report page

#### Overview (KPI cards)

These cards summarize the full campaign lifecycle.

They start with your planned audience, then show sending, delivery, failures, and reads.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F8GKecpzS5eJ2JD55v8eK%2FScreenshot%202026-01-19%20at%2014.28.55.png?alt=media&#x26;token=bafdde38-8893-4d1a-bae3-4de070894b6a" alt=""><figcaption><p>Overview (KPI cards)</p></figcaption></figure>

### Metrics explained

#### Target Audience

The total audience size selected for the campaign.

#### Sent

The number of messages **successfully submitted** by Netmera to the Meta (WhatsApp) APIs.

This metric means Netmera completed the technical send successfully.

#### Delivery (Success)

The number of messages **successfully delivered** to end users by Meta.

This value is based on the `delivered` events received via Meta WhatsApp webhooks.

{% hint style="info" %}
Delivery can lag behind Sent.

This is expected while Meta is still processing message statuses.
{% endhint %}

#### Delivery Rate (%)

Shows what percentage of sent messages were delivered to users.

**Formula:** `(Delivery / Sent) × 100`

#### Failed

Messages marked as failed by Meta (`failed` status).

{% hint style="info" %}
Failed messages are counted when Meta returns a final failure status.

While a campaign is still sending, you may see temporary gaps between Sent and (Delivery + Failed).
{% endhint %}

#### Read

Shows the number of messages opened and read by users.

Read events are displayed as a **line chart** on the report page.

This metric is based on the `read` events received from Meta.

#### Not Read

Messages that were delivered but not read yet.

Calculated as `(Delivery – Read)`.

#### Read Rate (%)

Shows what percentage of delivered messages were read.

**Formula:** `(Read / Delivery) × 100`

### How to interpret the numbers

#### Expected relationships

These checks help you quickly spot anomalies:

* **Read ≤ Delivery (Success)**\
  A message cannot be read before it is delivered.
* **Not Read = Delivery – Read**\
  This is a calculated field, not a webhook status.

#### Example

If you have:

* `Sent = 10,000`
* `Delivery (Success) = 9,200`
* `Read = 3,680`

Then:

* `Delivery Rate (%) = (9,200 / 10,000) × 100 = 92%`
* `Not Read = 9,200 – 3,680 = 5,520`
* `Read Rate (%) = (3,680 / 9,200) × 100 = 40%`

#### Read trend (line chart)

The report also visualizes read activity over time.

Use it to spot when users actually read the message after delivery.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FMJfN0dt2jAKuI9JMzby0%2Fimage.png?alt=media&#x26;token=06090a05-625f-4578-beab-bc589d71ba9f" alt=""><figcaption><p>Read trend (line chart)</p></figcaption></figure>

**How to read this chart**

* **X-axis**: Time buckets within the selected report range.
* **Y-axis**: Number of `read` events.
* Spikes usually mean users opened the message after delivery.