Ad Click Attribution for WhatsApp Know Which Ad Started Each Chat
If you run Meta or Google ads to a page on your own website with a WhatsApp button, DM Champ tells you which ad click each WhatsApp conversation came from. You paste one small script on your site, a short enquiry number is added to the visitor's message, and the contact shows the campaign it came from. The click data travels with the contact into webhooks, the API and, if you want, back to Meta.
How it worksConnecting Meta and Google Ads Step by Step
What the setup actually looks like, from the connection screen to the first booking or record the AI handles in Meta and Google Ads.
- 01Get your script
Go to Settings, Ad click tracking, in the Integrations group, and click Turn on and get my script. Your account gets its own site key and a one line script.
- 02Paste it on your website
Paste the script just before the closing body tag on every page that has a WhatsApp button. Optionally type the WhatsApp number your buttons link to, so only links to that number are tracked.
- 03A visitor taps your WhatsApp button
The script adds a short enquiry number to the message, records the visit with the ad click ids and campaign tags, and lets the tap continue to WhatsApp as normal. Nothing is sent before the tap.
- 04The first message is matched to the click
When the contact's first message arrives, DM Champ matches it to the visit by enquiry number first, otherwise by identical text, and the contact panel shows Came from an ad click with the campaign.
- 05Optionally report results to Meta
Enter your own Meta pixel or dataset ID and access token, then pick a Meta event on an agent tag. Whenever that tag is applied, the event goes to Meta with the contact's click data.
Every screen and field is covered in the setup guide: Meta and Google Ads documentation.
The collision fixAn Enquiry Number, Not a Tracking Code
A short number, like the reference a shop or clinic gives you, is added to the visitor's WhatsApp message. It is how DM Champ knows exactly which ad click belongs to which conversation, even when two visitors send the same quiz answers. You choose the wording and where it sits, and the settings page shows a live preview.
- Enquiry no. by default, or any one line of text that fits your business, such as Booking ref or Ref
- On its own last line by default, or at the end of the text
- 4 digits, or 5 when your site is very busy
- Your AI agent never sees it and never repeats it; the inbox shows the full message
- You can switch it off, and matching then only works on the text of the message
What gets recordedThe Click Data On the Contact
At the tap the script records the visit. When it is matched, a copy of the click data is stored on the contact and stays there until you delete it. The script sets no cookie, loads nothing else and only sends something when a visitor taps a WhatsApp button.
- Meta's fbclid and Google's gclid, gbraid and wbraid from the page address
- The _fbc and _fbp cookies, if your own Meta pixel set them on your site
- The campaign tags utm_source, utm_medium, utm_campaign, utm_content and utm_term
- The landing page, the page the visitor came from, the browser and the message text
- The IP address and the time, added when the visit arrives
Where you see itIn the Inbox and Everywhere the Contact Goes
The contact panel shows Came from an ad click with the campaign or source and the date. The same click data rides along on agent tag webhooks, on every webhook subscription event that carries a contact, on the contacts API and on the MCP tools, so your CRM or reporting gets it without extra work.
Send results to MetaLead and Purchase Events On Your Own Conversions API
With your own Meta Conversions API details, DM Champ reports outcomes back to your Meta ad account so Meta learns which ads bring real leads and sales. You pick the event per agent tag: Lead, Contact, Schedule, Purchase or a custom name, with an optional value and currency. When the tag is applied, by the AI, by hand, through the API or by an automation, the event goes to Meta with the stored click data plus the contact's phone, email and name, hashed.
- Each event has a fixed id, so the same event sent by your CRM is only counted once
- A contact without a match still sends the event, with only the hashed phone, email and name
Worth knowingThe Limits, Stated Up Front
Matching is deliberately strict, so a contact is never credited to the wrong ad.
- WhatsApp only: the WhatsApp Business API and WhatsApp Web channels
- The first message has to arrive within 15 minutes of the tap
- First match wins and is never overwritten
- Going forward only: contacts from before you installed the script have no match
- Meta credits an event to an ad only inside its attribution window, 7 days after the click by default, so also send an earlier event such as a booked consultation
- The script runs on your website, so your website's privacy notice should mention what it records
Frequently Asked.
Meet the Closer. Then Decide.
The same AI agent that closes $40K deals in DMs is one click away. No signup, no demo call: open the chat, push back, see if you can break it.
