Campaign analytics give you a clear picture of how each broadcast performed — from the number of messages dispatched to how many were opened by recipients. Every metric is tracked at the individual message level through the WhatsApp API and aggregated per campaign, giving you accurate delivery data without estimation.Documentation Index
Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
Use this file to discover all available pages before exploring further.
What this covers
- The four core delivery metrics and what each measures
- How campaign status reflects delivery progress
- How to interpret results and identify issues
Core metrics
Each campaign tracks four delivery metrics drawn from the WhatsApp Cloud API’s message status callbacks:- Sent
- Delivered
- Read
- Failed
Sent is the count of messages successfully dispatched from Galantis to the WhatsApp API.A message reaching
SENT status means it left Galantis and was accepted by Meta’s infrastructure. It does not confirm the message reached the customer’s device.If the sent count is lower than your estimated audience size, the gap typically reflects:- Customers whose consent status changed to non-
SUBSCRIBEDbetween estimation and send time - Messages that failed the API submission step — review
FAILEDcount for details
How metrics are tracked
Delivery status updates are received from Meta via webhook. Each time a message status changes — fromsent to delivered, or delivered to read, or to failed — Galantis updates the Message model record for that specific message.
MonitorCampaignJob runs during and after dispatch to tally counts and update the campaign-level status. When all messages have a terminal status, the campaign moves to SENT, PARTIALLY_SENT, or FAILED.
Reading campaign results
Navigate to Campaigns → [Campaign Name] to view the full analytics breakdown. Results are available as soon as dispatch begins — metrics update in real time as status webhooks arrive from Meta. Use the per-message error view to drill intoFAILED messages and identify the specific error reason per recipient.
Interpreting performance
| Signal | Likely meaning |
|---|---|
| High sent, low delivered | List contains inactive or invalid numbers |
| High delivered, low read | Message content or timing needs improvement |
| High read, low click-through | CTA button or offer relevance needs review |
| High failed with consent errors | List quality issue — review audience data sources |
| High failed with credit errors | Insufficient credits — review billing balance before next campaign |
Best practices
- Review failed messages after every campaign. Even a small failure rate contains actionable signal — error types tell you whether the issue is data quality, consent, or billing.
- Track read rate over time, not just per campaign. A single campaign’s read rate is affected by timing, audience, and content simultaneously. Trends across campaigns are more meaningful than individual results.
- Compare delivered-to-read rate across campaign types. Promotional and informational campaigns often have different baseline read rates. Comparing like-for-like gives more useful benchmarks.
- Act on
CUSTOMER_IS_MISSING_CALLING_CODEfailures. These indicate phone number records that will always fail until corrected. Update affected contact records in Shopify so they sync correctly into Galantis.
Related guides
- Scheduling & Throttling — How batch dispatch affects when metrics appear
- Compliance Checks — Pre-launch validations that reduce failure rates
- Audience Targeting — List and segment quality practices that improve deliverability
- Quality & Deliverability — How delivery performance affects your phone number rating