Capture the GCLID in Ninja Forms and send it back to Google Ads
You can attach the Google click identifier to every Ninja Forms submission, pass it into a CRM, and later return it to Google Ads as an offline conversion. The key is to store the identifier when the visitor first arrives, rather than relying on it still being present in the page address when the form is completed.
1. Install the snippet and add a hidden field
Install the attribution snippet on the site, using the theme header area, a header/footer plugin, or Google Tag Manager on WordPress. Then add a hidden field to the Ninja Forms form and set its default value to [gclid]. That field becomes the destination for the stored click identifier.
2. Store the first-visit identifier in the browser
When a visitor arrives from Google Ads, the snippet reads the identifier from the landing URL and stores it in the browser. It remains available while the visitor browses other pages or returns later. At submission, the stored value is written into the hidden field, so it travels with the name, email and other details entered in the form.
3. Pass the identifier to your CRM
Send the completed submission onward with a Ninja Forms add-on or an integration tool such as Zapier. Keep the GCLID as a distinct CRM field so it can be matched to the later sales event. Do not overwrite it with a later click unless that is the attribution rule you intend to use.
Return the GCLID 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, choose Add data source later. Next, decide which sales milestone should trigger the upload. A fully closed deal is not always the best choice: strategies such as Maximise Conversions, Maximise Conversion Value and Target CPA generally need at least 50 conversions a month, so an earlier milestone such as deal creation may provide enough signal when closures are fewer. Create a Zap whose trigger matches that milestone, choose Google Ads and Send Offline Conversion as the action, then map the stored GCLID from the CRM to the matching Zapier field. Test the flow before increasing ad spend.
Why browser storage works better, and what else it can capture
A URL-based merge tag fails in a common journey: the visitor lands on the homepage from an ad, then navigates to the contact page, where the identifier is no longer in the address. Browser storage avoids that gap. The same setup can also carry UTM parameters. For a paid-search example, the submitted record might show Paid Search, Google, a campaign name, a keyword and an ad name. For an organic visit, it might show Organic Search, Google, the search-engine domain and the searched keyword when available. Use this checklist before launch: snippet installed on every relevant page, hidden field present on each form, a test submission contains the identifier, the CRM field receives it, and the offline-conversion test succeeds.
Frequently asked questions
Why does the GCLID disappear when someone moves to another page?
No. A merge-tag approach only works while the identifier remains in the address at submission. If the visitor moves from the landing page to another page, that value can disappear. Browser storage preserves the first-visit value across pages and return visits.
Should the offline conversion be sent when a deal closes?
Choose the earliest stage that still represents a real business outcome and can produce enough volume. Waiting for a fully closed deal may leave smart bidding with too few signals when monthly closures are below roughly 50; tracking deal creation can provide a stronger signal.
Can hidden fields also carry UTM and organic channel data?
Yes. The same hidden-field approach can carry UTM values and channel details for paid and organic visits, including Organic Search, Organic Social, Referral and Direct Traffic, depending on the parameters and referral data available.