Capture the GCLID in Jotform and connect it to Google Ads
A form submission alone tells you who contacted you, not which ad click brought them in. Adding the Google click identifier to every Jotform submission closes that gap: the identifier travels with the lead into your CRM, and can later be returned to Google Ads so campaign performance reflects real leads and revenue rather than clicks alone.
Why URL-only capture misses leads
The identifier is present in the landing URL when a visitor arrives from a Google ad. The practical problem is timing: people rarely submit on that first page. They may read several pages, leave, and return days later. A method that only checks the URL at the moment of submission will miss those leads entirely, even though they came from paid search.
Step 1: Install the snippet and add a hidden field
Install the attribution snippet on your website. Most builders provide a custom-code or header area for this; alternatively, load it through Google Tag Manager so scripts stay centralised. Then create a hidden field in each Jotform form and set its default value to [gclid]. That placeholder gives the snippet a destination to populate.
Step 2: The identifier is saved, then written into the form
On landing from an ad, the snippet reads the identifier from the URL and stores it in the visitor's browser. It therefore survives navigation to other pages and a later return visit. When the form is completed, the stored value is written into the hidden field, so Jotform records it alongside name, email and any other answers. From there it can flow to a CRM or other tools through Jotform's native integrations or an automation platform such as Zapier.
Pre-launch checklist
Use this checklist before sending traffic: (1) snippet present on every page where a form may be reached, (2) hidden field added to each form with the correct default value, (3) a test submission from a GCLID-bearing URL shows the value in the submission, (4) the CRM field receives it, and (5) the offline conversion automation is tested end to end. If you are evaluating a hosted attribution tool, confirm its current trial length, plan limits and setup requirements directly with that provider before you commit budget or traffic.
Step 3: Return the GCLID to Google Ads as an offline conversion
First create the conversion in Google Ads: open Goals, then Conversions, start a new conversion and choose Offline Conversion. If asked for a data source, select 'Add data source later'. Next, pick the sales moment that should count. A won deal is the most direct measure, but bidding algorithms learn better with volume; where closed deals are fewer than roughly fifty a month, an earlier event such as deal creation may be the better signal. Then create an automation in Zapier triggered by that event, choose Google Ads with 'Send Offline Conversion', and map the stored GCLID from your CRM to the matching field.
What else the hidden fields can carry
Beyond the click identifier, UTM parameters can be passed through for paid campaigns. For example, a law firm lead from a paid search ad might arrive with Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the campaign name, Channel Drilldown 3 = the targeted keyword, and Channel Drilldown 4 = the specific ad. That breakdown shows which campaign, ad group, ad and keyword produced the lead. For unpaid visits, the same mechanism can record Channel = Organic Search with drilldowns for the search engine, its domain and, where available, the searched keyword, giving a fuller picture across organic search, organic social, referral and direct traffic.
Wrap up
In short: save the identifier at first landing, write it into a hidden field at submission, forward it to your CRM, and send it back to Google Ads when the chosen sales event occurs. That loop connects ad spend to leads and revenue instead of stopping at the click.
| Situation | What URL-only capture records | What browser-saved capture records |
|---|---|---|
| Visitor submits on the landing page | GCLID present in URL at submission | GCLID saved and written into hidden field |
| Visitor browses several pages, then submits | GCLID no longer in URL; nothing recorded | GCLID retained from first landing and submitted |
| Visitor leaves and returns later | No GCLID unless the ad URL is used again | GCLID retained in the browser and submitted |
Illustrative comparison based on the browsing behaviour described in the source material.
Frequently asked questions
What is a GCLID and why capture it on a form?
A GCLID is the click identifier Google Ads adds to the landing-page URL after someone clicks an ad. Capturing it on the form submission lets you connect that lead to the specific click in your CRM and, later, return it to Google Ads as an offline conversion signal.
Does the GCLID need to still be in the URL when the form is submitted?
No. If the identifier is only read from the URL at submit time, it will be missing when the visitor browsed other pages first or returned later. Saving it in the browser on first landing and writing it into a hidden field at submission preserves it across that journey.
How do I send the captured GCLID back to Google Ads?
Create the offline conversion first in Google Ads, choosing 'Add data source later' if prompted. Then decide which sales event should count, and build an automation triggered by that event that sends the stored GCLID to Google Ads. Test the flow before relying on it for spend decisions.
Should the offline conversion fire on a won deal or an earlier event?
Waiting for a fully won deal gives the cleanest revenue signal, but smart bidding needs enough volume to learn from. Where monthly closed deals are low, an earlier event such as deal creation can provide more signals. The choice depends on your volume and how closely the event matches value.
Can I capture UTM and organic channel data the same way?
Yes. The same hidden-field approach can carry UTM-derived channel detail for paid traffic and channel detail for organic search, organic social, referral and direct visits, so reporting is not limited to ad clicks.