Affiliate Tracker: Why You Need One and How to Choose

An affiliate tracker (also called ad tracking software) is a separate server-side app that intercepts every click before it reaches the offer, distributes traffic by your rules and collects statistics on your side rather than inside the ad account. Unlike a platform pixel, the tracker belongs to you: the data on what converted and how survives even if the account gets banned. Here is how a tracker differs from a pixel, which features actually matter, whether to pick self-hosted or cloud, and how a tracker saves your stats when the account goes down.

How a tracker differs from a platform pixel

A platform pixel is the ad network's own code: it lives inside your Facebook or Google account, optimises delivery for conversions and dies with the account. A tracker is an independent layer between the click and the offer: the user first lands on your tracker domain, which records the click parameters and redirects to the pre-lander or lander. How exactly a pixel loses data on a ban is covered in the pixel and conversion tracking guide; here the focus is the tracker as a separate class of software that insures against that loss.

• Data ownership — the pixel hands stats to the platform, the tracker collects them for you
• Granularity — the tracker sees geo, device, OS, browser, ISP and source per click
• Rules — the tracker distributes traffic by those parameters; the pixel only counts conversions

What a tracker does: the core features

• Flow split-tests — run several landers or offers in parallel and compare by conversion; the testing methodology is in the creative A/B testing breakdown
• Traffic distribution — by geo, device, language and OS, traffic is routed to different offers and landers automatically
• Network postbacks — the network reports a conversion to the tracker in real time, tied to a specific click
• Filtering — bots, fraud and off-target traffic are cut before they hit the offer
• Unified analytics — spend, revenue and ROI per slice in one place; which metrics to track at all is in the media buying KPIs guide

Postbacks: how the tracker sees real conversions

A postback is a server-to-server request from the network to the tracker at the moment of conversion: the network pings your URL with the click_id and lead status (lead, deposit, rejected). That is how the tracker ties a specific click to a specific sale, even when the network dashboard lags or is truncated. Without postbacks you judge payback by feel; with them, by fact, down to the individual creative and geo. How to calculate payback on that data is in the ROI vs ROAS article.

Self-hosted or cloud tracker

Trackers split into two classes, and choosing between them means choosing who holds your data:

• Self-hosted (Keitaro is a category example) — installed on your server; the data is fully yours, no click-volume limits, but you need a VPS and basic administration
• Cloud (SaaS) — the vendor hosts the tracker; easier start, no server needed, but the data sits on someone else's side and you pay per click volume

For grey verticals self-hosted is usually preferable: a cloud vendor can suspend your account over the traffic's vertical — and you lose the data again, the exact same problem as with a platform pixel.

A tracker moves your stats out of someone else's account onto your side: you can lose the account, but not the data on your winning setups.

How a tracker saves your stats when the account is banned

The main reason to run a tracker in grey verticals is not analytics so much as insurance. When an ad account gets banned, all its built-in stats vanish with it: creatives, audiences, conversion history, the trained optimisation. If you ran traffic through a tracker, that data is on your side: which setups converted, in which geos and on which devices, at what ROI. You spin up a new account and relaunch a proven setup immediately, without re-testing from scratch and without burning budget on hypotheses you already validated. What a setup is as a whole and which layers it consists of is in the affiliate funnel hub.

How to choose a tracker: criteria

1. Hosting type for your risk profile: self-hosted for grey verticals, cloud for a fast start on white
2. Redirect speed — tracker latency hurts both conversion and the lander's behavioral factors
3. Click limits and price per volume — at scale, SaaS can cost more than your own server
4. Ready-made postback integrations with your networks and sources
5. Flexibility of routing rules: geo, device, language, bot and fraud filters

Tracker + agency account: where both data and spend are protected

A tracker protects the data but not the spend itself: if the account gets banned every couple of days, no analytics will save the economics. The durable setup is a tracker on your side plus an ad account that survives grey-vertical moderation. Agency accounts with spend history provide the second half of that protection; how to match an account to your vertical and source is in the agency account selection guide. Together they close both points of failure: the tracker holds the stats, the account holds the spend.

Bottom line

A tracker is not "one more stats panel" — it is a separate infrastructure layer that moves traffic accounting out of someone else's account and onto yours. It gives you flow split-tests, geo and device routing and postbacks for honest ROI — but above all it insures your stats against an account ban. Paired with a durable ad account, a tracker turns losing an account from a disaster into a working moment.

Frequently asked questions

Why do I need a tracker if the ad account already has stats?

The account's stats live inside the account and vanish with it on a ban, and they never see conversions on the network's side. A tracker collects the data on your side and, via postbacks, ties a click to a real sale — it stays even when the account is gone.

How does a tracker differ from a platform pixel?

A pixel is the ad network's code inside the account: it optimises delivery and dies with the account. A tracker is an independent server-side layer between the click and the offer that routes traffic by rules and stores stats on your side.

Which tracker should a beginner choose?

For grey verticals, self-hosted (data fully yours, no risk of a vendor ban over the vertical); for a fast start on white traffic, a cloud SaaS is simpler. Watch redirect speed, click limits and ready postback integrations with your networks.