How to Track WhatsApp Leads from Google Ads: Step-by-Step Setup
Setup guide · Tracking
How to Track WhatsApp Leads from Google Ads: Step-by-Step Setup
In the UAE, many B2B buyers would rather send a WhatsApp message than fill in a form. That’s good for sales and bad for measurement: the chat happens inside WhatsApp, so Google Ads never sees it. This guide shows how to connect each WhatsApp chat back to the ad click that produced it, so you can see which campaigns bring real leads and teach Google Ads to find more of them.
Why WhatsApp leads go missing
When someone fills in a form on your website, Google Ads can record a conversion. When they tap a WhatsApp button, the conversation moves to WhatsApp. Your sales team sees the lead; Google Ads only sees a click on a link, if anything.
The result: campaigns that bring good WhatsApp leads look weak, and automated bidding learns from the wrong signals. If WhatsApp is a large share of your enquiries, this alone can make Google Ads look like it doesn’t work.
Save the Google click ID when a visitor arrives. Give each WhatsApp chat a short reference code linked to that click ID. When a chat turns into a real lead, upload the click ID back to Google Ads as a conversion.
How the method works
- A buyer clicks your ad. Google adds a click ID (GCLID) to the page address.
- Your page saves the click ID in the browser.
- The buyer taps WhatsApp. The message opens pre-filled with a reference code, such as VG-7K2Q9A.
- Your page logs the reference code together with the click ID.
- Your sales team records what happened to that reference: qualified, quoted, won.
- You upload the click IDs of the qualified leads to Google Ads.
This is the same idea as offline conversion import for phone and CRM leads, explained in our guide to tracking enquiries to quotations. Here we focus on the WhatsApp setup.
Step 1: Capture the click ID
Make sure auto-tagging is turned on in your Google Ads account, so Google adds the GCLID to every ad click [1]. On your landing pages, add a small script that reads the click ID from the page address and saves it in the browser, so it’s still available if the visitor moves to another page.
- Save gclid, and also gbraid and wbraid, which Google uses for some iPhone traffic.
- Keep it for up to 90 days. Google only keeps the GCLID for 90 days, so older clicks can’t be uploaded anyway [2].
- Store the value exactly as received. The GCLID is case sensitive [1].
Step 2: Add a reference code to the WhatsApp message
When the visitor taps your WhatsApp button, generate a short random code and add it to the pre-filled message, for example: “Hello, I found you on Google and would like a quotation. (Ref: VG-7K2Q9A)”. Most people send the message as it is, so the code arrives with the first message your team receives.
Use a wa.me link with a text parameter, and set the link when the button is tapped so each visitor gets a fresh code.
Step 3: Log the click with its reference
At the moment of the tap, save the reference code, the click ID, the page and the time somewhere you can look them up later. Practical options:
- A Google Sheet, through a small web script
- Your CRM, if it accepts incoming data
- Your analytics tool, as event parameters (useful for reports, but harder to look up one by one)
Without this log, the reference code in the chat can’t be matched to a click.
Want this set up properly?
We build WhatsApp tracking into every landing page we make.
Step 4: Track the click in Google Tag Manager and GA4
Send an event to the data layer when the WhatsApp button is tapped, for example whatsapp_click with the reference and click type as parameters. Then in Google Tag Manager:
- Create a Custom Event trigger for that event name.
- Add a GA4 event tag that sends the event with the reference as a parameter, and register it as a custom dimension in GA4.
- Optionally add a Google Ads conversion tag for WhatsApp clicks. Set it as a secondary conversion, because a tap is not yet a lead.
Now you can see WhatsApp taps by campaign, keyword and page in GA4 and Google Ads.
Step 5: Record what happened to each chat
This is the step most companies skip, and the one that matters most. When a WhatsApp chat arrives, your team notes the reference code and, later, the outcome:
| Reference | Outcome | Date | Value (optional) |
|---|---|---|---|
| VG-7K2Q9A | Qualified lead | 10 Nov 2026 | – |
| VG-3M8T1C | Quotation sent | 12 Nov 2026 | AED 85,000 |
| VG-9P4W2D | Not relevant | 10 Nov 2026 | – |
A shared sheet works fine. Keep it simple enough that your team will actually fill it in.
Step 6: Upload qualified leads to Google Ads
- In Google Ads, create a new conversion action of the type import from clicks, for example “Qualified WhatsApp lead”. Wait four to six hours before the first upload; uploads in the first hours can take two days to appear [1].
- Match each qualified reference to its click ID using your log from step 3.
- Upload a file with the click ID, conversion name, conversion time and, if you use it, value and currency.
- Upload regularly. Google recommends at least daily, or on a consistent schedule such as weekly [2].
Once Google Ads receives these, you can make qualified leads your main conversion, so bidding optimises for real leads rather than taps.
A note on enhanced conversions for leads. Google now recommends enhanced conversions for leads, which match on hashed email or phone captured from your website forms, over classic click ID imports [3]. It’s a good choice for form leads. For WhatsApp taps, where the visitor doesn’t type a phone number on your site, the click ID method above remains the practical route, and the two can run side by side.
Common mistakes
- Counting every tap as a conversion. Taps include accidental clicks and people who never send a message. Use taps as a secondary signal only.
- Not logging the click ID with the reference. Without the log, there’s nothing to upload.
- Waiting too long. Clicks older than 90 days can’t be uploaded. Upload a qualified-lead milestone early, rather than waiting for the deal to close.
- Changing the click ID. Don’t trim, lowercase or edit it.
- Time zone errors. A conversion time earlier than the click is rejected. Check the time zone in your upload file [4].
Frequently asked questions
Do we need the WhatsApp Business API for this?
No. The method works with the normal WhatsApp Business app, because the reference code is in the message and the matching happens in your log and sales sheet.
What if the customer deletes the reference code?
Some will. You can still match many chats by time and page, but those will be fewer. Most people send the pre-filled message unchanged.
Can we track phone calls the same way?
Calls from ads can be tracked directly in Google Ads, and website calls with call tracking. The upload step for qualified calls is the same.
How often should we upload?
Daily is best, weekly is acceptable. What matters is a regular schedule and uploading within 90 days of the click.
Sources
- [1] Google Ads Help, Set up offline conversions using Google Click ID (GCLID)
- [2] Google Ads Help, Offline conversion imports FAQs
- [3] Google Ads Help, About enhanced conversions for leads
- [4] Google Ads Help, Fix discrepancies and errors in offline conversion imports
Facts checked 10 November 2026. Google changes conversion import options often; check the current steps in your account.