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
R
Ricardo Nascimento Maia
It would be great
H
Henrique Pessoa Cançado
We need this functionality in over 100 sub-accounts
W
Waldeir Rodrigues Colares
Come on, I need this
P
Pedro Valentim
I NEED THIS, ITS SO SIMPLES TO BE DEVELOPED
PLEASE!
D
Denis Arceda
Hello, I'm going to save you 1500 to 3000 dollars. I confirm that this can be done within GHL, although not natively. Initially I tried to pay third parties “experts” in GHL to build it but no one really showed me evidence of having implemented it before, so I had to do it on my own to be able to improve my click to WhatsApp ads and pass this valuable data to the goal to optimize messaging campaigns. The implementation has been successful, this may take you a couple of days to do it with the assistance of Chat Gpt, Copilot, Claude or whatever AI you use.
What is needed:
- You have to use a number that is your own and not purchased at GHL.
- Doing the job and not being Webon.
I'll leave a summary of how to do it on your own while GHL adds it natively:
SENDING CLICK-TO-WHATSAPP EVENTS
GHL + Make + Meta CAPI Business Messaging
.Implemented architecture
Click-to-WhatsApp ad
→ Customer writes on WhatsApp
→ GHL captures the ctwa_clid, (save in contact fields)
→ Advisor registers Lead or Purchase
→ GHL Workflow validates data
→ Webhook to Make
→ Make builds the payload (do one scenario per event)
→ Meta CAPI Business Messaging hosts the event
→ Events Manager confirms reception
→ Ads Manager attributes when appropriate
GHL Responsible for:
Capture and preserve the ctwa_clid.
Save Purchase Fee.
Trigger the webhook.
Make Responsible for:
Receive the GHL webhook.
Transform data.
Build the JSON.
Generate the timestamp.
Send the payload to the Dataset endpoint.
Record technical errors.
Recover executions using Incomplete Executions and Retry.
Responsible Goal of:
Receive the event.
Validate the payload.
Relate it to WABA, Dataset and ctwa_clid.
Apply attribution.
Deduplicate according to your internal mechanisms.
Use the signal for advertising optimization.
Advanced idempotence was not implemented, in general that's overengineering.
b
businessmeteo m
GHL is now capturing the ctwa_clid but how to send the data back to Meta? GHL's native Conversion API isn't able to send ctwa_clid. Can anyone help?
L
Louis Duchesne
Hello, today we made the difficult decision to retire from go high level. Since it is not possible in any way to optimize our WhatsApp campaigns, which is the main way in which we attract customers.
Great CRM but if it's not on the cutting edge, it's no use.
I decided to move my entire service
J
Jordy Vizuete
It's been more than a year, this is urgent
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 ?
Load More
→