Capture the GCLID in Gravity Forms and Send It to Google Ads
A click identifier is only useful if it survives the journey from ad click to form submission and then reaches the systems that act on it. This guide explains how to store that identifier in the browser, write it into a Gravity Forms submission, forward it to a CRM, and return it to Google Ads as an offline conversion.
Why the click ID needs to survive browsing
Google Ads can generate enquiries, but clicks alone do not show whether those enquiries became customers. The click identifier attached to an ad click — the GCLID — is the link between a campaign and a later lead. Capturing it on every relevant form submission lets you connect advertising spend to CRM records and, later, report the outcome back to Google Ads.
The workflow has three parts: remember the identifier when the visitor arrives, place it into the form data when they submit, and use the stored value downstream. A hidden field is the bridge between the first two parts because it travels with the submission without asking the visitor for anything.
Set up capture in three steps
Install the attribution snippet on the site so it can read the identifier from the landing URL and save it in the visitor's browser. Common placement options described for WordPress include the theme's header area, a header/footer insertion plugin, or Google Tag Manager.
Then add a hidden field labelled for the GCLID to each Gravity Form that should carry it. When a visitor who arrived from a Google ad completes the form, the saved identifier is written into that field and submitted alongside name, email, and other entries.
Checklist before testing:
- Snippet installed on every page where a tracked form can be reached
- Hidden GCLID field present on each target form
- A test submission shows a non-empty GCLID value
- The value appears in the form entry, not only on the landing page
Forward the value and avoid the URL-only gap
Once the identifier is part of the submission, forward the entry to your CRM or other tools through Gravity Forms add-ons or an integration tool such as Zapier. Keeping the GCLID as its own field matters: it makes later mapping, filtering, and reporting straightforward.
A URL-only method fails in a common case. A visitor clicks an ad, lands on the homepage, browses to a contact page, and submits there. The identifier is no longer in that page's URL, so it is lost. Browser storage avoids that gap because the value from the first visit is retained across pages and even if the visitor leaves and returns later.
Return the GCLID as an offline conversion
First create the offline conversion in Google Ads: open Goals, then Conversions, add a new conversion, choose Offline Conversion, and choose to add the data source later. Next decide which business event should count. A closed deal is the most direct outcome, but volume matters for automated bidding. If fewer than 50 deals close per month, sending an earlier event such as deal creation usually provides enough signals for strategies like Maximise Conversions, Maximise Conversion Value, or Target CPA.
Then build the automation: set the trigger to that chosen event in your CRM, choose Google Ads as the action, select Send Offline Conversion, and map the stored GCLID to the matching field. Test the path end to end before relying on it for bidding decisions.
What else the submission can carry
The same hidden-field pattern can carry more than the click ID. UTM parameters behind ads can be passed through as channel and drilldown values, and organic arrivals can be recorded too.
Example — paid search: a visitor clicks a family-law ad and submits a form. The submission could carry Channel = Paid Search, with drilldowns identifying Google, the campaign name, the keyword being bid on, and the ad clicked.
Example — organic search: a visitor finds the same site through a Google search and submits a form. The submission could carry Channel = Organic Search, with drilldowns for Google, the search engine domain, and the searched keyword when available.
That broader record helps you compare paid and organic enquiries in the CRM instead of seeing only the form contents.
| Situation | URL-only capture | Browser-stored capture |
|---|---|---|
| Visitor submits on the landing page | Identifier present in URL, so it can be captured | Captured from browser storage |
| Visitor browses to another page before submitting | Identifier no longer in URL, so it is missed | Retained and written into the hidden field |
| Visitor leaves and returns later | No guarantee the identifier is still available | Retained for the later submission |
Comparison summarises the methods described in the guide; tool availability should be verified by the owner before publication.
Frequently asked questions
Will dynamic population alone capture the GCLID if someone browses first?
No. If the parameter is only present on the landing page and the visitor moves to another page before submitting, a URL-only approach will miss it. Storing the value in the browser preserves it across pages and return visits.
When should the offline conversion be sent back to Google Ads?
Choose the earliest reliable business event that still represents value. Waiting for a closed deal is conceptually clean, but smart bidding needs volume — the guide notes at least 50 conversions per month for strategies such as Maximise Conversions, Maximise Conversion Value, or Target CPA. If closed deals are fewer, an earlier event such as deal creation gives the system more data.
Does this only work for paid clicks?
Yes. The same hidden-field approach can carry UTM-derived channel and drilldown values, and it can also record organic sources such as Organic Search, Organic Social, Referral, and Direct Traffic.