Meta ads that end on WhatsApp are hard to report. The click leaves Ads Manager. The chat starts on WhatsApp. Those two systems do not share a row.
WhatsAble passes the referral through to your custom webhook and to n8n, Make, and Zapier triggers. Persist ctwa_clid and source_id on that first inbound, then write those two values to a Sheet or a CRM. Then you can see which creative produced the chat.
WhatsAble does not create the ad. Run the ad in Meta Ads.
Why the report breaks
A Click-to-WhatsApp ad is a Meta ad. The lead taps it and writes you on WhatsApp. Ads Manager sees the click. WhatsApp sees the chat. Without the referral on that first inbound, you cannot join the two.
This page is the opportunity. The sibling Click-to-WhatsApp ads page owns the field table.
How do I catch the first inbound?
In the WhatsAble dashboard, open Developer, add an endpoint URL, and enable incoming. The first Click-to-WhatsApp inbound POSTs the referral to that URL.
https://whatsable.app/integrations/webhook
n8n, Make, and Zapier triggers get the same referral. Map top-level referral on that inbound.
https://whatsable.app/integrations/n8n
https://whatsable.app/integrations/make
https://whatsable.app/integrations/zapier
An Agent Skill is not a separate event. It sees the same Message webhooks payload, including the referral, only if that skill is on a webhook you created. Installing skills alone does not deliver it.
https://whatsable.app/vibe-code
Typically only the first inbound after the ad click includes the referral. Later messages in the same chat usually omit it. Persist ctwa_clid and source_id immediately.
What can I build with that referral?
A sales inbox that already knows the ad. The first inbound writes source_id onto the contact in the CRM you already use. This page does not invent CRM clicks.
A weekly sheet you can report from. The same inbound appends ctwa_clid and source_id. No invented Sheet buttons. Group the week by ad and see which creative produced chats.
A pause decision that is not a vibe. If one ad starts chats and another does not, you take that back to Meta Ads. The automation did not create the ad. It only kept the id.
What this is not
This is not a WhatsAble ad-creation product. It is not a wa.me, QR, or widget path, and it is not inbox compose. It is not a 72-hour window as a WhatsAble feature, and it is not a second field spec.