GCLID capture for CRM and Google Ads
If the click ID does not survive the form submission, you cannot reliably upload the later sales outcome back to Google Ads.
What needs to be captured
For Google Ads, store the available click identifiers and campaign parameters with the lead. That usually means GCLID, GBRAID, WBRAID, UTMs, landing page, first-touch timestamp and last-touch timestamp.
The practical flow
- Visitor lands from an ad with click parameters.
- The landing page stores the parameters in first-party storage.
- The values are copied into hidden form fields.
- The form submission creates a lead record with those fields attached.
- The CRM or workflow stores the lead status and sales outcome.
- Qualified outcomes are uploaded back to Google Ads against the click ID.
Why forms break this
Form plugins, embedded booking tools and third-party CRMs often strip context unless they are wired deliberately. A lead in the CRM without click IDs is useful for sales, but weak for PPC optimisation.
What good looks like
Every submitted lead has a durable lead ID, original landing page, first-touch parameters, last-touch parameters, click IDs where available, consent state where relevant and a later qualification status. That is enough to create a proper offline conversion loop.