Capture GCLID in Elementor Forms and Send It to Your CRM and Google Ads
A Google Ads click identifier is only useful if it survives the journey from landing page to form submission and then reaches the systems that act on it. This guide explains a three-part setup: store the identifier in the browser, write it into a hidden form field, and forward it to a CRM and, when ready, back to Google Ads as an offline conversion.
Why the click identifier matters
Clicks can look promising in an ad account while producing few customers. Without linking a submission to the ad click that started the visit, you cannot tell which campaigns create revenue. Capturing the identifier at form level closes that gap: the lead record carries the click reference, and that reference can later be returned to the ad platform.
Three steps: install, store, submit
First, place the attribution snippet on the site. On WordPress it can be added through Elementor's Custom Code settings, a header/footer insertion plugin, or Google Tag Manager. Second, add a hidden field to each Elementor form and set its default value to [gclid]. That field is the destination the snippet writes to. Third, when a visitor arrives from a Google Ad, the snippet reads the identifier from the URL and stores it in the browser. When the form is completed, the stored value is written into the hidden field and submitted with the visible answers such as name and email. From there the value can be passed to a CRM or other tools, including via an integration platform.
Decision checklist: URL-only versus browser-stored capture
Checklist before you rely on the data: (1) snippet loads on every page where a form may be completed, not only the landing page; (2) every relevant Elementor form has the hidden field with the correct default value; (3) a test submission from a URL containing a click identifier shows the value in the submission; (4) a test submission after browsing to a different page still shows the value; (5) the CRM field receiving the value is mapped correctly. The browsing test is the one most setups fail, because it distinguishes browser storage from URL-only reading.
Returning the identifier to Google Ads as an offline conversion
In Google Ads, open Goals, then Conversions, create a new conversion and choose Offline Conversion. When asked for a data source, select 'Add data source later'. Next choose where in your sales process a conversion should be recognised. Waiting for a fully closed deal is cleanest, but smart bidding needs volume — around 50 conversions a month is the working threshold described here. If closed deals are fewer than that, an earlier event such as deal creation gives the system more data. Then create an integration flow: trigger on the chosen event, select Google Ads as the action, choose Send Offline Conversion, and map the stored identifier from the CRM to the correct field. Test the flow before increasing ad spend.
Beyond GCLID: UTM and organic attribution on the same submission
The same hidden-field pattern can carry more than the click identifier. UTM parameters can be captured and passed through, for example channel, campaign, keyword and ad drilldown fields for a paid search visit. Organic visits can also be described, for example organic search channel, search engine and the searched keyword where available. That means reporting is not limited to paid clicks: every lead can carry a channel description. A worked example: a visitor clicks a paid search ad, browses several pages, then submits a contact form. The submission should still contain the click identifier plus the campaign and keyword fields, because the data was stored at arrival rather than read from the final page URL.
| Situation | URL-only reading | Browser-stored capture |
|---|---|---|
| Visitor submits on the landing page | Identifier present in URL, captured | Stored at arrival, captured |
| Visitor browses other pages, then submits | Identifier no longer in URL, missed | Stored in browser, captured |
| Visitor leaves and returns later | No identifier to read | Stored value can still be written to the field |
| Organic or UTM visit | Not captured by click-identifier reading alone | Channel and drilldown fields can be passed through |
Comparison based on the workflow described in the guide; tool behaviour should be verified in the owner's own implementation.
Frequently asked questions
What is the minimum setup to capture GCLID in an Elementor form?
Add the attribution snippet to the site, then add a hidden field to the Elementor form whose default value is [gclid]. The snippet stores the click identifier in the browser, and the hidden field receives it at submission.
Will GCLID still be captured if the visitor browses several pages before submitting?
Yes, if the identifier was stored when the visitor first arrived. That persistence is the key difference from reading the URL only at submission time, when the parameter may already have disappeared after browsing other pages.
How do I send the captured GCLID back to Google Ads?
Create an offline conversion in Google Ads, choose 'Add data source later', pick the sales-process point you want to count, then use an integration platform to trigger on that event and map the stored GCLID to the Send Offline Conversion action.
Can the same setup capture UTM and organic attribution data?
UTM parameters and organic-channel details can be passed alongside the click identifier, so a submission can show channel, campaign, keyword and related drilldown fields rather than only the paid click.