UTM parameters do not inherently stop Google Ads from adding a GCLID. With auto-tagging enabled, Google can append it to a URL that already contains a query string.
If your lead records are missing GCLID, find where the value disappears. It may be absent on the incoming visit, removed by a redirect, lost during page navigation, or omitted when the form submits.
Check the URL before changing tracking templates
Google's auto-tagging test guide explains that GCLID is appended with an ampersand when the URL already has a parameter. For example, these parameters can coexist:
https://example.com/contact?utm_source=google&utm_medium=cpc&gclid=TestCapture123TestCapture123 is a made-up value for checking how the website handles the URL. It cannot match a Google Ads click or validate an offline conversion upload.
Confirm auto-tagging in Google Ads, then open the landing URL with a test parameter. Inspect the redirects and the page where your tracking loads. Check that the parameter reaches the page unchanged, including its capitalization.
Trace the value through each step
Redirects: Use your browser's Network panel to inspect the initial request and any redirects. Check HTTP-to-HTTPS changes, www/non-www redirects, and redirects made by landing-page tools. Fix a redirect that drops the query string rather than adding another copy of GCLID elsewhere.
Page navigation: If someone lands on one page and submits a form on another, reading only the current URL may miss the original value. Your capture method needs to preserve eligible attribution data and make it available to the eventual form, subject to the site's consent settings.
Form capture: Check the saved form entry. A hidden field that looks populated in the browser is not enough if the form integration does not submit it. Test failed validation followed by a successful submission and any AJAX or multi-page behavior.
CRM storage: Compare the saved field with the form entry. Look for empty mappings, truncation, case changes, extra whitespace, or automation that overwrites it.
Upload: Inspect upload diagnostics and the conversion action used. An upload can fail for reasons beyond the click ID, including the conversion time or action configuration. Do not treat every rejected record as a URL problem.
Keep URL configuration simple
A Final URL suffix can hold UTM parameters such as utm_source=google&utm_medium=cpc&utm_campaign={campaignid}. A tracking template may be needed for a tracking service or a more specific setup. Keep the configuration consistent at the account, campaign, ad group, and ad levels, and check for overrides.
The {gclid} ValueTrack parameter exists, but manually adding it everywhere is not a universal fix for missing attribution. It cannot supply a usable GCLID for every kind of visit. Google's ValueTrack reference.
Use the URL testing tools to inspect the assembled destination and use a synthetic ID to check capture and persistence. Neither that test nor an Ad Preview visit proves an offline match. Verify the full import with a genuine eligible ad interaction and its actual later outcome.
Some visits will not carry GCLID
Not every visitor came from a Google ad. Some ad contexts also use different measurement mechanisms, including situations where the GCLID ValueTrack value is empty. Google's iOS measurement guidance describes those limitations.
Where appropriate, enhanced conversions for leads can use eligible first-party data to improve matching. They require their own correct setup and do not guarantee that every lead can be attributed. Check the requirements of your chosen import method rather than manufacturing an ID for a record that has none.
If you want a manual checklist for reviewing capture, storage, and uploads, the OCT Setup Checklist is free with an account. Fixing the stage where the data is lost is what makes the rest of the process useful.