Skip to main content

Redirection Checker

Redirection Checker

J
Written by Jorge Rubia

The Redirection Checker lets you trace every hop a URL makes — from the initial click to the final landing page — so you can verify that a tracking link, offer URL, or redirect chain is working as expected before sending real traffic through it.

You'll find it under Tools → Redirection Checker.


Running a test

Click New test to open the test configuration modal.

Fill in the following fields:

  • URL (mandatory) — the URL you want to test. This can be a tracking link, an offer URL with macros, or any redirect chain you want to inspect.

  • Related offer (optional) — select an offer to automatically populate the URL field with that offer's tracking link, including its unreplaced macros.

  • Randomize values — only relevant when a Related offer is selected. Click this to automatically generate random values for all the macros present in the offer's tracking URL, so the test can run without you having to manually fill in each macro.

Emulation settings

These fields control how the click is simulated:

  • Operating system (mandatory) — the OS emulated when the request is made

  • Country (mandatory) — the country emulated when the request is made

Advanced

Toggle Advanced to reveal additional emulation options:

  • Connection typeWifi or Carrier

  • Carrier — if Connection type is set to Carrier, select the specific carrier to emulate from the list

  • City — the city emulated when the request is made

Once everything is configured, click Begin test.


Reading the results

The Redirection Checker simulates a real click using the operating system, country, carrier, and other parameters you configured, and follows every redirect until it reaches the final destination.

The results panel shows:

  • Test information — a summary of the test: the full test URL, test duration, related offer (if any), and the emulation settings used (operating system, country, city, connection type)

  • Test results — a visual chain showing each redirection in order, including:

    • The full URL at each hop

    • The HTTP status code returned (e.g. 302 for a redirect, 200 for the final destination)

    • The request duration for that specific hop

The final node in the chain (highlighted in green) represents the landing page where the redirect chain ends.


Test history

Every test you run is saved and listed in the main Redirections checker table, showing:

  • Test URL — the URL that was tested (truncated, with a copy icon to retrieve the full value)

  • Test entity — the related offer, if one was selected

  • Author — who ran the test

  • Tested at — date and time of the test

  • Test duration (ms) — total time for the full redirect chain

  • Redirections — number of hops detected

  • Result — outcome of the test

Click on any row to expand it and view the full test information and results again.


Related articles

Did this answer your question?