The Click Id Vanishes Somewhere In The Chain: What To Check

The click id vanishes somewhere in the chain: what to check


Ad platforms have a specific warning for this, and its entire remedy is to have someone find what is wrong on your side. That is the complete instruction, and it bypasses the only question you actually have: which hop of the chain drops the marker. The route answers that itself, aloud, if you ask it with one request instead of a browser tab. The checks below take about a minute together and they run in any order.


What to look at


Regard the first exposed target as the culprit and halt there. A parameter that is missing cannot come back, so every hop after that one is blameless no matter how it appears.
Check the status codes as well as the targets. Some codes preserve the method of the request and others may not, so a click that arrives as a form submission can lose data in a way that has nothing to do with the query string.
If the marker survives to the last response and reporting still shows nothing, the chain is not your issue any more. The loss is occurring after the call lands, and that is a separate investigation, with various tools.
Run the same request against an address you already know is healthy before trusting the result on the questionable one. A healthy chain carries the marker through every hop and ends on a plain success, and seeing that once makes a broken chain obvious.
Read what turning that option on actually does before switching it on. It does not append the incoming parameters to the ones on your target address; it replaces them, so a target that has parameters of its own comes out stripped.


Where the leak is not a hop at all


Parameters also vanish in places that never appear in a trace: a link altered by a mail client before it is sent, an in-app browser that strips the address before the request goes out, a script that replaces the address after the page has loaded. None of those leave a hop to look at. If the trace is clean and the numbers are still missing, that is where to go next, and it is worth knowing before an afternoon disappears into rules that were fine all along.



A browser is the wrong tool for this particular question. It shows the address you landed on and hides the route that produced it, and it runs the page's own scripts, which can put a parameter back and make a broken chain appear healthy. Anything that speaks plainly and follows the hops for you will do.



The identical test written out, with a clean route next to a broken one: agent readiness score



Scan from the top and stop at the first line that lost the marker. One call identifies the hop, and the fix falls to whoever owns that hop, which is usually a setting rather than an incident.