We were setting up analytics for our own funnel when we hit a wall worth writing down — because if you run ads that send people to WhatsApp, you'll hit it too, and it quietly wastes ad budget.

Here's the short version: the conversion happens somewhere your analytics tool can't see. Picking a "better" analytics tool doesn't fix it. Something else does.

Why the dashboard shows nothing

Website analytics — Google Analytics and every other browser-based tool — works by running a small script in the browser, on your website. It can only see what happens on pages you own.

A click-to-WhatsApp ad does the opposite. Someone taps your ad and lands straight in the WhatsApp app, in a chat with you. They never touch your website. The questions get answered, the quote gets sent, the booking gets made — all inside the chat. There's no web page in that flow, so there's no script watching, so your analytics has nothing to report.

This is why "which analytics tool should I use?" is the wrong first question for a WhatsApp funnel. GA4, the privacy-friendly ones, the fancy product-analytics ones — none of them can see a conversation that happens inside another app. They're not bad; they're just looking in the wrong place.

What actually connects the ad to the sale

There's a quieter mechanism that does work, and it's the thing to get right.

When someone taps a Meta ad that opens WhatsApp, Meta quietly attaches a hidden tag to that first message — a click ID. Think of it as a numbered ticket that says "this conversation started from that ad." (Google has its own version for its ads.)

That ticket is the link that matters. When the chat turns into a real customer, you send it back to the ad platform — "the conversation from this ticket just became a sale." Now Meta knows which ad actually produced a paying customer, not just which ad got a cheap click. And once it knows that, it can go find more people like the ones who bought.

The important part for a non-technical owner: this hand-off happens behind the scenes, between your systems and the ad platform — not through a tag on a web page. It's a different mechanism than website analytics, and it's what stops you from scaling up the ad that gets cheap clicks and no customers.

The trap that wastes the budget silently

Here's the gotcha that cost us an afternoon and would cost an owner a lot more.

That numbered ticket only works if it actually reaches you. Your WhatsApp number is run by a provider sitting between Meta and your business, and that provider has to pass the ticket through. Ours didn't document whether it does — the field simply wasn't mentioned anywhere. It might forward it, it might quietly drop it, and you can't tell from the docs.

So before building anything on top of it, we did the cheapest possible test: run one real ad, tap it ourselves, send a message, and look at exactly what arrived. If the ticket's in there, you're in business. If it isn't, no amount of analytics setup will save you — it's a plumbing problem with your provider, and that's the conversation to have first.

The lesson generalizes: confirm your provider actually passes the click ID through before you build any reporting on top of it. A whole attribution setup resting on a click ID your provider silently strips is worse than no setup, because it looks like it's working.

Three jobs, three tools — don't ask one to do all three

Untangling this made the roles obvious. There are three separate jobs, and reaching for a single tool to cover them is the core mistake:

  • Tell the ad platforms what worked (the click-ID hand-off above). This is the money signal — it's what makes your ad spend get smarter instead of just bigger. For a WhatsApp funnel, it's the one you can't skip.
  • See what people do on your website (Google Analytics). Useful for your site and your other ads — but blind to the chat.
  • See the whole journey, chat included (a product-analytics tool fed from your back end). This is the only one that can show the WhatsApp steps, and only because the events come from your systems, not a browser.

Each tool is good at its job, and not much help outside it.

What we'd tell you

If you're paying to send people into WhatsApp and your reports look empty, you're not doing it wrong and you don't need a new dashboard. You need the click ID to survive the trip into the chat, and you need to send it back to the ad platform when a chat becomes a customer.

We've just wired this up for ourselves and haven't run real campaign volume through it yet, so we won't pretend we have conversion numbers to show. But the shape of the problem is clear, and the first move is cheap: before you trust any of it, run one ad, click it, and confirm the ticket actually arrived. Check the pipe first.