How to Track Which Ads Bring WhatsApp Buyers

To track which ads bring WhatsApp customers, read the referral object that WhatsApp attaches to messages from Click-to-WhatsApp ads, save its ad ID and click ID against the contact, and report each sale back to Meta through the Conversions API. That way you can link a sale in a chat to the ad that started it, and Meta can see it too.

Ads Manager on its own shows chats started, not who bought. This guide explains what data you get, how to use it with or without a developer, where UTM tags fall short, and exactly what you’ll see in Automate AI.

Why tracking WhatsApp ads is harder than a website

On a website, a pixel watches the visitor from click to checkout. A chat has no pixel. The customer taps the ad, WhatsApp opens, and everything after that happens in a conversation your ad reports don’t show, often ending in a payment link or a shop visit.

So there are two jobs. The first is attribution for you: knowing which ad each customer came from. The second is feedback to Meta: telling it which clicks became sales, so it has more to learn from than chats started. The sections below cover both. For how to set up these ads in the first place, see Click-to-WhatsApp ads.

What the referral object contains

When someone messages you from a Click-to-WhatsApp ad, Meta’s messages webhook includes a referral object. Meta says it’s only included for messages sent via one of these ads. Its main fields are:

There’s no referral on an ordinary message, so a customer who saves your number and writes a week later looks like anyone else. The chat that came from the ad is the one that counts. To see the field in a real webhook, see WhatsApp Cloud API webhooks.

Three ways to attribute chats to ads

On the WhatsApp Business app, you have no webhook, so you’re limited to the last two. Moving to the API is what gives you the first. See what the WhatsApp Business API is.

Prefilled messages: the simple backup

Every Click-to-WhatsApp ad can set the text that appears in the customer’s message box. Meta’s default is “Hello! Can I get more info on this?”, and you can change it. Automate AI’s ad form has a box for it too, up to 120 characters. Give each ad its own wording:

Your team can now read the source from the first line, and you can count these messages by hand. In a chatbot, one keyword in each prefilled message can start a matching flow. In Automate AI, keywords work word by word, so use a distinct word such as “SUMMER”.

Two limits: the customer can edit the text before sending, and it tells you nothing about what the ad cost. It’s a good backup for the referral data, not a replacement. For help writing them, see generating quality leads with WhatsApp ads.

Where UTM tags fall short

UTM tags are made for websites. They sit on a link, and your analytics reads them when the page loads. A Click-to-WhatsApp ad doesn’t load a page, so there’s nothing to read them, and WhatsApp messages don’t pass tags to your analytics.

• Ad straight to WhatsApp: UTM tags do nothing. Use the referral object.
• Ad to a landing page, then a WhatsApp button: UTMs tell you who reached the page, and how many clicked the button. They don’t tell you who bought, and these chats don’t carry a referral, since Meta only adds it to messages sent from the ad itself.
• Payment or product link inside the chat: you can tag this link, for example utm_source=whatsapp. That shows sales from WhatsApp as a whole in your analytics, but not which ad started the chat.

To link a landing page visit to a chat, some teams put a short code in the prefilled message on the WhatsApp button. It’s the same idea as above, and the same limit applies.

Report sales back with the Conversions API

Meta’s Conversions API accepts business messaging events, so a sale in a chat can be reported back to Meta, which says this helps with optimisation and understanding ad performance. In outline, for developers:

1. Save ctwa_clid with the conversation when the first message arrives. Meta calls it a personal identifier that’s unique per click, so store it with care.
2. Get the dataset for your WhatsApp Business Account through the Dataset API.
3. When a sale happens, post an event to /{DATASET_ID}/events with action_source set to business_messaging, messaging_channel set to whatsapp, and ctwa_clid and whatsapp_business_account_id in user_data.
4. Remove duplicates yourself. Meta says it doesn’t deduplicate events for this API.

Events for business messaging include Purchase, LeadSubmitted, QualifiedLead, AddToCart and OrderCreated, and Meta says they should only represent things that happened in the messaging thread. Two limits matter:

• The 7-day limit on event_time. Meta rejects a request if any event’s time is more than 7 days in the past, so send events soon after they happen.
• No click ID: there’s a fallback using hashed customer details, but it needs page_id, covers only some countries, and only credits ad interactions from the past seven days. Matches aren’t certain, so send ctwa_clid when you have it.

Meta also has automatic events, where it analyses new chats from these ads, detects leads and purchases, and sends a webhook. Businesses must opt in, it isn’t available in the EU, UK, Japan or South Korea, and Automate AI doesn’t use it, so its events come from what you do in the app.

What you see in Automate AI

Automate AI reads the referral on every incoming message. If the message has a ctwa_clid, it saves the click ID and ad ID on the contact, and keeps a history of ad clicks, so a customer who returns through a new ad counts as last touch on that ad. Here’s what that gives you on screen, and what it doesn’t:

“Chats started” and “spent” come from Meta. “New contacts” is Automate AI’s own count of people whose message carried that ad’s ID. Despite the name, existing contacts who tap the ad count too, and someone who taps two ads counts under both. If you create ads under Click-to-WhatsApp Ads, that gives you a quick cost-per-contact check. For example, with made-up numbers: ₹6,000 spent and 40 contacts from the ad is ₹150 each.

If your ads run in Ads Manager, the ad data is still captured and the Conversions API still works. You just won’t have a per-ad list in the app, so use the prefilled message trick to show your team the source, and check events in Events Manager.

Sending results back to Meta

Set up Integrations › Conversions API: it needs a dataset plus your WhatsApp connection or a pasted token, and the main Enabled switch starts off. Each event only goes out for contacts who came from an ad:

Status and Purchase events respect an attribution window you set, 7 days by default and up to 90, so an old click doesn’t get the credit. If you sell in person or by bank transfer, the status route is the one to use: when a salesperson moves a chat to “Won”, Meta gets the event. That makes honest statuses important.

A simple tracking routine

1. Name ads clearly so an ad ID leads to something a person understands.
2. Give each ad its own prefilled message as a backup.
3. Pick your stages. Keep it to Lead, Qualified and Won, as statuses your team uses.
4. Map those statuses to Meta events: Lead to Lead, Won to Purchase, and Qualified to a custom event such as QualifiedLead. Send a test event with a test code first.
5. Check once a week: cost per contact from the ad, qualified leads, and sales per ad if you track them yourself, for example from your own ad IDs or prefilled messages.
6. Move budget slowly, and give an ad time before judging it. Sales in chats can take days.

Don’t expect the numbers to match perfectly. Meta counts chats, you count contacts, and returning customers or Status ads will appear differently. Use the numbers to compare ads with each other, not as exact accounts. For the bigger picture, see Click-to-WhatsApp ads vs website vs lead forms.