If you run Meta Click to WhatsApp ads, DM Champ tells you which ad each WhatsApp lead came from and hands you the Meta click identifier you need to report real conversions back. Your campaigns can then optimise for sales and bookings, not just for chats started.
How it worksWhat the setup actually looks like, from the connection screen to the first booking or record the AI handles in Meta Click-to-WhatsApp Ads.
Meta attaches hidden referral information to that first WhatsApp message. DM Champ reads it and stores it on the contact as ad_referral. There is nothing to switch on.
As the lead progresses, booked a call, became a customer, was lost, apply a tag. Your AI Agent can tag the contact during the conversation using auto-tagging rules, or you can tag by hand from Chats or the Contacts page.
Applying a tag fires the contact tags updated event, and that payload includes the contact's ad_referral. Set the webhook URL on the tag itself, in the Tags tab of the agent or campaign the contact belongs to.
Your automation tool, Zapier, Make or Pabbly, receives the outcome plus the click id and calls Meta's Conversions API using business messaging as the action source, or Google Ads offline conversion import.
Every screen and field is covered in the setup guide: Meta Click-to-WhatsApp Ads documentation.
What gets capturedWhen someone taps a Click to WhatsApp ad and messages your business, Meta attaches hidden referral information to that first message. DM Champ reads it automatically and stores it on the contact as ad_referral, with no setup and no configuration on your side. The source type tells you whether the click came from a paid Click to WhatsApp ad or an organic Facebook or Instagram post, and the click identifier is empty for organic posts because Meta does not issue one. The channel is currently always WhatsApp.
Which connectionMeta only delivers the structured referral information, including the click identifier, through the official WhatsApp Business API. The non-official WhatsApp web connection does not receive it, by design of how that connection works, so there is no ad click data available there at all. If closed-loop ad attribution matters to you, run your Click to WhatsApp campaigns through a number connected via the official WhatsApp API.
First touchThe referral is captured on the first message a contact sends from an ad. If that same contact later clicks a different ad and the newer click carries a click identifier, the stored ad_referral is refreshed so your reporting uses the current one. Organic post referrals carry no click identifier and never overwrite a paid ad click id that was captured earlier.
Closing the loopReporting a conversion needs two things: the click id, which is captured for you, and the outcome, which you set. Tags are the most reliable way to attach that outcome, because applying a tag fires the contact tags updated webhook and that payload includes the contact's ad_referral. Removing a tag does not fire it. The webhook URL lives on the tag itself, in the Tags tab of the agent or campaign, not in Settings, and every tag can point at the same endpoint if you want one place to receive everything.
LimitsDM Champ captures the attribution data and exposes it, but it does not push conversions to Meta or Google for you today. You forward them with webhooks plus an automation tool. Attribution is also captured going forward only, from the moment it is live, and cannot be backfilled onto conversations that already happened. If you want a native integration, tell support at [email protected].
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.