A tracker is the software that sits between your traffic and the offer and writes down everything: which ad, placement and creative each click came from, where it was sent, and which clicks became conversions. Without one, you only know totals; with one, you know what to cut and what to scale.
An affiliate tracker is a system that records each click with its source data, redirects it to a landing page or offer, and attributes incoming conversions back to that click. The core loop is: a click arrives with tokens from the traffic source (campaign, placement, creative, device), the tracker stores them with a unique click ID, sends the user on with that ID appended to the offer URL, and later receives a postback containing the same ID when the conversion happens. Reports then group revenue, cost and conversions by any combination of the stored fields.
Trackers come in two models. Self-hosted trackers such as Keitaro and Binom run on your own server: lower per-click cost at volume, full control over data and redirect speed, and the responsibility of hosting and maintenance. Cloud trackers such as Voluum and RedTrack are hosted services: quick to start, priced by event volume, with integrations for ad platforms built in. Both offer the same essentials: campaign and flow rules (split testing landers and offers, routing by GEO or device), cost import from traffic sources, postback and pixel endpoints, and bot filtering.
Networks have their own tracking platforms (Scaleo, Everflow, HasOffers-style systems, or an in-house one) that track the affiliate’s clicks to the offer. The affiliate’s tracker is different: it covers the part of the funnel the network cannot see, the traffic source, the prelander and the split tests, and it is where cost meets revenue. The two connect through the click ID passed in a sub-ID parameter and returned in the network’s postback.
A tracker is only as good as its setup. The decisions that matter are passing every useful token from the traffic source, mapping the network’s postback macros correctly, importing costs so ROI is real, hosting close to the audience so redirects add little latency, and securing the postback endpoint. Discrepancies between tracker and network are normal within a few percent; larger gaps almost always trace back to one of those steps.
You run one offer on a native source through two prelanders. The network reports 300 approved conversions and 9,000 USD revenue for the week. The tracker, with cost imported, shows the split.
| Path | Clicks | Cost | Conversions | Revenue | ROI |
|---|---|---|---|---|---|
| Prelander A, desktop | 6,000 | 1,800 USD | 96 | 2,880 USD | +60% |
| Prelander A, mobile | 14,000 | 3,500 USD | 126 | 3,780 USD | +8% |
| Prelander B, desktop | 3,000 | 900 USD | 48 | 1,440 USD | +60% |
| Prelander B, mobile | 7,000 | 1,750 USD | 30 | 900 USD | −49% |
The network sees a campaign at 9,000 USD revenue; with 7,950 USD of cost it is a modest 13% ROI. The tracker shows that prelander B on mobile loses half its spend while desktop on either prelander returns 60%. Pausing one path lifts ROI to about 30% on the same traffic. None of this is visible without the click ID linking the source, the prelander and the device to the conversion. Numbers are illustrative.
How affiliate tracking really works: clicks, click IDs, postbacks, server-to-server flows and why clean attribution is the foundation of a profitab...
Intermediate · 10 min readHow S2S postback tracking works: click ID, macros, where the postback URL goes, testing, deduplication, and why server-side is the durable standard...
Core · 10 min readHow to build an affiliate dashboard that drives decisions: the five to eight metrics that matter, segmenting by source, offer and GEO, leading vers...
Advanced · 11 min readHow to diagnose affiliate tracking problems: which tracker, network and platform discrepancies are normal and which are alarming, plus broken postb...
It records each click with its source data, redirects it to the lander or offer with a unique click ID, receives conversions by postback or pixel, and reports revenue, cost and ROI by any source field.
Self-hosted (Keitaro, Binom) is cheaper at volume and gives full control but needs a server and maintenance; cloud (Voluum, RedTrack) is faster to start and priced by events. Both cover the essentials.
For paid traffic, yes. The network tracks clicks to the offer; only your tracker sees the traffic source details, prelanders, split tests and costs that decide what to scale.
Small gaps are normal (timing, deduplication, approval status). Large gaps usually mean lost click IDs, wrong postback macros or different attribution windows.
References are listed as plain text on purpose; look them up by title and publisher. Updated: 2026-10-06.
Run them inside a network with real tracking, roughly 48-hour payouts and a dedicated manager.
Join the network