Broadcast Analytics & Real-Time Delivery Funnel

Overview

Launching a broadcast is only the first step of a WhatsApp outreach strategy. Real-time visibility into whether messages were delivered, read, or failed is essential for evaluating campaign ROI, customer engagement, and database health.

The Broadcast Analytics & Funnel Dashboard (/dashboard/marketing/campaigns/:id) provides a comprehensive command center for every launched campaign. It delivers live delivery funnel tracking, aggregate response metrics, per-recipient audit logs, granular error diagnostic messages, and phone-number search capabilities.

Accessing Campaign Analytics

Navigate to Marketing > Broadcasts (/dashboard/marketing/campaigns).
Locate your target campaign in the Broadcast History table.
Click on the broadcast name or click the arrow button on the right to open the Campaign Detail & Analytics page.

[!TIP] If a campaign is actively sending (InProgress or Queued), the page enables an automatic 5-second polling monitor (Auto-refreshing), dynamically updating message delivery counts without requiring manual page reloads.

Campaign Header & Status Lifecycle

The top section of the detail view displays key operational metadata and the current campaign execution state:

Broadcast Name: The human-friendly campaign identifier assigned during creation.
Template Name: The Meta-approved template used for this broadcast.
Created By: The team member or administrator who authored the campaign.
Execution Timestamps: Timestamp of campaign creation, launch time, and completion time.
Campaign Execution State Badge:

Status	Badge Color	Meaning & System State
Draft	Slate / Neutral	Campaign is drafted and saved, but has not yet been queued or dispatched.
Queued	Amber / Warning	Campaign is waiting in line to be processed by the broadcast queue worker.
In Progress	Blue / Info (Pulse)	Messages are actively streaming through Meta's WhatsApp Cloud API.
Completed	Emerald / Success	100% of recipient messages were processed and dispatched successfully.
Completed (Errors)	Orange / Alert	Campaign finished, but one or more recipient messages failed to dispatch.
Cancelled	Rose / Destructive	The scheduled broadcast was aborted before execution began.

Key Performance Metrics

Below the header, four high-level metric cards provide an immediate snapshot of broadcast reach:

┌──────────────┐  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐
│     SENT     │  │  DELIVERED   │  │     READ     │  │    FAILED    │
│    12,450    │  │    12,180    │  │    8,740     │  │     270      │
│ 100% of total│  │ 97.8% of sent│  │ 70.2% of sent│  │ 2.2% of total│
└──────────────┘  └──────────────┘  └──────────────┘  └──────────────┘

Sent Count: The total number of messages successfully handed off to Meta's WhatsApp Cloud servers.
Delivered Count: The number of messages that reached recipient devices (indicated by double checkmarks on WhatsApp).
Read Count: The number of messages opened and read by recipients (indicated by blue checkmarks on WhatsApp).
Failed Count: The number of messages that Meta could not deliver due to invalid numbers, blocked contacts, or network errors.

The Delivery Funnel

The Delivery Funnel visualizes the progression of your broadcast from dispatch to customer engagement:

  [ Total Recipients: 12,450 ]
              │
              ▼
  ┌────────────────────────────────────────────────────────┐
  │ Sent: 12,450 (100%)                                    │
  └────────────────────────────────────────────────────────┘
              │
              ▼
  ┌──────────────────────────────────────────────────┐
  │ Delivered: 12,180 (97.8%)                        │
  └──────────────────────────────────────────────────┘
              │
              ▼
  ┌────────────────────────────────────┐
  │ Read: 8,740 (70.2%)                │
  └────────────────────────────────────┘

Funnel Benchmarks for WhatsApp Marketing

Healthy Delivery Rate: > 95% of sent messages. Lower delivery rates suggest stale customer lists or invalid mobile numbers.
Healthy Read Rate: 60% – 85% within 4 to 24 hours of delivery. Highly targeted promotional campaigns often achieve read rates exceeding 80%.
Failure Threshold: < 3%. If failures exceed 5%, verify customer phone number formats, country codes, and opt-out preferences.

Recipient-Level Delivery Audit Log

The bottom section provides an itemized, line-by-line audit table of every individual recipient included in the broadcast run.

Table Columns

Column	Information Displayed
#	Sequence line number corresponding to the uploaded audience list.
Phone Number	International format mobile number (e.g. `+91 98765 43210`).
Send Status	Immediate dispatch result: `Sent`, `Failed`, `Pending`, or `Skipped`.
Delivery Status	End-to-end receipt status from Meta webhooks: `Delivered`, `Read`, `Failed`, `Sent`, or `Deleted`.
Failure Reason	Specific error explanation explaining why delivery was unsuccessful.

Quick Filter Tabs

Above the table, filter tabs allow instant isolation of specific recipient segments:

All: Full recipient roster.
Delivered: Recipients whose devices received the message.
Read: Recipients who opened and viewed the template.
Failed: Recipients whose messages encountered errors.
Sent Only: Messages dispatched by Meta servers but not yet confirmed as delivered to the device (often device offline or out of coverage).
Pending: Messages queued awaiting dispatch.

Searching and Sorting

Instant Phone Search: Type any partial or complete phone number in the search bar to locate specific customer delivery records.
Column Sorting: Click on any column header (such as Line Number or Send Status) to toggle ascending or descending sorting.
Pagination Control: Switch between 20, 50, or 100 rows per page to review large audience logs smoothly.

Diagnosing Common Delivery Failures

When a message status displays as Failed, the Failure Reason column surfaces actionable diagnostic feedback. Common causes include:

Failure Message	Cause	Corrective Action
User is not on WhatsApp	The phone number is a landline or has no active WhatsApp account.	Clean the contact record in your CRM or mark the number as invalid.
Message undeliverable / blocked	Recipient has blocked your business number or phone privacy settings reject business chats.	Number will automatically be suppressed in subsequent broadcast runs.
Template variable mismatch	A required dynamic placeholder (e.g. `{{2}}`) was empty or contained invalid formatting.	Review your audience CSV or CRM mapping to ensure all variables are populated before launching.
Outside 24-hour service window	Attempted to send a session message instead of an approved template.	Ensure all broadcast communications utilize official pre-approved Meta templates.
Spam rate limit reached	Account hit Meta's daily messaging tier limit or negative quality score threshold.	Pause broadcasts for 24 hours until tier resets; review content relevance to avoid customer spam reports.

Best Practices for Campaign Analysis

Wait 2 to 4 Hours for Accurate Read Rates: While delivery statuses update within seconds, customers open messages throughout the day. Review final read rates 4 to 12 hours post-launch.
Track Opt-Out Rates: Monitor customer replies in the Team Inbox following a broadcast. If multiple recipients reply STOP or express dissatisfaction, adjust audience segmentation criteria.
Prune Stale Contacts: Regularly export or review failed recipients. Removing inactive numbers improves your delivery percentages and prevents wasted messaging credits.
Compare Template Performance: Compare the read and click-through rates of image header templates versus text-only templates to optimize future campaign designs.

Overview​

Accessing Campaign Analytics​

Campaign Header & Status Lifecycle​

Key Performance Metrics​

The Delivery Funnel​

Funnel Benchmarks for WhatsApp Marketing​

Recipient-Level Delivery Audit Log​

Table Columns​

Quick Filter Tabs​

Searching and Sorting​

Diagnosing Common Delivery Failures​

Best Practices for Campaign Analysis​