gclid not passed to landing page

Introduction

If the landing page never sees gclid, Google Ads cannot match conversions to the right click. It is a common complaint after migrating to new trackers, adding vanity URLs, or copying links between accounts.

The challenge is tracing where gclid fell off without guessing. Redirect stacks, consent banners, and caching plugins all try to rewrite URLs, so you need hard evidence before adjusting templates.

This article outlines how gclid should propagate through redirects, how to spot the hop that removed it, and how to validate the fix with Redirect Checker, Click ID Extractor, UTM Builder, Postback Tester, and Facebook CAPI Tester.

Explanation of the concept

When auto-tagging is enabled, Google Ads appends gclid to the ad's destination URL. Every redirect in the stack should forward the full query string, and the landing page should store it in cookies or hidden fields for CRMs and offline conversion imports.

If a redirect rebuilds the URL without copying parameters, a vanity link points to a clean URL, or JavaScript rewrites window.location, gclid disappears before any script can capture it. The landing page loads, but the click ID never made the trip.

Common problems

Vanity domains, geo routers, and smartlinks often rebuild tracking templates incorrectly. They pass utm_source, utm_campaign, or other parameters but forget to merge the incoming query string, so the first hop already loses gclid.

Infrastructure issues cause the rest: CDN rules that normalize URLs, caching systems that ignore unusual parameters, or consent tools that delay the scripts responsible for copying gclid.

• Redirects that point to https versions of the page without re-attaching gclid.
• JavaScript or meta refreshes that overwrite window.location with hard-coded parameters.
• Smartlinks that only pass along a whitelist of parameters and drop everything else.
• Teams that manually paste 'clean' URLs into Google Ads and forget to re-enable auto-tagging.
• Security middleware that strips gclid before the page loads.

Step-by-step troubleshooting

Replicate the problematic journey and log every hop. Start with the ad URL, feed it into Redirect Checker, and save the query string after each redirect. Pay attention to differences between GEOs, devices, and consent states.

Once you know which hop removed gclid, coordinate with the owner of that redirect. Provide logs, decoded URLs, and recommended templates so they can merge the query string correctly.

1. Audit redirects with Redirect Checker

   Record the status codes and query strings for each hop, then flag any step where gclid vanished.

2. Inspect the landing page

   Use Click ID Extractor to see whether gclid reaches the final URL. If not, use the redirect log to locate the failure.

3. Share canonical templates

   Build a clean set of Google Ads links with UTM Builder and distribute them to every buyer, channel partner, or agency.

4. Re-run postbacks

   After fixing redirects, fire a mock conversion through Postback Tester and confirm that partners now see gclid.

5. Validate server payloads

   Replay the flow with Facebook CAPI Tester to ensure your team can still package click IDs into server-side events.

Tools that help solve the problem

Consistent tooling keeps your investigation grounded. Redirect Checker shows where gclid vanished, Click ID Extractor proves whether it returns, and Postback Tester ensures downstream systems now see it.

Store each report alongside tickets and onboarding docs so future migrations have a reference.

Conclusion

Redirects, vanity links, and caching layers are convenient, but each one is an opportunity to lose gclid. A structured audit keeps that risk under control.

Collect evidence, fix the problematic hop, and archive the before-and-after outputs so the issue does not return.

Tools mentioned in this article

More affiliate tracking guides

From the Tracking Tools blog