Global Redirect

A global redirect is the safety net at the very bottom of your program. When a click can't be routed to a real destination — it was blocked by a traffic rule, the offer expired, an offer cap is full, or the link points at something that no longer exists — the visitor still has to go somewhere. The global redirect is the single account-wide fallback that catches all of it, so no visitor ever hits a broken page and no click silently disappears into nothing.

The fallback chain

Unrouteable traffic walks a chain from most specific to most general, and the global redirect is the last real link:

traffic-rule redirect → campaign fallback → offer redirect → global redirect → (nothing)

Each link is tried in turn; the first one that's set wins. The global redirect only fires when nothing more specific applies, which is exactly when you most need a graceful destination.

What it can be

The global redirect accepts two kinds of value:

• A URL — send the visitor there with a 302 redirect (a house offer, your homepage, a "this promotion has ended" page).
• An HTTP status code — 404 (Not Found, shown as a clean generic page that reveals nothing about the URL), 410 (Gone), or 204 (a silent dead-end).

Left empty, it defaults to 404.

A worked example

You run seasonal offers that expire. When a holiday offer ends, its links are suddenly unrouteable — but affiliates still have them published. Rather than letting those clicks dead-end, you set your global redirect to https://yourbrand.com/offers, a page listing your current promotions. Now a visitor who clicks a retired link lands on live offers instead of an error, and you recover traffic you would otherwise have lost. For a program where leaking traffic to a generic page is worse than nothing, you'd set it to 404 instead and reveal nothing.

How this works in LimeliJourney

In LimeliJourney the global redirect is set once, account-wide, on the Settings page (Instance Settings → Global redirect) — part of how tracking handles the edges of your program. New accounts default to 404, so unrouteable traffic returns a clean Not-Found page until you point it somewhere. To capture that traffic instead, enter a URL — a house offer or your homepage. Because it sits at the end of the fallback chain behind rule redirects, campaign fallbacks, and offer redirects, it never overrides a more specific destination; it only catches what would otherwise have nowhere to go.