Someone clicks a Google ad, lands on a page, taps the WhatsApp button, has a conversation, and buys. The advertiser can see the click on one side and the deal on the other, but nothing in between connects them. The redirect that carries a customer from a landing page into a WhatsApp conversation drops the identifier Google attached to the click, which is why so many WhatsApp-sourced leads land in reporting as unknown.
What Happens at the wa.me Hop
wa.me is the link format that hands a visitor off from a web page into a WhatsApp conversation. In practice, once a click reaches that redirect, the destination number and any pre-filled message text carry through to the conversation, and other parameters attached to the same link, including Google's click identifier, do not.
This isn't a gap in anyone's tracking setup. It's the redirect doing what it's built to do: hand a phone number and a message to WhatsApp, and nothing else. Google didn't build wa.me, and there's no agreement between the two platforms to preserve a competitor's click ID across that boundary.
Why Meta's Own Ads Don't Have This Problem
The picture looks different when the ad itself is a Meta ad. Run a click-to-WhatsApp campaign on Facebook or Instagram, and the referral information arrives inside Meta's own ecosystem: a click identifier is included in the webhook payload when the conversation starts. A business that reads that payload, as a Meta WhatsApp Cloud API solution provider does, can tie the conversation back to the ad that started it.
Google-into-WhatsApp doesn't get the same treatment, and there's no reason it would. wa.me is Meta's redirector. Preserving a competitor's tracking parameter across that hop was never part of the design.
The Fixes Businesses Try, and Where They Leak
Faced with the gap, most teams reach for one of two fixes, and both have a hole in them.
The first is a token in the pre-filled message: mint a unique code, attach it to the message text, store it against the click when the link is generated, and match it against whatever arrives on WhatsApp. It works until the customer edits the message before sending it, which happens often enough to matter, because WhatsApp lets people rewrite pre-filled text before they hit send. A customer who deletes the code and types their own question looks, from the reporting side, identical to a customer who arrived with no tracking at all. The leak is visible in aggregate (mint a thousand links, count how many still carry a code on arrival), but the specific leads that lost their code can't be recovered after the fact.
The second fix is a form in front of the WhatsApp button: capture the click identifier before the visitor leaves the page, then hand them on to WhatsApp. Nothing breaks this, because the evidence is captured before the customer has a chance to lose it. But it reintroduces the exact friction that made WhatsApp the preferred channel in the first place. A business that offered WhatsApp because customers didn't want to fill in a form has now put a form in front of the WhatsApp button, to measure how many people would have preferred WhatsApp to the form.
| Fix | Survives message editing | Adds friction before WhatsApp |
|---|---|---|
| Token in the pre-filled message | No | No |
| Form before the WhatsApp button | Yes | Yes |
| Number-carried attribution | Yes | No |
A Fix Call Tracking Solved Fifteen Years Ago
Voice call tracking ran into the identical problem long before WhatsApp existed. A customer clicked an ad, called a phone number instead of filling in a form, and the click disappeared the moment they left the browser. The industry's answer wasn't a token or a form. It was Dynamic Number Insertion: show each visitor a unique phone number tied to the campaign that brought them, so the number itself carries the attribution when they call. Nothing depends on the customer preserving anything, because the customer isn't the one carrying it. The number is.
The same principle applies once the destination is a WhatsApp conversation instead of a phone call.
How Wappari Carries the Number Through
Wappari runs this pattern for businesses advertising into WhatsApp. As a Meta WhatsApp Cloud API solution provider, Wappari sees the payload as each conversation lands, and applies the same number-carried approach voice call tracking has used for over a decade: the number a customer arrives on identifies the campaign that put them there, so the attribution survives the hop even when the customer never sees a code to lose.
Every method that asks the customer to carry something eventually loses some customers along the way. Carrying it on the number instead means there's nothing for the customer to lose in the first place. If you're running paid search into a WhatsApp button, what is your attribution telling you right now, and how would you know if it were wrong?
Frequently Asked Questions
How do I pass a gclid into WhatsApp?
A gclid can't travel through the wa.me redirect as a URL parameter. The redirect only carries the destination number and any pre-filled message text through to the conversation, so the identifier has to be recovered another way: either captured before the WhatsApp button is clicked, or carried on the number the customer arrives on instead.
Does wa.me support UTM parameters?
No. wa.me is built to hand off a phone number and a pre-filled message, and other parameters attached to the same link, including standard UTM tags, don't carry through to the conversation on the other side.
Why do my WhatsApp leads show up as "unknown" in Google Ads?
Because the click identifier Google Ads attaches to a landing page visit doesn't survive the redirect into WhatsApp. By the time the conversation starts, there's nothing left in the message for Google to match the lead back to the ad that produced it.
Does click-to-WhatsApp advertising fix WhatsApp attribution?
For Meta's own ad formats, yes: a click identifier is included in the webhook payload when the conversation starts. That path doesn't extend to ads run on other platforms, including Google Ads, which is where the unknown-source problem shows up.
Should I put a form in front of my WhatsApp button to track conversions?
It's the one fix that can't be broken by a customer editing a message, because the click identifier is captured before they ever reach WhatsApp. But it also puts the exact friction back in front of the button that offering WhatsApp was meant to remove.