Menu
  1. Services
  2. Case studies
  3. Method
  4. Pricing
  5. About
  6. Contact

More pages

Get my free audit

Blog · Guide

How to track WhatsApp conversions from your ads

By Published 5 min read

Short answer

The pixel only sees the click. The sale happens inside WhatsApp, where it can't follow. To track it, save an ID for every chat (Meta's ctwa_clid, or your own code for the button on your site), mark the sale in your CRM and send it back to Meta and Google through their APIs or an offline import.

What can the pixel see, and what does it miss, when the sale happens on WhatsApp?

The Meta pixel and the Google tag live on your website. They see the visit, the product someone looked at and the tap on the green button. That’s where their view ends. Once the person opens WhatsApp, the conversation moves to another app, and the sale closes days later over chat or a bank transfer.

Click-to-WhatsApp ads make it harder, because a lot of people never touch your site. They go straight from the ad to the chat. Ads Manager reports conversations started, and that measures interest. To know which ad brings in money, you need to connect each conversation to its sale.

In the accounts I manage, I handle it with one simple rule: every conversation starts with a tag that says where it came from, and every sale goes back to the ad platform with that tag. The rest is plumbing.

Step 1: how do people get to your WhatsApp?

Almost always two ways, and you track them differently:

  • Click-to-WhatsApp ad (Meta). The chat opens right from Facebook or Instagram. Meta hands you a click ID inside the conversation.
  • WhatsApp button on your site. The person came from Google, Meta, TikTok or an email, browsed around and tapped the button. The click ID (GCLID, fbclid or your UTMs) stays in the browser, and you have to carry it into the chat.
The journey you need to track
  1. 1Ad click
  2. 2WhatsApp opens with its tag
  3. 3Sale marked in the CRM
  4. 4Sale goes back to Meta or Google

Step 2: save the ctwa_clid for every chat that comes from an ad

When someone messages you from a click-to-WhatsApp ad, the WhatsApp Business Platform sends a referral object in the message webhook. It includes the ad ID, the headline and a field called ctwa_clid, the ID for that click. You’ll find it in the messages webhook reference, which also notes that the ctwa_clid is left out when the ad ran in WhatsApp Status.

Your CRM or WhatsApp provider has to store that value with the conversation. When the chat turns into a sale, you send a Purchase event to Meta through the Conversions API with action_source: business_messaging, the ctwa_clid and the sale value. Meta walks through it in its Conversions API for Business Messaging guide, which also accepts events like LeadSubmitted, QualifiedLead and OrderShipped.

Two things from that same guide worth knowing up front:

  • The ctwa_clid comes through the WhatsApp Business API (Cloud API). If your team answers from the phone app with no CRM connected, you won’t see it.
  • If you don’t have the ctwa_clid (say, for older chats), you can send the phone number or email hashed with SHA-256. Meta accepts it, but it only attributes ad interactions from the past 7 days, and only in some countries, per the same docs.

Step 3: give every button click on your site a code

The button on your site has a different problem. The person shows up with a GCLID or an fbclid in the URL, but WhatsApp knows nothing about it. My go-to fix is a short reference code inside the message.

WhatsApp lets you build click-to-chat links with a pre-filled message, like wa.me/number?text=.... With a bit of JavaScript or Google Tag Manager, you build the link at the moment of the click, so the message reads something like “Hi, I’d like more info (ref. K7P2)”. At the same time, you save a row K7P2 in your database or a spreadsheet with the GCLID, the fbc (Meta’s click cookie), the UTMs and the landing page.

UTMs only help if you set them up right in the ad. Google recommends always using utm_source, utm_medium and utm_campaign, lowercase and with consistent names, in its campaign URL guide. When a chat comes in with “ref. K7P2”, your team or your CRM already knows the campaign and the ad.

Also track the button click as a conversion in GA4, Meta and Google Ads. Treat it as a secondary signal: it tells you someone wanted to talk, not that they bought.

Jean's tip

If the code in the message makes your sales team nervous, put it at the end in lowercase. People rarely delete it, and if they do, you lose that one sale for attribution. That’s it.

Step 4: mark the sale in your CRM and send it back to Meta and Google

Your CRM is where the pieces come together. Every contact needs to keep its source tag (the ctwa_clid, or the ref code with its GCLID and fbc) and a stage: conversation, qualified lead, sale. Without that column, none of the above works.

When a conversation becomes a sale, send it back:

  • To Meta, through the Conversions API. If it came from a click-to-WhatsApp ad, as a messaging event with the ctwa_clid. If it came from your site, as a server event with the fbc and the customer’s hashed info. If you want the full picture of how that API works and why the pixel alone falls short, I break it down in what Meta’s Conversions API is.
  • To Google Ads, with offline conversion import. Google gives you a GCLID for every click, and when the person buys you send that GCLID back with the date and value, per its offline conversions help page. These days it recommends doing it with enhanced conversions for leads, which add the hashed email or phone to the GCLID.

Watch the clock: Google only keeps the GCLID for 90 days, according to its page on offline import errors. If your sales cycle is long, upload sales every week instead of at the end of the quarter.

This is part of my measurement and tracking service: an audit of what you already have, the reference code, the CRM connection and the API setup for each platform.

What number do I watch while all this gets built?

Until the sale makes it back to the platform, the honest number is cost per conversation. That’s what I publish in my messaging case studies, because you can measure it without any integration.

979

WhatsApp conversations tracked in one Meta and Google account

Case 12 · jeanmorillo.com

The next level is counting qualified conversations, and the last one is the sale with its value. Each level gives Meta and Google better info to find people who buy, not just people who message. You can see how I run each type of account in my case studies, and if you want to know what your account is missing, grab a free audit. If a term sounds unfamiliar, it’s in the glossary.

FAQ

Does the Meta pixel track sales I close on WhatsApp?

No. The pixel lives on your website and sees the click on the button, but the chat and the sale happen inside the WhatsApp app. If you want Meta to know about the sale, you have to send it yourself through the Conversions API.

What's a ctwa_clid?

It's the click ID Meta attaches to the first message when someone comes from a click-to-WhatsApp ad. You get it in the WhatsApp Business Platform webhook and send it back to Meta along with the sale.

Can I use the WhatsApp Business app on my phone?

For chatting, sure. But the ctwa_clid comes through the WhatsApp Business API (Cloud API) webhook, so if you want to tie sales to ads you need a CRM or provider connected to that API.

How do I track my site's WhatsApp button in Google Ads?

Track the click as a secondary conversion, save the GCLID from that visit next to a code that travels in the message, and when the sale closes, import it into Google Ads as an offline conversion or with enhanced conversions for leads.

How long do I have to upload a sale to Google Ads?

Google keeps the GCLID for 90 days, so a sale that closes after that can't be tied back to the click.

Sources

  1. Conversions API for Business Messaging: Onboarding Guide, Meta for Developers
  2. Text messages webhook reference, Meta for Developers (WhatsApp Business Platform)
  3. About offline conversion imports, Google Ads Help
  4. About enhanced conversions for leads, Google Ads Help
  5. Fix discrepancies and errors in offline conversion imports, Google Ads Help
  6. URL builders: Collect campaign data with custom URLs, Google Analytics Help
  7. How to use click to chat, WhatsApp Help Center

Want this working in your account?

I start with a free audit: I review your account and your tracking, and tell you what I'd change first.

Get my free auditSee: Measurement & tracking

Keep reading