GoHighLevel Google Ads Conversion Tracking: Forms, GCLID and Enhanced Conversions
GoHighLevel (GHL) is great at capturing and nurturing leads. It is less great at telling Google Ads which ads produced them. The usual result is a Google Ads account that reports far fewer conversions than the CRM shows, or the opposite: one lead counted two or three times.
This guide covers how to track GoHighLevel leads in Google Ads properly: where the conversion should be counted, how to keep the click ID, and what to do about Enhanced Conversions.
Why GoHighLevel tracking breaks
Most problems come from four places:
- Forms embedded in an iframe. When a GHL form sits on your own website as an embed, it runs inside an iframe from another domain. Tags on your page can’t see what happens inside it, so “form submitted” never reaches Google Tag Manager.
- Lost click IDs. The
gclid(orgbraid/wbraidon some iOS traffic) is in the landing page URL. If the visitor moves to another page, or the form lives on a different domain, the ID is gone unless something stores it. - Two systems counting the same lead. A thank-you page tag in Google Ads plus a CRM-based conversion from GHL, both set as primary, means every lead is counted twice.
- Thank-you pages that can be reloaded. Page-view based conversions fire again on every refresh or revisit.
Step 1: Decide where the conversion is counted
Pick one primary source of truth for each conversion.
| Option | How it works | Best for |
|---|---|---|
| Website tag (GTM or Google tag) | A conversion fires when the form succeeds or the thank-you page loads | Fast setup, real-time data |
| CRM-based (offline) conversion | GHL sends the conversion when a contact reaches a stage (for example “Booked” or “Won”) | Optimising for quality leads, not form fills |
Many accounts use both, but in different roles: the website lead as a secondary conversion for reporting, and the CRM stage (qualified lead, booked appointment, sale) as the primary conversion that Smart Bidding optimises toward.
Step 2: Keep the click ID with the lead
Whichever option you choose, the click ID has to reach the GHL contact record.
- Store it on landing. Save
gclid,gbraidandwbraidfrom the URL into a first-party cookie or local storage when the visitor arrives, so they survive page changes. - Pass it into the form. Add hidden fields for the click IDs (and UTM parameters) to your GHL form and fill them from storage, or append them to the form’s URL so GHL can read them.
- Check the contact. Submit a test with
?gclid=test123on the landing URL and confirm the value appears on the contact in GHL.
If the form is on a GHL funnel page, add your tracking code through the funnel’s settings (header tracking code), so the same storage script runs there too.
Step 3: Track the form submission correctly
If the form is on a GHL funnel or website page
You control the page, so you can load Google Tag Manager in the funnel’s tracking code and trigger the conversion on the thank-you step only. Make the thank-you step reachable only after submitting (not linked from anywhere else) to reduce false fires.
If the GHL form is embedded on your own website
Because the form is in an iframe, use one of these:
- Redirect to a thank-you page on your own domain after submission, and fire the conversion there. Simple and reliable.
- Load GTM inside the form/funnel as well, and fire the conversion from within the iframe’s page.
Avoid putting the visitor’s email or phone into the thank-you page URL to “pass” data across. Personal data in URLs ends up in analytics reports and breaks Google’s policies.
Step 4: Send CRM stages back to Google Ads
To let Google Ads optimise for real outcomes, send pipeline stages back as conversions:
- In Google Ads, create an Import conversion action per stage you care about (for example “GHL – Appointment booked”, “GHL – Sale”).
- Send conversions from GHL when a contact reaches that stage, including the stored click ID, the conversion time with time zone, and a value. Depending on your account this can be done with HighLevel’s built-in Google Ads options, a webhook to an automation tool, or a scheduled upload.
- Set the stage you want to optimise for as primary, and make the website form conversion secondary.
If you’d rather have this built for you, see Google Ads offline conversion tracking.
What about Enhanced Conversions?
Enhanced Conversions improve matching by sending a hashed email or phone number with the conversion. With GHL there is a catch: when the form is in an iframe, your page’s Google tag can’t read the email field. A request on HighLevel’s own ideas board describes exactly this limitation.
Workable options:
- Fire the Google tag inside the GHL page where the form lives, so it can read the fields directly.
- Use Enhanced Conversions for Leads on the CRM side: send the hashed email with the stage conversion from GHL instead of from the browser. This doesn’t depend on the iframe at all.
Normalise before hashing (lowercase, trimmed email; phone with country code). The free Customer Data Hasher shows the exact value Google expects.
Test before you trust it
- A test lead with
?gclid=test123shows the click ID on the GHL contact - The website conversion fires once per submission (check with Tag Assistant)
- Reloading the thank-you page doesn’t create a second conversion
- Only one conversion per outcome is set to primary in Google Ads
- A test stage conversion appears in Google Ads (allow a few hours)
Need it done for you?
GoHighLevel tracking touches forms, funnels, workflows and Google Ads settings at once, which is why it so often breaks quietly. If you want it set up and verified end to end, see my Google Ads conversion tracking repair service or book a free tracking audit.
Need this implemented, audited, or white-labeled?
Whether you are an eCommerce brand owner fixing signal loss or a digital marketing agency needing a senior analytics engineer under strict NDA, I deliver 24–48h SLA turnaround with 8.5+ EMQ match rates.


