Capture the GCLID in FormAssembly and return it to Google Ads
Visitor counts alone do not show which Google Ads clicks produced enquiries. Saving the click identifier with every form submission, passing it to your CRM, and later returning a meaningful outcome to Google Ads closes that gap.
Why the click ID needs to travel with the lead
Google Analytics can report visits from paid search, but it does not reliably connect those visits to named leads or closed business. A GCLID is the click identifier attached to a Google Ads click. When that identifier travels with a form submission, the resulting lead can be matched back to the campaign, ad group, and keyword that produced it.
The practical sequence has three parts: preserve the identifier when the visitor first arrives, place it into the form when the visitor submits, and send a later business outcome back to Google Ads with the same identifier.
Step 2: Preserve the identifier until submission
When a visitor arrives from a Google Ads click, the attribution tool reads the GCLID from the landing URL and stores it in the browser. The stored value remains available while the visitor moves between pages, and it can also survive a return visit days later.
At submission, the tool writes the stored identifier into the hidden field. This differs from reading only the current URL: a visitor may land on the homepage, move to a contact page, and submit there after the identifier is no longer visible in the address bar.
Step 3: Send the identifier with the submission
The submitted record now contains the GCLID alongside the details entered by the lead, such as name and email. Use a native FormAssembly connector or an automation service such as Zapier to pass the identifier into the CRM or another destination system.
Keep the field name consistent across the form, CRM, and automation so later matching does not depend on manual cleanup.
Return a meaningful outcome as an offline conversion
In Google Ads, go to Goals and then Conversions, start a new conversion, and choose Offline Conversion. When asked for a data source, select the option to add it later. This creates the conversion definition that will receive outcomes from outside the website.
Next, choose the business event that should be returned. Waiting for a fully closed deal may produce too few events for automated bidding. The captured guidance notes that smart bidding options such as Maximise Conversions, Maximise Conversion Value, and Target CPA typically need at least 50 conversions per month. If closed deals fall below that level, an earlier event—such as deal creation in the CRM—may provide enough signal.
Create an automation whose trigger matches that chosen event. Select Google Ads as the action, choose Send Offline Conversion, and map the stored GCLID from the CRM or automation record to the required field. Test the full path before relying on the data for budget decisions.
What else the attribution data can clarify
A URL-only approach can miss the identifier when navigation removes it from the address bar. Browser storage solves that common case by retaining the first-click value across pages and return visits.
The same attribution setup can also capture UTM parameters and channel details. For a paid-search example, the submitted record may include Paid Search as the channel, Google as the first drilldown, the campaign name as the second, the keyword as the third, and the ad name as the fourth. For organic discovery, it may instead identify Organic Search, Google, the search-engine domain, and the search term when available. These fields help distinguish paid and organic routes without relying only on the GCLID.
Pre-launch checklist
Use this checklist before treating the setup as complete:
- The attribution snippet loads on every page where a relevant form may be reached.
- Each FormAssembly form contains a hidden field with the correct default value.
- A test visitor arriving from a tagged Google Ads URL submits a form and the GCLID appears in the submission.
- The identifier reaches the CRM through the chosen connector or automation.
- The offline conversion exists in Google Ads and uses the intended business event.
- The automation maps the CRM identifier to the Google Ads action correctly.
- A test outcome appears as an offline conversion before campaign decisions rely on it.
The protected form-controls contract is form-controls-contract; its exact controls and fields remain governed by that module rather than restated here.