Capture the GCLID in GoHighLevel for Google Ads offline conversions
If you cannot connect a GoHighLevel contact to the Google Ads click that produced it, you cannot reliably report that contact as an offline conversion. This guide explains how to preserve the GCLID from the landing visit, write it into a form submission, store it on the contact, and then use it for offline conversion reporting.
Why the click ID is lost without early capture
Google Ads can generate leads, but lead volume alone does not show which campaigns produce paying customers. The missing link is usually the click identifier. When a visitor arrives from an ad, that identifier is present in the landing URL. If it is not saved at that moment, it is gone by the time the visitor reaches a contact form on another page.
Four steps from landing visit to stored contact
- Install the capture snippet on the website, through site settings or a tag manager, and add a hidden GCLID field to each lead form. The hidden field is the destination the tool writes to; visitors do not need to see or complete it.
- On arrival from a Google Ad, the tool reads the GCLID from the URL and stores it in the visitor's browser.
- When a form is submitted, the stored value is populated into the hidden field and captured by the form tool with the other submitted details.
- Pass that submission to GoHighLevel through the form tool's native integration, or through Zapier or Make, so the GCLID is stored on the new contact.
Pre-flight checklist
Checklist before you rely on the data: the snippet loads on every page where a lead form can be reached; every form has the hidden field; a test submission from a URL containing a GCLID creates a contact with that value; a submission after browsing to a second page still carries the original value; and the value is mapped to a dedicated contact field rather than overwritten by later visits.
Send the stored GCLID back as an offline conversion
First create the destination in Google Ads: go to Goals, then Conversions, add a new conversion and choose Offline Conversion, then select Add data source later when prompted. Next choose the pipeline moment that represents a conversion. Waiting for closed deals may produce too few events for smart bidding strategies, which the guide notes need at least 50 conversions per month; an earlier stage such as Opportunity creation can provide enough volume. Then build the automation: trigger it from that chosen stage in GoHighLevel, use Google Ads Send Offline Conversion as the action, and map the contact's GCLID to the required field. Test the full path before increasing ad spend.
Why browser storage beats reading the current URL
Built-in form parameter capture typically reads only the URL present at submission, so it fails when the visitor moves from the landing page to a contact page. Browser storage solves that gap. The same approach can also carry UTM parameters for paid campaigns and attribution details for organic search, organic social, referral and direct visits, giving a fuller picture of where each contact originated. The law-firm example in the table below shows the shape of that extra data.
| Field | Paid search example | Organic search example |
|---|---|---|
| Channel | Paid Search | Organic Search |
| Channel Drilldown 1 | ||
| Channel Drilldown 2 | Personal Injury Campaign | www.google.com |
| Channel Drilldown 3 | Car Accident Lawyer | Car Accident Lawyer Seattle |
| Channel Drilldown 4 | Free Case Review Ad | Not available in this example |
Illustrative examples from the guide; actual values depend on the UTM parameters and search data available for each visit.
Frequently asked questions
What is a GCLID and why store it in GoHighLevel?
A GCLID is the click identifier Google Ads attaches to a visit from an ad click. Storing it on the contact lets you connect that contact back to the originating click when you later report an offline conversion.
Will the GCLID survive if a visitor browses several pages before submitting a form?
Because the identifier is saved in the visitor's browser on arrival, it can still be written into a form completed on a later page or after a return visit, rather than only when the parameter is present in the current page URL.
How does the captured value reach GoHighLevel?
Use the form tool's native GoHighLevel integration where available, or pass the submission through Zapier or Make so the hidden-field value lands on the new contact alongside name, email and phone.
When should I send the GCLID back to Google Ads?
Create an Offline Conversion action in Google Ads, choose a pipeline stage that will generate enough volume for smart bidding — the guide notes at least 50 conversions per month — then trigger the send from that stage, for example when an Opportunity is created, and map the stored GCLID to the offline conversion field.