Redirect tracer

HTTP chain hop by hop — vendors, macros, UTM, response body. Zero setup. Français

How it works

  1. Paste the URL — ad click, pixel or tracking link (DoubleClick, Xandr, TTD…).
  2. Choose a User-Agent — Chrome desktop, iPhone Safari or Googlebot. The header is sent on every hop; some ad servers adapt the chain based on the agent.
  3. Click Trace — the server follows each Location header one by one and times every request.
  4. Read the results — HTTP status, domain, vendor (IAS, DV, GAM, TTD, Criteo…), unresolved macros, UTM. Open Details for full headers and body preview (256 KB cap).

Frequently asked questions

What is a redirect chain and why should I inspect it?

It's the sequence of HTTP 3xx responses a server returns before reaching the final page. In ad tech, each hop typically corresponds to an intermediary (ad server, verification vendor, DSP…). Inspecting it helps detect unresolved macros, unknown intermediaries, or excessive latency.

How does it work without any installation?

Paste your URL and click Trace. Flownect runs the requests server-side to rebuild the chain. No extension, no account, nothing to install.

Does the Chrome, iPhone Safari or Googlebot menu really change the trace?

Yes. Every HTTP request includes the User-Agent you selected. Many domains (ads, affiliate, stores, anti-bot) return a different chain or target based on that header. It is not a real browser (no cookies, no JS), but the User-Agent is genuinely the one you picked.

What do unresolved macros mean?

Macros like {CACHEBUSTER} or {CLICK_URL} must be substituted by the ad server at delivery time. If they appear as-is, tracking pixels are not fed — guaranteed measurement losses.

What is the difference between a 301 and a 302?

A 301 is cached by the browser: the second click bypasses the intermediary ad server, skewing counts. A 302 forces a new request every time — the right behaviour in tracking chains.

How many hops is acceptable?

Beyond 5–7 hops, cumulative latency can trigger time-outs on mobile. The tool displays total latency to spot chains that are too long.

Are traced URLs stored by Flownect?

No. Requests are processed on the fly and are not logged or stored by Flownect.