Skip to content

Capture the GCLID in Duda Forms and Pass It to Your CRM

If you run Google Ads to a Duda site, you can see how many clicks arrive, but not which of those clicks became a real lead or customer. The missing link is usually the Google Click ID (GCLID) — the value Google Ads appends to the landing URL. This guide shows how to place the GCLID into a Duda form hidden field on every submission, move it into your CRM, and optionally return it to Google Ads as an offline conversion.

What you are building

The setup has three moving parts. First, a small script on your Duda site captures the GCLID from the landing URL and keeps it in the visitor's browser. Second, a hidden field on each Duda form receives that value at submit time. Third, the submitted value travels with the lead record into your CRM, where you can report on it or forward it to Google Ads. The same script can also capture UTM parameters and organic-channel details, which is useful if you want a single attribution record per lead rather than a Google-Ads-only view.

Step 1 — Install the script and add a GCLID hidden field

Add the tracking snippet to your Duda site through the Site Wide HTML area of the Duda dashboard so it applies across every page. Then open each form that should capture the GCLID and add a new hidden field labelled GCLID. The label matters: it is the hand-off point the script writes into. If you have several forms — a contact form, a quote form, a newsletter form — repeat the hidden field on each one you want covered. Full step-by-step instructions for the hidden-field part are available in the help article linked from the source registry.

Step 2 — How the GCLID reaches the field

When a visitor clicks a Google Ad, the landing URL carries a gclid parameter. The script reads that parameter and stores it in the browser, so the value survives page-to-page browsing and return visits. At submit time the stored value is written into the hidden field you created. This is the key difference from naive approaches that only read the URL at the moment of submission: if the visitor navigates away from the landing page before filling in the form, a URL-only method loses the GCLID.

Step 3 — Confirm the GCLID is captured with each submission

After a test submission, open the form submissions area of the Duda dashboard. The GCLID should appear alongside the lead's name, email, and other answers, and it should also show up in any lead notification email Duda sends. From there you can push the record into your CRM using Duda's built-in integrations, or through an automation tool such as Zapier or Make. If the field is empty on a test, check three things in order: the hidden field label matches exactly, the script is loaded on the page containing the form, and the test visit actually arrived with a gclid parameter in the URL.

Where the GCLID lives at each hop

Use this map when something goes missing. Each row is a stage in the chain, the location where the value should be visible, and the most common reason it is not.

Step 4 — Return the GCLID to Google Ads as an offline conversion

In your Google Ads account, open Goals, then Conversions, and create a new conversion action of type Offline Conversion. On the final screen, choose the option to add a data source later — you will supply the data through an automation rather than a direct upload. Next, decide which stage of your sales process should trigger the send-back. Many teams wait until a deal is fully closed, but Google's smart bidding strategies — Maximise Conversions, Maximise Conversion Value, and Target CPA — generally need at least 50 conversions per month to perform well. If your closed-deal volume is below that, sending an earlier qualified-lead event (for example, when a new deal is created in the CRM) gives smart bidding a usable signal without starving it of data.

Step 5 — Map the GCLID in Zapier

Create a new Zap whose trigger matches the stage you chose — for example, a new deal created for a contact. Set Google Ads as the action app and choose Send Offline Conversion as the event. In the action configuration, map the GCLID field from your CRM (or wherever the value is stored) into the corresponding Zapier field. Before increasing ad spend, run a test record through the Zap and confirm the conversion appears in Google Ads. The source registry links to a deeper article on testing offline conversions.

Why browser storage matters for Duda forms

A URL-only capture method works only while the gclid parameter is still present in the address bar. Real visitors often browse several pages before converting, or leave and return days later. Storing the value in the browser means the hidden field is populated on the eventual submission regardless of the path taken. The same mechanism also captures UTM parameters, so a single form submission can carry channel, source, campaign, ad group, and ad-level detail alongside the GCLID.

Worked example — a construction company's paid and organic leads

Suppose a construction company runs a Google Ads campaign for residential renovations. A visitor clicks the Free Quote Ad and later submits a form. The attribution record for that lead would read: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Residential Renovations Campaign; Channel Drilldown 3 = Home Renovation Contractors; Channel Drilldown 4 = Free Quote Ad. If a different visitor arrives through a regular Google search instead, the record would read: Channel = Organic Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = the search engine domain used; Channel Drilldown 3 = the search term, when it is available. Both records can sit in the same CRM field set, which makes paid and organic performance comparable in one report.

Decision checklist before you go live

Use this list to catch the common gaps before you spend on ads.

  • Hidden field label is exactly GCLID on every form you want covered.
  • The tracking snippet is loaded site-wide, not only on the landing page.
  • A test visit with a gclid parameter produces a populated hidden field in the Duda submission record.
  • The CRM field that stores the GCLID is included in the Zap's trigger payload.
  • The offline conversion action exists in Google Ads and is set to receive data later.
  • The trigger stage produces enough monthly volume for smart bidding to learn from — roughly 50 conversions per month is the working threshold.
  • A test conversion has appeared in Google Ads before budget is increased.

Two different failures look the same

An empty GCLID column in the CRM can come from two unrelated causes. The first is capture failure: the visitor never had a gclid in the URL, or the script was not present on the page, so the hidden field was empty at submit time. The second is transport failure: the hidden field was populated in Duda, but the CRM mapping or the Zap field mapping dropped the value before it reached the destination. Check the Duda submission record first. If the GCLID is there, the problem is downstream; if it is missing, the problem is upstream.

GCLID field map across the capture chain
StageWhere the value should appearWhat to check if it is missing
Ad clickgclid parameter in the landing URLConfirm the ad's final URL includes the parameter
Browser storageStored value in the visitor's browserConfirm the tracking snippet is loaded site-wide
Duda formHidden field labelled GCLIDConfirm the label matches exactly and the field is on the submitted form
Duda submission recordGCLID column in form submissions and notification emailConfirm the submission was made after the script loaded
CRM recordGCLID field on the lead or dealConfirm the integration or automation maps the field
Zapier actionGCLID input on the Send Offline Conversion stepConfirm the field is mapped, not left blank
Google AdsOffline conversion attributed to the clickConfirm the conversion action exists and accepts data later

Descriptive checklist based on the captured setup steps; not a verification of any specific account configuration.

Frequently asked questions

Does the GCLID survive if the visitor leaves and comes back days later?

Yes, when the value is stored in the browser rather than read only from the current URL. The hidden field is populated at submit time from the stored value, so a return visit still carries the original click ID.

Can I capture UTM parameters alongside the GCLID in the same Duda form?

Yes. The same script that stores the GCLID also captures UTM parameters, so a single submission can carry channel, source, campaign, ad group, and ad-level detail. Add the corresponding hidden fields to the form for each value you want to keep.

What if my closed-deal volume is below 50 per month?

Send an earlier qualified event instead — for example, when a new deal is created in the CRM. Google's smart bidding strategies generally need at least 50 conversions per month to perform well, so a lower-volume closed-won signal can starve the model of data.

Do I need Zapier, or can Duda send the GCLID to my CRM directly?

Either route can work. Duda's built-in integrations can push form data into a CRM, and third-party tools such as Zapier or Make can do the same. The GCLID must be mapped into the CRM field in whichever route you choose.

How do I know the offline conversion actually reached Google Ads?

Run a test record through the whole chain and check that the conversion appears in Google Ads before increasing budget. The source registry links to a dedicated article on testing offline conversions.