Capture the GCLID in Webflow Forms and Send It to Your CRM
Clicks alone do not show whether advertising produced customers. Capturing the Google Click ID on each Webflow form submission links a lead to the ad click that brought the visitor in, lets you pass that identifier to a CRM or other tools, and makes it possible to report the eventual result back to Google Ads as an offline conversion.
Three-step capture workflow
The workflow has three parts. First, place the attribution snippet on the site, either through Webflow settings or through Google Tag Manager, and add a hidden field to the form. Second, when a visitor arrives from a Google ad, the identifier is read from the landing URL and retained in the browser. Third, on submission the retained value is written into the hidden field and stored alongside the visible answers. From Webflow it can then move onward through a native integration or a connector such as Zapier.
Pre-launch checklist
Checklist before going live: the snippet loads on every page where a form may be reached; each form has the hidden field; a test click with a GCLID in the URL produces a submission containing that value; the value arrives in the CRM field you intend to use; and the offline-conversion mapping points at that same field. Test the full path before increasing ad spend.
Returning the result to Google Ads
Create the conversion in Google Ads under Goals and Conversions, select Offline Conversion, and choose to add the data source later. Decide which business event counts: a closed deal, or an earlier stage such as deal creation when closed deals are too infrequent for smart bidding. In Zapier, trigger on that event, choose Google Ads with Send Offline Conversion, and map the stored GCLID from the CRM to the destination field.
What else travels with the submission
The same form submission can carry more than the click identifier. Paid visits can include UTM-derived channel, campaign, keyword and ad detail, while organic visits can include channel, search engine, referring domain and keyword where available. That broader context helps distinguish a lead driven by a specific ad from one that arrived through organic search, organic social, referral or direct traffic.
| Scenario | Channel | Drilldown 1 | Drilldown 2 | Drilldown 3 | Drilldown 4 |
|---|---|---|---|---|---|
| Paid search example | Paid Search | Family Law Campaign | Divorce Lawyer Sydney | Free Consultation Ad | |
| Organic search example | Organic Search | www.google.com | Divorce Lawyer Sydney | Not available |
Illustrative examples from the source; replace bracketed values with your own campaign data.
Frequently asked questions
Why does a GCLID disappear before the form is submitted?
A URL-only approach fails when the visitor moves to another page, because the identifier is no longer in the address. Storing it in the browser at landing preserves it for a later form submission, including after a return visit.
Which sales milestone should trigger an offline conversion?
Choose a milestone with enough volume for bidding. Waiting for a fully closed deal is cleanest conceptually, but if that produces fewer than about 50 conversions a month, an earlier event such as deal creation gives the bidding system more data to learn from.
What is the order for sending a GCLID back to Google Ads?
Create the offline conversion in Google Ads first, choosing to add the data source later. Then connect the chosen CRM event to Google Ads through Zapier, select Send Offline Conversion, and map the stored GCLID to the matching field.
Can UTM and organic channel data travel with the form submission?
Yes. Alongside the click identifier, UTM values from paid links and channel information for organic visits can be passed with the submission, so the receiving system shows both the campaign source and the specific campaign, keyword or ad where available.