What is Redirect Tracking?

Redirect tracking is the classic CPA/arbitrage click-counting scheme: the user hits the tracker link, the server logs the click, then returns an HTTP redirect (usually 302, sometimes 301 or meta refresh) to a landing page or offer URL.

The click always passes through the tracker domain: IP, User-Agent, GEO, referer, and a click ID are captured. Downsides are added latency, possible losses when redirects are blocked, and a visible intermediate domain.

Typical flow

1. Ad → https://track.example/click?campaign=5&...
2. Tracker logs the click and substitutes macros in the offer URL.
3. 302 → landing or direct offer with {clickid}.

Vs. direct tracking

With direct tracking, a pixel or JS on the landing sends data without a visible redirect. Redirect is simpler for beginners and required when you cannot edit landing code (direct linking to the network offer). Some sources (push, pop) are historically redirect-based.

Technical notes

Double redirects (tracker → pre-land → offer) raise bounce. SSL on the tracking domain is mandatory. When a domain is blacklisted, fast rotation of tracking URLs in campaigns is needed. Server-side click loss on tracker downtime is critical — uptime monitoring is required.

See also: tracker, tracking domain, click ID, direct tracking.