Capturing ctwa_clid for Click-to-WhatsApp campaign attribution
L
Lucas B
I hope you’re doing well. My name is Lucas, and I’m using GoHighLevel to manage conversations and leads from Facebook Ads campaigns that use the “Click to WhatsApp” (CTWA) format.
I’ve noticed that when a WhatsApp message is received through these campaigns, the GoHighLevel platform does not relay (or expose) the ctwa_clid parameter in the webhook payload nor in the contact’s record. This parameter is essential for tracking and attributing conversions accurately, as it’s the unique identifier Facebook assigns to trace back the specific origin of the interaction.
To provide more context, I’m using the webhook set up in the GoHighLevel developer platform (under the “API” section). However, the payload coming through to my webhook after the inbound message event does not include any referral details or parameters like ctwa_clid.
I’d like to know:
Is there an existing or upcoming feature that allows GoHighLevel to automatically capture the ctwa_clid when a user initiates a conversation from a Click-to-WhatsApp ad, and then pass it through to webhooks or other integration points?
If not, is there any workaround or recommended approach (e.g., a landing page, custom fields, or advanced configuration) to help retrieve this parameter and store it within GoHighLevel?
Are there any future plans to enhance the attribution and tracking of WhatsApp campaigns within GoHighLevel’s dashboard, allowing us to measure the performance of Facebook Ads more precisely and optimize our ad spend?
Having native support or at least a method to receive the ctwa_clid in GoHighLevel would greatly improve our ability to track ROI on WhatsApp ad campaigns and automate our follow-up processes.
Thank you very much for your assistance, and I look forward to your response.
Best regards,
Lucas Borthiry
One South Media
Log In
F
Fernando Garza
Upvoting this — and adding what GHL Support just confirmed to me in writing: this is a known platform-wide limitation for ALL accounts ("WhatsApp click to Ads are relatively new to GoHighLevel and we haven't added features for correct conversions"), with no ETA — it's on the roadmap for "an upcoming quarter" with no commitment.
One clarification that may help others here: the ctwa_clid IS actually exposed today at contact.attributionSource.ctwaClid, and workflow webhooks can forward it. But that only gets you halfway. The real blocker is deeper:
Since GoHighLevel is the BSP that owns the WhatsApp Business Account, the WABA is not associated with the advertiser's Meta dataset. So when you send conversion events (Schedule, Purchase) back to Meta via the Conversions API with action_source: business_messaging + ctwa_clid, Meta rejects them with error 2804132 ("WhatsApp Business Account not associated with the dataset"). And there's nothing the advertiser can do — we don't own the WABA, so we can't create the association ourselves.
The consequence: Click-to-WhatsApp campaigns run through GHL can never be optimized for real conversions — only for "conversations" — which means low-quality leads and unmeasurable ROAS for every advertiser using this format.
What we need: a way to associate our WABA with our own Meta dataset (per sub-account), or have GHL forward conversion events natively. WhatsApp is THE channel in Latin America and Meta is investing heavily in click-to-message ad formats — this wall affects every GHL agency outside the US.
A
Albert Ivan Apaza Gonzales
news ?
N
Nathan Santana
WE NEED IT PLEASE.
A
Anibal Unda
URGENT!!!! An integration with N8N must be done or simply change the crm. Please enable
L
Leonardo Carvajal
Is there a way for them to enable this urgently? WE NEED IT PLEASE.
S
Shawn Kimmel
Would like to see this supported very soon
J
Joel acuña
We need it urgently
T
Toolyx AI
We need