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

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


Ad platforms have a specific alert for this, and its entire fix is to have someone spot what is wrong on your side. That is the complete instruction, and it skips the only question you really have: which hop of the chain loses the marker. The route answers that itself, out loud, 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 consider


Treat the first exposed target as the culprit and stop there. A parameter that is gone cannot return, so every hop after that one is blameless no matter how it looks.
Run the same request against an address you already know is sound before trusting the result on the suspect one. A healthy chain carries the marker through every hop and ends on a plain success, and seeing that once makes a faulty chain obvious.
Check the status codes as well as the targets. Some codes retain the method of the request and others may not, so a click that arrives as a form submission can drop data in a way that has nothing to do with the query string.
On a bulk list, the setting that passes the incoming query string through is off unless somebody turned it on, and that is the most probable cause of the warning on a zone of this kind.
If the marker makes it to the final response and reporting still shows nothing, the chain is not your problem any more. The drop is happening after the call lands, and that is a separate investigation, with other tools.
Send a request bearing a marker parameter and read the target line of every hop, not the address the browser finally shows. The hop whose target first comes back empty is the one that lost it.



A browser is the wrong instrument for this specific question. It displays the address you ended on and hides the route that created it, and it executes the page's own scripts, which can put a parameter back and make a broken chain look healthy. Anything that speaks clearly and traces the hops for you will do.


Where the leak is not a redirect at all


Parameters also disappear in places that never appear in a trace: a link rewritten by a mail client before it is sent, an in-app browser that removes 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.



The same test written out, with a clean route next to a broken one: unique click id on a redirect



Read from the top and stop at the first line that lost the marker. One call names the hop, and the fix falls to whoever controls that hop, which is usually a configuration rather than an outage.