WhatsApp campaign reporting is the practice of collecting, organising, and interpreting performance data from your WhatsApp channels — delivery counts, read rates, click-throughs, opt-outs, and revenue attribution — so every campaign decision is anchored in evidence rather than instinct. If you are following the WhatsApp marketing guide for South Africa, reporting is the step that determines whether your strategy actually improves over time or simply repeats itself.
Around 29 million South Africans actively use WhatsApp — roughly 94–96% of internet users, per app analytics data from January 2025. That reach makes WhatsApp one of the most powerful channels available to SA businesses, and it means the cost of running campaigns without proper reporting is high: investing in one of the country's most-used apps without knowing which campaigns earned their keep.
Most operators can tell you their last broadcast's read rate. Far fewer have a system connecting those reads to revenue, tracking template quality, maintaining a POPIA consent trail, and running on a consistent review cadence. This guide builds that infrastructure.
Quick Answer
WhatsApp campaign reporting combines three data sources: the native analytics in WhatsApp Manager (messaging, template, and conversation analytics), UTM-tagged links that bridge WhatsApp activity to your GA4 property, and a POPIA compliance log that records consent, opt-outs, and list-hygiene events. Together, these tell you which campaigns drove revenue, which templates are heading toward a quality-rating downgrade, and whether your data practices can withstand an Information Regulator audit.
Jump to a section
What WhatsApp Campaign Reporting Actually Covers
Your Three Native Analytics Views in WhatsApp Manager
Building Your WhatsApp Campaign Reporting Dashboard
UTM Parameters: Bridging WhatsApp to GA4
POPIA — The Fourth Column in Every WhatsApp Report
Reading Healthy vs. Unhealthy Campaign Signals
Does your WhatsApp setup produce a revenue-attributed weekly report?
Tell us what you're currently tracking and we'll show you what the full three-layer reporting stack should look like for your business — no obligation.
See What Full Reporting Looks LikeWhat WhatsApp Campaign Reporting Actually Covers
WhatsApp campaign reporting spans four interconnected layers, each answering a different business question.
Delivery health answers "did the message reach the right people?" — tracking sent-to-delivered ratios, failed sends, and number quality. Engagement quality answers "did recipients respond?" — read rates, button-click counts, reply counts, and link clicks. Revenue attribution answers "did the campaign move the business?" — connecting WhatsApp touchpoints to purchases, bookings, or qualified leads. Compliance integrity answers "can we prove we had the right to send this?" — consent timestamps, opt-out records, and suppression-list updates.
For a deeper breakdown of what each engagement metric means and how to calculate it, the WhatsApp marketing metrics guide covers the definitions in detail. This guide focuses on the infrastructure: which tools produce each data layer, how to connect them into a coherent dashboard, and what to do with the output each week.
Key Principle
Delivery and read data lives inside WhatsApp Manager. Revenue attribution requires UTM-tagged links feeding GA4 (or your CRM). POPIA compliance data must be logged separately — Meta's native tools do not record consent provenance or opt-out timestamps. All three sources need to be active before your first reporting cycle is meaningful.
Your Three Native Analytics Views in WhatsApp Manager
WhatsApp Manager, accessed via Meta Business Suite, provides three built-in analytics views that form the foundation of any campaign reporting setup.
Messaging analytics shows aggregate counts of messages sent, delivered, and received, broken down by date range and conversation type. Use this view to spot volume trends and identify the split between business-initiated (template) and customer-initiated (service) conversations. Both matter for cost management — especially since July 2025, when Meta shifted from per-session to per-message billing for templates. Understanding the marketing, utility, and authentication category split directly controls your monthly messaging cost. The WhatsApp Business API pricing guide for South Africa covers category costs in full.
Template analytics is the most directly actionable view. Select any approved message template and open its Insights tab to see sent, delivered, and read counts alongside button-click tallies. This is where you find out whether a CTA button is actually being tapped or just read past, and it is the primary signal for template optimisation.
Pricing and conversation analytics tracks spend by conversation category over time. If your marketing conversation spend is rising while reply rates stay flat, this view flags the mismatch before it becomes a budget problem.
WhatsApp Business App vs. WhatsApp Business Platform (API)
The free WhatsApp Business app shows aggregate statistics — total sent, delivered, read, received — but does not break these down by campaign, template, or contact segment, and provides no conversion data. Businesses running broadcast campaigns or WhatsApp chatbot automations need the Business Platform (API) and a business solution provider to get campaign-level reporting.
Building Your WhatsApp Campaign Reporting Dashboard
A functional WhatsApp campaign reporting dashboard pulls from three sources — WhatsApp Manager, GA4, and your CRM — and organises them into a weekly one-page view that shows whether this week's activity improved on last week's.
The structure that works in practice for most SA businesses has five columns:
| Column | What It Shows | Data Source |
|---|---|---|
| Delivery health | Sent vs. delivered rate; failed sends | WhatsApp Manager (messaging analytics) |
| Engagement quality | Read rate; button clicks; reply count | WhatsApp Manager (template analytics) |
| Revenue attribution | Sessions from WhatsApp; conversions; revenue | GA4 (Traffic Acquisition, filtered by utm_source=whatsapp) |
| Compliance status | Opt-outs this period; suppression list size; consent log updated? | Your CRM or opt-in platform |
| Quality rating | Current template quality (High/Medium/Low); block and report rate | WhatsApp Manager (template insights) |
The CRM connection is the layer most businesses skip. With your WhatsApp CRM integration in place, tag every contact with the campaign that acquired them and track subsequent conversions — turning a single read rate into a lifetime revenue figure per list segment. If not yet in place, start with the GA4 UTM bridge and add the CRM layer once that attribution is working.
For WhatsApp Flows, Manager records form completions and step drop-off data — track completion rate and exit points per flow as a separate row in your dashboard.
UTM Parameters: Bridging WhatsApp to GA4
WhatsApp does not share click data with external analytics tools. Without UTM-tagged links in your templates, every click from a broadcast appears in GA4 as direct traffic — invisible and unattributable. UTM tracking is the only reliable attribution bridge between WhatsApp activity and your website analytics.
The standard structure for WhatsApp broadcasts:
utm_source=whatsapp&utm_medium=broadcast&utm_campaign=aug-promo-2026For Click-to-WhatsApp ads, use
utm_medium=ctwa-followup on follow-up messages to separate ad-originated conversations from organic broadcasts in your reports.Inconsistent capitalisation ("Broadcast" vs "broadcast"), missing campaign names, or using the same UTM string across different campaigns. Each inconsistency creates a separate row in GA4, splitting your data and making campaign comparison impossible.
In GA4, navigate to Reports → Acquisition → Traffic Acquisition, then filter by Session source containing "whatsapp" to see all WhatsApp-originated sessions, revenue, and goal completions for any date range. Naming your campaigns with a consistent convention — lowercase, channel first, then campaign type, then date (e.g., whatsapp_broadcast_retention_aug-2026) — keeps this view clean across months of data.
Attribution Rule of Thumb
Every template link — whether in a broadcast, a Flow, a chatbot response, or a status message — should carry its own UTM string with a unique utm_medium value for that WhatsApp surface. Without this separation, broadcast performance, chatbot performance, and status performance all collapse into the same GA4 row and you cannot tell which drove the result.
POPIA — The Fourth Column in Every WhatsApp Report
Under the Protection of Personal Information Act (POPIA), WhatsApp messages to South African consumers constitute electronic direct marketing under Section 69 of the Act. That classification carries specific record-keeping obligations that belong in every campaign reporting framework — not as a separate compliance project, but as a column in your weekly dashboard.
POPIA is an opt-in regime. An active, voluntary opt-in — a ticked checkbox, a typed "YES," an explicit agreement — must exist for every contact you market to, unless they are an existing customer and you are offering similar products. Pre-ticked boxes, purchased lists, and inferred consent do not qualify.
The April 2025 regulatory amendments made explicit that an "opt-out shall not constitute consent" — providing an unsubscribe link does not create the permission that allows you to send in the first place. A functional opt-out option is still a legal requirement in every marketing message under POPIA Section 69; it simply cannot substitute for the upfront consent that authorises the send.
What your compliance reporting layer must log per campaign:
- Consent timestamp and source for every number on the send list (e.g., "opted in via website form, 14 March 2026")
- Opt-outs received this campaign period — counted, timestamped, and removed from active lists immediately
- Suppression list version used at send time — so you can prove no previously opted-out contact received the broadcast
- Existing customer flag if relying on the existing-customer exception — noting the product/service relationship and that a clear opt-out option was included
The Information Regulator issued its first direct marketing enforcement notice in February 2024, published its Guidance Note on Direct Marketing in December 2024, amended the POPIA Regulations in April 2025, and commenced a formal monitoring exercise in February 2026. Penalties for unlawful processing reach up to R10 million per breach. The enforcement infrastructure is active, not theoretical.
Practical Compliance Tip
A simple Google Sheet with columns for phone number, opt-in source, opt-in date, and opt-out date (if applicable) satisfies the record-keeping requirement for most SMEs. The key is that it is maintained at send time — not reconstructed after an enquiry arrives. Your opt-out rate in each campaign report is both a deliverability signal and a compliance metric.
Not sure your WhatsApp opt-in records would survive a POPIA audit?
Share your current opt-in flow and we'll review it for compliance gaps before they become enforcement notices — no obligation, back to you within 24 hours.
Request a Compliance ReviewReading Healthy vs. Unhealthy Campaign Signals
Five measurable signals — quality rating, block rate, opt-out rate, read rate, and click-through rate — determine whether a WhatsApp campaign is healthy, declining, or approaching a Meta-imposed sending limit. Each has a specific threshold and a specific action when crossed.
Template quality rating (High/Medium/Low): Meta calculates this from block rate, report rate, unhealthy template usage, and message volume over the last 24 hours — reply rate and template engagement contribute positively. A downgrade from High to Medium is an early warning. A drop to Low can trigger sending limits that reduce your maximum daily messages. Check this rating weekly, not monthly.
Block rate above 1% per 1,000 messages: A block rate at this level can shift your quality rating from green to yellow within 24 hours. Blocks carry more weight than opt-outs — they signal the recipient wanted zero contact, not fewer messages. If your block rate climbs, review message frequency, list relevance, and opt-in quality before the next send.
Opt-out rate above 2% per campaign: This threshold is the point at which Meta's quality system takes notice. Occasional elevated opt-outs after a frequency burst are recoverable; sustained rates above 2% across successive campaigns indicate a structural problem with list health or message relevance.
Read rate as a floor, not a ceiling: One widely referenced global figure — from Braze data cited by Blueticks — puts the average read rate for opted-in WhatsApp marketing messages around 68%. This is a floor figure: it counts only recipients who have read receipts enabled, so actual reads are likely higher. The more reliable signal is your own read rate trend across campaigns. A read rate falling across three successive campaigns is a content or frequency problem.
Click-through rate by template type: Chatarmin's global benchmarks put interactive-button CTR at 45–60%, versus 2–5% for text links. These are directional global figures, not SA-specific benchmarks. South Africa's 94–96% WhatsApp penetration among internet users means SA list quality varies more widely than in markets with lower adoption — a tightly opted-in SA list typically performs at or above these global reference points, while a loosely consented or purchased list often falls well below them. Use the global figures to set initial expectations; your own programme's trend is the primary benchmark. A button CTA that consistently underperforms your average by 20+ percentage points is a template worth rewriting.
The official WhatsApp Business blog's case study on Baro Cosmetics — an 80% message open rate and a 10–11x purchase rate increase compared with email — illustrates what a well-managed programme looks like at full maturity. Holiday Pirates reported 10x more engagement from WhatsApp than from email. Neither figure translates directly to a South African SME benchmark, but both illustrate that the reporting infrastructure to capture and compare these numbers is what separates optimised programmes from static ones.
Why South African Businesses Choose Growth Pulse Media for WhatsApp Reporting
Growth Pulse Media connects all three reporting layers — WhatsApp Manager analytics, GA4 UTM attribution, and a POPIA-compliant consent and opt-out log — as a single integrated setup, not three separate projects handed off between teams. Our WhatsApp marketing service has the reporting infrastructure built in from the first campaign send.
Our founder built and scaled a South African ecommerce business before founding GPM — the reporting frameworks we hand to clients are the ones we needed ourselves, paid for with real messaging spend on real SA audiences. We have run the broadcasts, tracked the template quality downgrades, and learned which UTM naming conventions keep GA4 data clean across months of campaigns.
On the platform side, we work with native WhatsApp Business API setups and SA-compatible business solution providers, connected to the CRM and analytics tools SA businesses already use — including HubSpot, ActiveCampaign, and GA4. We work with a deliberately limited number of active clients, which means every reporting review is handled by a senior strategist, not escalated from a junior account layer.
Who This Is NOT For
You know what you want to measure — now build the infrastructure to measure it.
Book a scoped reporting setup: we configure WhatsApp Manager analytics, your GA4 UTM conventions, and a POPIA-compliant consent log in a single structured engagement.
Book a Reporting Setup SessionFrequently Asked Questions
What metrics should I track in WhatsApp campaign reporting?
At minimum, track delivery rate (sent-to-delivered ratio), read rate (delivered-to-read), button-click rate, opt-out rate, and block rate for every campaign. Add revenue attribution via UTM-tagged links in GA4 once the basic infrastructure is in place. Template quality rating — checked in WhatsApp Manager — is the early-warning signal for deliverability problems and should be reviewed weekly alongside campaign metrics.
How do I connect WhatsApp performance to my Google Analytics 4 reports?
Add UTM parameters to every link in your WhatsApp templates before sending. Use a consistent naming convention: utm_source=whatsapp, utm_medium=broadcast (or ctwa-followup for Click-to-WhatsApp ad follow-ups), and a campaign-specific utm_campaign value. In GA4, filter the Traffic Acquisition report by session source containing 'whatsapp' to see sessions, conversions, and revenue attributed to each campaign. WhatsApp does not send click data to GA4 natively — UTM parameters are the only attribution bridge.
Does POPIA require me to keep records of WhatsApp marketing consent?
Yes. Because WhatsApp messages constitute electronic direct marketing under POPIA Section 69, you must be able to demonstrate lawful basis for every contact you message. For most marketing messages, that means an active opt-in record — source, date, and nature of consent. Opt-out records must be maintained and acted on immediately. The Information Regulator's formal monitoring exercise, which commenced in February 2026, makes these records an active compliance requirement, not a theoretical one.
What is a WhatsApp quality rating and how does it affect my campaigns?
WhatsApp assigns each approved message template a quality rating — High, Medium, or Low — based on signals from the last 24 hours: block rate, report rate, unhealthy template usage, and send volume relative to tier. A Low rating can trigger sending limits that cap the number of messages your number can send per day. Monitor the quality rating in WhatsApp Manager's template analytics view after every campaign send. A block rate above 1% per 1,000 messages is the primary risk threshold to watch.
How often should I review my WhatsApp campaign reports?
As a practical rule of thumb, check template quality rating within 24–48 hours of each send — the rating reacts quickly to block and report signals, and catching a downgrade early prevents a sending-limit escalation. Engagement metrics (read rate, button clicks, opt-outs) are typically stable around 72 hours post-send based on WhatsApp's observed read velocity. Revenue attribution in GA4 is best reviewed at 7 days, once the purchase window has closed. A monthly review then aggregates these into trend data across campaign types, list segments, and send frequencies.
Build WhatsApp Reporting That Connects to Real Revenue
Growth Pulse Media sets up WhatsApp campaign reporting from the ground up — WhatsApp Manager analytics, GA4 UTM attribution, and a POPIA-compliant consent log — integrated with the platforms SA businesses already use. Senior attention, limited client load, no obligation.
Talk to Us About WhatsApp ReportingNo obligation — we'll get back to you within 24 hours.

