GCLID Lost After Redirect: Find and Fix the Broken Hop
Updated
Compare the entry URL with every redirect destination and find the first transition that removes or changes gclid. Fix that routing rule and retest the entire route. A synthetic identifier can verify parameter preservation, but only valid Google Ads click data and the intended measurement setup can establish attribution.
Keep Google Ads click context intact from the campaign entry URL to the page that reads it.
The ad destination can load normally while a redirect drops the Google click identifier. This often happens when a short link, locale rule or canonical-host redirect rebuilds a destination without its query string. UTMs may survive because a rule explicitly allows them, while gclid is discarded. Diagnose the route before changing conversion tags or replacing auto-tagging with manual tags. The task is to preserve the approved identifier unchanged and then verify the measurement layer independently.
What to check
1. Confirm what the entry URL should contain
Check the campaign's auto-tagging configuration with the Google Ads owner and inspect the actual resolved landing URL. Typing a clean destination into the address bar does not create a Google Ads click identifier. Do not label the site broken simply because that clean URL has no gclid. Establish whether the identifier was present before the suspected redirect.
2. Use a clearly synthetic value for routing tests
To test forwarding without generating ad clicks, use a URL such as https://go.example.com/offer?gclid=AdVaultQA_20261018&utm_source=google&utm_medium=cpc. The example domain is a placeholder and the identifier is invented. Its survival tests the URL route only. It cannot verify Ads attribution, a valid advertising click or conversion matching.
3. Record HTTP and browser-driven transitions
Enable Preserve log in the browser Network panel and load the test entry URL. Compare each document request and Location destination, then look for JavaScript or meta-refresh navigation. Record the full URL at each stage. A server-only redirect trace can miss routing that happens after a document has loaded, including consent or language interstitials.
4. Identify the first rule that changes the identifier
Find the earliest transition where gclid disappears or its value changes. Review the specific shortener, CDN rule, server rewrite, CMS redirect or tracking template that produced that URL. An allow-list may preserve utm_source while dropping gclid. Another rule may overwrite the query string when it changes the hostname or path. Fix the identified rule rather than every redirect at once.
5. Preserve the value without opening every parameter
Keep the approved click identifier intact and retain the campaign fields required by your measurement design. Avoid lowercasing values, splitting encoded destinations incorrectly or replacing the whole query with a fixed template. Explicitly review what is forwarded; blindly copying every incoming field can carry unrelated information into a third-party destination. Retest both the identifier and the intended landing path.
6. Check URL cleaning and measurement timing
If gclid reaches the final document request but vanishes from the address bar, inspect client-side URL cleaning. Determine whether the intended Google tag or conversion integration had access to the identifier before it was removed. Also record consent and browser restrictions. The identifier appearing in a request does not establish that storage, collection or a later conversion occurred.
7. Review the remaining funnel separately
A redirect fix does not verify cross-domain continuity, account linking, conversion configuration or an offline-import pipeline. Check the relevant Google diagnostics with the account owner. If your funnel uses another domain, confirm the measurement design on both sides. Do not fabricate a replacement click ID or assume that adding UTMs can reconstruct an identifier already lost.
8. Retest all affected route variants
Repeat the original entry route after the change, including relevant host, mobile and locale variants. Keep the before-and-after hop trace and test date. Use AdVault's UTM Checker or full campaign check to inspect observable URL evidence, then validate the authorised Google measurement path separately. Record parameter preservation and attribution validation as separate outcomes.
What you see and what it usually means
UTMs survive, but gclid disappears
The responsible rule may forward a limited parameter list. Inspect that allow-list before changing the campaign tags.
The final request has gclid, but the address bar loses it
Investigate client-side URL cleaning and the order in which measurement reads the landing URL.
A synthetic ID survives, but Google Ads reporting is unchanged
Routing has been tested. Valid click data and account-side measurement still need their own verification.
A typical case
Illustrative trace: https://go.example.com/offer?gclid=AdVaultQA_20261018 redirects to https://www.example.com/en/offer without a query string. The rule producing the second URL is the first observed loss. After a fix, the destination retains ?gclid=AdVaultQA_20261018. That is evidence that this test value survives this route. It is not a real Google Ads click and establishes nothing about recorded conversions or advertising performance.
Before you call it fixed
- Expected entry identifier established
- Synthetic tests labelled as routing tests
- Every HTTP and browser navigation recorded
- First parameter-changing rule identified
- Approved identifier value preserved intact
- Final-page measurement timing reviewed
- Remaining funnel verified separately
- Production route variants retested
Check the production URL
A correct configuration on paper can still fail after redirects, deployment or consent logic. Use the exact URL your campaign will send traffic to.
Check a campaign URLVerify the signal directly
Related troubleshooting guides
Common questions
Does gclid=TEST prove that Google Ads tracking works?
No. A synthetic value checks whether the website accepts and forwards a parameter. It cannot validate an advertising click or conversion attribution.
Can a 301 redirect preserve GCLID?
Yes. The important evidence is the destination URL produced by the rule. Check whether it retains the required parameter and value through the complete route.
Should I remove auto-tagging if a redirect drops GCLID?
Identify and repair the forwarding problem first. Changing the campaign's tagging method is a separate measurement decision and does not repair the route.
Technical references
Scan the full campaign route.
See where the click lands, what survives the redirect chain and which supported tracking signals are visible on the final page.