Capture the GCLID in Instapage Forms and Send It to Your CRM
A click identifier is only useful if it survives the journey from ad click to form submission. This guide shows how to store that identifier when a visitor arrives, place it into a Instapage form without asking the visitor to type it, and then use it in your CRM and for offline conversion reporting in Google Ads.
Why the identifier matters
Analytics can show that ads produced visits, yet visits alone do not reveal which campaigns produced leads or paying customers. The click identifier links a form submission back to the specific ad click that started the visit. Once that identifier is attached to the lead record, it can travel into a CRM, a spreadsheet, or an offline conversion upload.
Two capture methods, and why they differ
URL-only capture: the identifier is read from the address bar at the moment the form is submitted. If the visitor clicks through other pages, leaves, or returns days later, the address may no longer contain it and the value is lost.
Browser-stored capture: the identifier is read on arrival and saved in the visitor's browser. When a form is later completed, the saved value is written into a hidden field. Browsing, navigation, and a delayed return do not erase the link between click and lead.
Setup checklist
- Install the attribution snippet on the landing page. Place it through the page's JavaScript settings, either for one page or across several landing pages.
- Add a hidden field to the form and label it GCLID. That field is the destination the snippet writes to.
- On arrival from a Google Ads click, the tool extracts the identifier from the URL and stores it in the browser.
- On submission, it populates the hidden field automatically.
- Instapage then captures the identifier with the visitor's name, email, and other entries. It appears in the Instapage submissions view and in lead notification emails.
- Route the submission onward with Instapage integrations, Zapier, Make, or a direct CRM connection.
Sending the value back as an offline conversion
Create the conversion action first: in Google Ads, open Goals, then Conversions, start a new conversion, and choose Offline Conversion. When asked for a data source, choose the option to add it later.
Next, pick the trigger stage. Waiting for a fully closed deal can starve smart bidding of volume; the guide notes that strategies such as Maximise Conversions, Maximise Conversion Value, and Target CPA typically need at least 50 conversions per month. If closed deals fall below that, an earlier qualified stage, such as a new CRM deal, gives Google a usable signal.
Then build the automation: create a Zap whose trigger matches that stage, choose Google Ads as the action, select Send Offline Conversion, and map the stored GCLID from the CRM to the matching Zapier field. Test the upload before increasing ad spend.
What else the hidden fields can carry
Paid example: a visitor arrives from a paid search campaign for accounting software. The hidden fields can carry Channel = Paid Search, with drilldowns naming Google, the Small Business Accounting Campaign, the keyword Best Accounting Software, and the Free Trial Ad.
Organic example: a visitor arrives from a regular Google search. The same pattern can carry Channel = Organic Search, with drilldowns naming Google, the search engine domain, and the searched keyword where available. Organic Social, Referral, and Direct Traffic are also covered.
Owner example template
Customer example worksheet
Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.
| Field | Your details |
|---|---|
| Customer and permission to use the example | ________ |
| Problem and starting point | ________ |
| Configuration or actions | ________ |
| Measurement period | ________ |
| Outcome and supporting evidence | ________ |
| Approval to publish | ________ |
| Check | Done when |
|---|---|
| Snippet installed | Code present in Instapage JavaScript settings for the target page or pages |
| Hidden field added | A field labelled GCLID exists on the form |
| Arrival capture | A test click stores the identifier in the browser |
| Submission capture | The identifier appears in Instapage submissions and notification emails |
| CRM routing | The identifier arrives in the CRM alongside contact details |
| Offline conversion | The chosen CRM stage triggers a Google Ads offline conversion with the mapped identifier |
Use as a pre-launch verification list; test with a real click-through before scaling spend.
Frequently asked questions
Why does a GCLID disappear before a form is submitted?
No. If capture depends on the identifier still being present in the page address at submission, a visitor who browses elsewhere or returns later can lose it. Storing the value in the browser when the ad click first arrives preserves it for a later form fill.
Which sales stage should trigger an offline conversion?
Choose a stage your sales team treats as a qualified signal, such as a newly created deal, rather than waiting for a closed deal if closed deals are too few. Smart bidding needs enough conversion volume to learn from, and the source guide uses 50 conversions per month as the practical threshold.
Can hidden fields carry more than the GCLID?
Yes. The same hidden-field pattern can carry UTM values and channel details for paid and organic visits, so a lead record can show campaign context alongside contact details.