Skip to content

Capture the Google Click ID in Formidable Forms and report offline conversions

Google Ads shows clicks, but not which click became a lead. Storing the Google Click ID (GCLID) with every Formidable Forms submission closes that gap: the identifier can travel to a CRM or spreadsheet, then return to Google Ads as an offline conversion so campaign reporting reflects enquiries and sales, not only traffic.

Why the identifier is lost without browser storage

A GCLID is attached to the landing URL when a visitor arrives from a Google Ads click. If that identifier is not saved at arrival, it disappears from the URL as soon as the visitor moves to another page. A form on a later page therefore has nothing to record, even though the enquiry came from a paid click.

The fix has three parts:

  • Save the GCLID in the browser when the visitor first lands, so browsing and return visits do not lose it.
  • Write the saved value into a hidden field on the form at submission time.
  • Store the submitted value with the contact record, then use it when reporting the eventual conversion back to Google Ads.

Checklist before you start:

  • Access to add a small script to the site header, or to load it through Google Tag Manager.
  • A Formidable Forms form you can edit.
  • A destination for submissions, such as a CRM, Google Sheets, or an integration tool such as Zapier.
  • Access to the Google Ads account that ran the clicks.

Set up capture in three steps

Step 1: Add the capture script and a hidden field

Place the script supplied by your capture tool in the site header. On WordPress, a theme header area or a header/footer insertion plugin can do this; Google Tag Manager is an alternative route. Then add a hidden field named GCLID to each Formidable Forms form you want to measure. The field is the destination the script writes to; visitors do not need to see or complete it.

Step 2: Let the script save and populate the value

On arrival from a Google Ads click, the script reads the GCLID from the URL and stores it in the browser. When the visitor later submits a form, the stored value is written into the GCLID hidden field. Because storage happens at arrival, the value survives moving between pages and returning on a later day.

Step 3: Record the value with the submission

Formidable Forms stores the hidden-field value alongside the visible answers, such as name and email. From there it can flow onward through a native CRM integration, for example Salesforce or HubSpot, to a spreadsheet such as Google Sheets, or through Zapier to other tools. Verify in a test submission that the GCLID field contains a value before relying on it in reporting.

Return the GCLID to Google Ads as an offline conversion

First create the conversion that will receive the data. In Google Ads, open Goals, then Conversions, start a new conversion and choose Offline Conversion. When asked for a data source, select the option to add it later.

Next, choose the sales milestone that should count. Waiting until a deal is won gives the most valuable signal but can be too infrequent: automated bidding approaches such as Maximise Conversions, Maximise Conversion Value and Target CPA generally learn better with more than 50 conversions a month. If won deals are rarer than that, an earlier event, such as a new deal created for the contact in the CRM, gives Google Ads more signals to learn from.

Then connect the milestone to Google Ads. In Zapier, create a Zap whose trigger is that milestone event, for example new deal created. Set the action to Google Ads and choose Send Offline Conversion. Map the stored GCLID from the CRM record to the matching field in the action. Run a test conversion before increasing spend, to confirm the identifier, timing and value are arriving correctly.

What else the captured data can show

URL-only capture fails in a common journey: a visitor clicks an ad, lands on the homepage, then navigates to the contact page. The GCLID is no longer in the URL at submission, so nothing is recorded. Browser storage avoids that failure by keeping the identifier from the landing moment until the form is completed.

The same setup can also carry UTM parameters from the ad, so a submission can show channel, campaign, ad group and ad alongside the GCLID. For example, an accounting firm enquiry might arrive as Paid Search through Google, under a Tax Returns campaign, a Sydney ad group and a Free Consultation ad. In a CRM or spreadsheet, those fields support charts comparing campaigns, ad groups and ads.

Organic discovery can be recorded in the same way. A law firm enquiry found through an organic Google search might show Organic Search, Google as the source, the search engine domain, and a query such as Divorce Lawyer Sydney where available. Combining paid and organic attribution gives a fuller view of where leads originate and where growth opportunities sit.

Failure distinction to check in testing:

  • GCLID present on landing but empty on submission: the hidden field is missing, misnamed, or the script is not loading on the form page.
  • GCLID present but no offline conversion in Google Ads: the conversion action has not been created, the Zap trigger does not match the chosen milestone, or the GCLID field mapping is wrong.
  • Conversions arriving but bidding not improving: volume may be too low for the chosen milestone, so consider an earlier event.