How to capture the GCLID in Framer forms
A GCLID links a form lead back to the Google Ads click that brought the visitor to your site. This guide explains how to preserve that identifier through browsing, attach it to each Framer submission, pass it to your CRM, and use it for offline conversion reporting.
Why the click identifier matters
Visitor counts alone do not show which advertising clicks became leads or customers. The GCLID provides that bridge: it identifies the specific Google Ads click behind a visit. When it travels with the form submission into the CRM, the business can connect later pipeline activity to the originating click and send qualified outcomes back to Google Ads.
Set up the form in three steps
First, install the attribution snippet. In Framer, open Site Settings, go to Custom Code, and paste the snippet into the End of Head field. Second, add a hidden field component to the form and set its default value to [gclid]. That placeholder tells the tool where to place the identifier. Third, submit a test form and confirm the GCLID appears alongside the visible lead fields.
How the identifier survives the journey
When a visitor arrives from a Google ad, the tool reads the GCLID from the landing URL and stores it in the browser. If the visitor moves from the homepage to a contact page, the URL may no longer contain the identifier, but the stored value remains available. On submission, the tool writes it into the hidden field, so it is included with the name, email and other submitted data. Framer can then forward the submission through its webhook, or through Zapier or Make, to the CRM.
Return the GCLID as an offline conversion
In Google Ads, open Goals, then Conversions, create a new conversion action, and choose Offline Conversion. When asked for a data source, select Add data source later. Next, choose the CRM moment that best represents value. Waiting for a fully closed deal may produce too few events for smart bidding; the source guidance notes that strategies such as Maximise Conversions, Maximise Conversion Value and Target CPA generally need at least 50 conversions per month. If closed deals are rarer, an earlier event such as a newly created deal can provide more usable volume. Then build the automation: trigger it from that CRM event, choose Google Ads Send Offline Conversion as the action, and map the stored GCLID to the matching field. Test the flow before increasing spend.
What else to check in the submission
A URL-only approach fails when the identifier disappears during browsing. Browser storage solves that gap. The setup can also pass UTM parameters and channel drilldowns for paid search, plus channel and search details for organic search, organic social, referral and direct visits. Use the table below as a field check when reviewing a submission.
| Field group | What to verify | Example use |
|---|---|---|
| Click identifier | GCLID is present on submission | Match the lead to a Google Ads click |
| Paid channel | Channel and drilldowns are populated | Identify campaign, ad group, ad and keyword context |
| Organic channel | Channel, source domain and keyword where available | Separate organic leads from paid leads |
| CRM event | Chosen trigger fires once per qualifying lead | Send the offline conversion at the right pipeline stage |
Examples are illustrative field checks based on the captured workflow, not guaranteed values for every visitor.
Frequently asked questions
What is needed to capture a GCLID in a Framer form?
Add the attribution snippet to the site, place a hidden field in the Framer form with the GCLID placeholder as its default, and let the tool store the click identifier from the landing URL until submission.
Will the GCLID survive if a visitor browses other pages before submitting?
Yes. Storing the identifier in the browser means a visitor can move between pages, or return later, and the original click identifier can still be written into the form when they submit.
How do I send the captured GCLID back to Google Ads?
Create an offline conversion action in Google Ads, choose a CRM event early enough to provide useful volume for bidding, then map the stored GCLID to that event through your automation tool.
Can the form also capture UTM and organic channel data?
The same setup can also record UTM parameters and channel details for paid and organic visits, so a lead record can show more than the click identifier alone.