Capture the GCLID in Keap for Google Ads offline conversions
When a lead arrives from a Google Ads click, the click identifier in the landing URL links that visitor to the ad that produced them. If that identifier reaches Keap with the contact, you can later report the resulting pipeline event back to Google Ads and judge campaigns by downstream outcomes rather than form fills alone. This guide explains how to preserve the identifier from landing through form submission, store it on the Keap contact, and choose a sensible point at which to send it back.
Why the identifier must be stored, not just read at submission
Click data disappears quickly. A visitor may land on the homepage, read several pages, and only later open the contact form; by then the original URL parameter is gone. The reliable pattern is therefore to save the identifier in the browser at first arrival, insert it into a hidden form field at submission, and carry it into the CRM with the rest of the contact record. That stored value is what makes the later offline-conversion upload possible.
Set up capture before the first test submission
- Place the capture snippet on the site, directly or through a tag manager, following the setup guidance for your platform. 2. Add a hidden field named for the GCLID to every lead form that should carry attribution. 3. Confirm the snippet fires on landing pages, not only on form pages. 4. Submit a test form after arriving from a tagged test URL and check that the hidden value is present in the submission payload.
From landing page to Keap contact record
On arrival, the tool reads the identifier from the URL and keeps it in the browser. When the visitor later submits a form, the stored value is written into the hidden field and travels with the name, email, phone number and other answers. Keap forms create the contact directly; third-party forms such as Gravity Forms, Typeform or Tally need their native Keap integration or a connector such as Zapier or Make to forward the submission. After forwarding, verify the identifier sits on the contact record next to the other submitted details.
Send the stored identifier back 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 the option to add it later. Next, decide which pipeline stage counts. Waiting for a closed deal is conceptually clean, but smart bidding approaches generally need around 50 conversions a month; below that volume, an earlier event such as deal creation gives the system more signal. Build the automation around that chosen stage: trigger on the Keap event, use Google Ads Send Offline Conversion as the action, and map the stored identifier from Keap into the matching field. Test the full path before relying on it for budget decisions.
What else to store alongside the click identifier
The same stored-attribution approach can also carry UTM-derived channel detail and information about organic arrivals, including Organic Search, Organic Social, Referral and Direct Traffic. For a paid-search example, the record might show Paid Search as the channel, Google as the source, and the campaign, keyword and ad names in successive drill-down fields. For an organic example, it might show Organic Search, Google, the referring search domain, and the query when available. Treat these as illustrative field maps: confirm the exact field names your forms and Keap instance use before building reports on them.
| Stage | What happens | Check |
|---|---|---|
| Landing | Identifier read from the ad URL and stored in the browser | Snippet fires on the landing page |
| Form submission | Stored value written into a hidden field and sent with contact details | Test submission contains the value |
| Keap | Contact created with the identifier on the record | Value visible beside name and email |
| Google Ads | Identifier uploaded at the chosen pipeline stage as an offline conversion | Test upload received before scaling budget |
Illustrative workflow based on the described capture, form and CRM handoff; field names must be confirmed in the reader's own setup.
Frequently asked questions
Why does a standard hidden field sometimes miss the GCLID?
No. A form tool that only reads the URL at submission time will miss the identifier if the visitor navigates to another page first. Storing the value in the browser on arrival preserves it across pages and return visits.
Should the offline conversion fire when a deal closes?
Use the stage that gives Google Ads enough volume to learn from. If closed deals are fewer than roughly 50 per month, an earlier pipeline event such as deal creation is usually the more practical conversion point.
Does this work with non-Keap forms?
Keap forms can create the contact directly. With a third-party form, use its native Keap integration or a connector such as Zapier or Make to pass the submission, including the stored identifier, into Keap.