If a Google Ads click ID disappears before the landing-page tag can read it, inspect each redirect rather than rebuilding the form. The failing hop may belong to the CDN, HTTPS redirect, hostname redirect, language routing, or WordPress. Fixing a hidden field cannot recover a value that never reached the page.
Google explains how auto-tagging adds the click identifier in its auto-tagging guide. The exercise below checks URL transport with a synthetic marker. It does not validate a real advertising click or prove that a conversion will be attributed.
Use a harmless marker, not a customer identifier
Choose one approved landing page and append gclid=HandLRedirectTest123. Use a question mark for the first query parameter and an ampersand when a query already exists. Keep the parameter before any #fragment. Do not insert personal data, credentials, or a real customer's click ID into shared diagnostics.
Test the exact landing shape used by the campaign, including a legacy path or hostname when that is what the ad currently targets. Do not click your own live advertisement repeatedly to create test traffic.
Record each server redirect
For your own public page, a GET request can show response headers through the chain:
curl -sS -L --max-redirs 10 --max-time 20 -D - -o /dev/null 'https://example.com/offer?gclid=HandLRedirectTest123'
Replace the example URL. Inspect each Location value and the final destination. Curl does not execute JavaScript, so repeat in the browser with Network open and Preserve log enabled. If the marker survives the server chain but disappears afterward, investigate client-side navigation or URL cleanup.
Transport: Synthetic value survives redirects. Existing query: No duplicate separators. Browser: Client-side navigation checked. Measurement: No fake conversion uploaded. Explanatory checklist, not a customer test result.
Assign the first failing hop
Build a trace with the incoming URL, response status, outgoing Location, marker present or absent, and the layer that owns the redirect. For example, a synthetic test might preserve the marker through HTTPS normalization but lose it on a language redirect. Repair the language rule rather than adding competing redirect plugins.
Preserve approved campaign parameters with a structured URL operation. Do not blindly concatenate question marks or decode and re-encode the entire URL repeatedly. Avoid forwarding arbitrary sensitive query parameters to another domain. Review the allowlist with the site's measurement and privacy owner.
Run a small regression matrix
Test a URL with no query, one with the synthetic marker, one with an existing non-sensitive parameter, and one with an anchor fragment. Include the canonical path and an actual retired campaign path. Confirm there is no redirect loop, duplicate parameter, accidental hostname change, or broken page response.
Then test the real browser timing. A marker removed after a tag has read it is different from a marker removed before collection. Do not conclude solely from the final address bar. Use the authorized tag debugger and the site's consent policy to verify what was available at the measurement event.
Once the landing path preserves the value, continue with form and CRM click-ID mapping. Never upload the synthetic marker as a real offline conversion. HandL WP can trace the redirect and attribution handoff without changing unrelated campaign or CRM settings.
References reviewed October 9, 2026. Examples are explanatory, not customer test results.