I sat in a budget review last quarter where a founder walked us through the 2026 plan, line by line.
Meta had a number. Google had a number. Influencers had a number. Even the “brand” bucket had a number nobody could quite defend.
WhatsApp? It was tucked under CRM. No budget of its own. No CAC. No ROAS target.
And yet, when we opened the revenue dashboard, WhatsApp was doing roughly a quarter of the top line.
That gap — between what the channel earns and how we fund it — is the whole story.
The number CMOs keep filing in the wrong folder
You’ve probably seen the figure floating around: WhatsApp now drives somewhere between 20–35% of D2C revenue in India.
Let me be honest about that number. There isn’t one clean, audited source you can wave in a board meeting. It shows up, worded slightly differently, across a stack of 2026 industry reports and vendor decks. Treat it as a directional estimate, not gospel.
But even at the low end, think about what 20% means for a ₹50 crore brand. That’s ₹10 crore flowing through a channel you’ve slotted under “retention,” with no owner and no measurement plan.
We don’t do this to any other channel that size. Imagine telling your board that Meta lives inside the “customer support” cost centre.
👉 A channel gets a line item when it earns one. WhatsApp earned it a while ago — most budgets just haven’t noticed.
So why is it still filed under CRM? Partly habit. WhatsApp entered most Indian brands as a support tool — order updates, “where’s my package,” a bot to deflect tickets. It grew up. The org chart didn’t.
WhatsApp stopped being a helpdesk two years ago
Here’s what changed while we weren’t looking. WhatsApp quietly became a full commerce surface — catalogues, in-chat checkout, curated storefronts, Click-to-WhatsApp ads pulling people in cold. Not a place to service a customer. A place to acquire one.
The GoKwik WhatsApp Commerce Intelligence Report for 2026 puts real numbers behind this. They analysed 26 billion messages across 1,800+ D2C brands over four quarters. The line that stopped me:
👉 83% of all WhatsApp-driven orders in the Oct–Dec 2025 festive quarter came from first-time buyers.
Read that again. Eighty-three percent were new customers. That is not a retention channel. That is an acquisition channel wearing a retention badge.
But here’s the nuance, because there always is one. Volume isn’t what separates the winners. Automation is.
Brands running automated customer journeys saw an 11.1% average click-through rate, against 2.6% for old-school broadcast blasts. Even when broadcast CTR climbed to about 3% during the festive peak, automation still beat it by more than 3.5x. Some automated journeys hit open rates near 74%.
As Chirag Taneja of GoKwik put it: “The brands seeing outsized growth on WhatsApp aren’t sending more messages. They are letting AI decide which message to send, to whom, and when.”
The category data seals it. In electronics, top-quartile brands converted at around 1.5% versus a 0.4% network average — a 3.8x gap. In fashion, top performers ran at 2.5x the category average. That spread doesn’t come from spending more. It comes from building the channel properly.
A utility doesn’t have a top quartile. A media channel does.
The attribution gap nobody built the plumbing for
Now for the uncomfortable part.
If WhatsApp is doing a quarter of your revenue, can you actually prove which rupee came from where?
Most brands can’t. And it’s not a discipline problem — it’s a plumbing problem.
When someone taps a Click-to-WhatsApp ad, Meta injects a tracking ID called ctwa_clid into the webhook. Here’s the trap: it only shows up in the first message of the conversation. Miss it there, and it’s gone forever. One CTWA guide put the failure rate bluntly — 9 out of 10 advertisers lose attribution. Their Meta dashboard proudly shows “conversations started,” and not a single sale tied back to it.
Conversations started is not revenue. It’s a vanity metric in a nice costume.
The second failure sits in the Conversions API setup. To connect a WhatsApp sale back to the ad that sparked it, events need to fire with action_source: "business_messaging" and messaging_channel: "whatsapp". Leave it on the generic "website" default — which is exactly what most teams do — and Meta simply won’t associate the sale with your CTWA ad. It’s the single most common misconfiguration.
So you end up in the worst spot: a channel that quietly prints money, and no evidence to justify funding it. No wonder it stays stuck under CRM. You can’t fight for a budget line you can’t measure.
What does a real WhatsApp attribution stack actually look like? A few things:
- 🔹 Capture
ctwa_clidon the first inbound message — no exceptions. - 🔹 Fire CAPI events for the real journey: viewed product, added to cart, purchase completed.
- 🔹 Measure first-reply speed. The money is made after the click, and a slow human handoff quietly breaks the chain.
- 🔹 Stop benchmarking on flat cost-per-lead. A ₹50 lead is terrible if none convert; a ₹1,500 lead is brilliant if it becomes a ₹2 lakh order. Track cost-per-qualified-lead and revenue-per-conversation instead.
This isn’t just my hobby-horse. When Bain and Meta studied Indian conversational commerce — surveying 7,800 users and 150 businesses — one of their five headline recommendations was to “implement measurement frameworks to assess conversational commerce performance.” The industry knows the gap exists. Very few have closed it.
India vs global: we’re actually ahead here
There’s a strange thing happening, and it’s worth naming.
Globally, Meta’s messaging ads are one of its fastest-growing lines — Click-to-WhatsApp ad revenue grew 60% year-on-year in Q3 2025, and Meta is rolling out ads on WhatsApp Status through 2026. The infrastructure is scaling up fast.
But adoption is lopsided. In India, WhatsApp has roughly 536 million monthly users and near-total penetration. Over 650 million Indians are active on messaging platforms, against only about 200 million who shop online — a 3x+ gap Bain calls the untapped opportunity. In the US, WhatsApp has around 100 million monthly users, and only about one in two opens the app daily.
I’ll add the caveat the data demands: penetration isn’t the same as monetization. Average WhatsApp ARPU in Europe runs well above the global average — and India’s monetization almost certainly trails Europe’s, even if it leads on usage. So “global brands are behind” isn’t quite right everywhere.
But the behaviour gap is real. In the US and much of Europe, CTWA is still an experiment — a line item someone tests. In India, it’s already how people shop.
Which means Indian marketers know something global marketing content hasn’t caught up to yet: WhatsApp isn’t the next channel. It’s a current one. Most of the playbooks being written abroad are still treating it as tomorrow’s bet.
The budget line I’d actually propose
So here’s what I’d put on the table.
Stop sizing WhatsApp against “support cost saved.” That framing caps it forever — it turns a revenue engine into a savings exercise. Size the line item against its revenue share. If it’s doing 25% of revenue, it deserves a funded, owned, measured seat next to Meta and Google. Not a footnote under CRM.
But — and this matters — don’t ask for the budget before you can measure it. Earn the line item with the plumbing first. A minimal checklist before you walk into that meeting:
- ✅
ctwa_clidcaptured on first message - ✅ CAPI events firing with the correct
action_source - ✅ First-reply time tracked and tightened
- ✅ A cost-per-qualified-lead and revenue-per-conversation number you trust
- ❌ Not “conversations started” as your headline metric
Do that, and the budget conversation stops being a debate. The numbers argue for you.
One vendor framing stuck with me: most brands “still treat it as a help desk” while it quietly does the work of their best-performing channel. The tragedy isn’t that WhatsApp underperforms. It’s that it over-performs, invisibly, in a folder marked “support.”
The channel isn’t waiting for your org chart to catch up. It’s already converting first-time buyers at scale while your budget spreadsheet pretends it’s a cost centre.
👉 The question isn’t whether WhatsApp deserves a line item. It’s how much revenue you’re comfortable leaving unattributed until it gets one.
I’d love to hear from the folks building 2026 plans right now — is WhatsApp a funded, owned channel in your budget, or is it still hiding under CRM? What’s stopping the shift? Drop your experience below; I’ll learn as much from you as you might from this.