<b>Redirect health — 5 checks before redirects cost you</b>

<b>Redirect health — 5 checks before redirects cost you</b>

Every hop in a redirect chain is a place to lose traffic, leak click IDs, or trip an ad-network scan. Audit the chain, not just the final URL.

— Count the hops. Tracker → offer should be one 302, maybe two. Three or more = added latency and more failure points. Map it with a redirect tracer, not by clicking.
— Confirm click ID survives every hop. Click through, inspect the final landing URL's query string. If <code>clickid</code> is gone by hop 2, every conversion after it is orphaned.
— Check the status codes. 302 (temporary) for offer rotation, never 301 (permanent) — browsers cache 301 and freeze your distribution.
— Test mobile and desktop user-agents separately. A redirect that 200s on desktop can 403 on mobile if the offer geo/device-gates.
— Measure time-to-final-URL. Over 600ms and you're bleeding clicks on slow connections before the LP loads.

Do this from the actual target GEO via proxy. A redirect that's healthy from your office can be a dead end from the traffic's country.

Run this before every launch.