Your sales close in chat, but Ads Manager cannot see them. I connect every sale that closes in WhatsApp, Messenger or Instagram back to the Meta ad that started the conversation, using the Conversions API for business messaging.
Everything happens in writing. No calls, no meetings.
Click-to-WhatsApp adreferral.ctwa_clid savedlead stored with the click IDPurchase sent to the Conversions APIconversion reported to MetaMost broken setups fail in one of three places. The ad works, the chat works, but the link between them is lost.
ctwa_clid arrives only in the referral object of the first message after the ad click. If it is not stored then, later sales cannot be tied to the ad.
Each WhatsApp Business Account, Page and Instagram account has its own dataset. An event sent to the wrong one is received but never matched.
A wrong action_source, a missing messaging_channel, a hashed click ID or web fields in a chat event can each cause a rejection or a silent miss.
A complete path from the first message to a reported conversion, built around the tools you already use.
Your webhook reads ctwa_clid from the first message and stores it with the lead, exactly as it arrived, never hashed.
Lead and Purchase events sent with action_source set to business_messaging, the right channel and the right IDs for each one.
Works with your existing CRM or custom panel, or a small connector when there is none.
Page scoped and Instagram sender IDs mapped per channel, so one template does not break the other.
Verified with test events in Events Manager, plus written notes on what was built and where.
Async from start to finish. You always know what happens next, in writing.
Your WhatsApp provider, CRM and the events you want to report.
What will change, what it costs and when it will be ready.
Implemented and confirmed with test events before anything goes live.
Written documentation, with optional monthly maintenance.
WhatsApp is rolling out usernames and Business-Scoped User IDs (BSUIDs), so a customer's phone number can be missing from your webhook. Meta's Conversions API event for Click-to-WhatsApp is keyed on the click ID and your WhatsApp Business Account ID, not on the phone number. The risk sits in your own webhook, CRM and deduplication logic.
I check all of this as part of the setup. For the full breakdown, read the WhatsApp BSUID checklist for CTWA and CAPI.
Not sure? Start with a Meta attribution audit.
No. It needs the WhatsApp Business Platform, either the Cloud API or a provider built on it. The Business app alone has no webhooks, so the click ID never reaches your system.
Yes. Messenger events use page_id and page_scoped_user_id. Instagram events use instagram_business_account_id and the sender's ig_sid. Each channel gets its own correct fields.
Usually not. I work with the CRM or panel you already use. If it cannot send events, a small connector can be added.
No. Only conversations that start from an ad carry a click ID, and Meta makes the final attribution decision. The setup makes sure every eligible sale is sent correctly.
No. After we agree on the scope, access is given through Meta's own invites. Passwords and access tokens are never shared in messages.
It depends on the channels, your CRM and the events you want to report. Send a short description of your setup and you get a written quote. Monthly maintenance is available after handover.
Meta's own reference: Conversions API for business messaging.
Describe your setup in a few lines. You get a written plan and a quote, with no calls.