Tracker vs TDS: What's the Difference and Which Do You Need

People use "tracker" and "TDS" as if they were the same thing, and in many products they overlap. They are still two different jobs. A TDS decides where a click goes. A tracker records what the click did afterwards. Which one you need depends on the questions you are trying to answer.

This article lays out what each one does, where they overlap, a side-by-side table and a checklist you can run against your own setup.

What a TDS does

A traffic distribution system is the layer between the ad and the offer. The ad links to the TDS, and the TDS applies your rules to every click: send German Android users to offer A, send everyone from a data center to a page you set, split the rest 50/50 between two landers. It works at the moment of the click and its output is a destination.

The main features of a TDS are conditional routing, split shares, bot filtering and the ability to change destinations without touching the ad. We describe it in detail in What is a TDS in affiliate marketing.

What a tracker does

A tracker is about measurement. It stores every click with its parameters and gives each one an identifier. When the affiliate network records a lead or a sale, it calls a postback URL and passes that identifier back. The tracker matches the conversion to the click, and now you know which campaign, creative, placement or landing page the money came from.

The core of a tracker is click storage, a click ID, postback handling, cost and revenue records and reports. Reports let you group by any parameter you passed in: source, campaign, ad, placement, country, device, offer. This is the part where you find out that one placement gives you nearly all the profit and three others lose money.

Where they overlap

Most trackers include routing, because a tracker has to send the visitor somewhere. Many TDS products include basic statistics, because you need to see clicks. That is why the labels blur. Keitaro, Binom, Voluum and RedTrack are examples of products usually called trackers, and all of them include some routing. Several cloud services started as a TDS and added tracking later.

The question is not what the product is called. Ask what it can do:

• How rich is the routing? Which conditions, how many, can they be combined?
• How good is the bot filtering? Is it configurable, and are filtered clicks logged with a reason?
• Does it receive postbacks, and does it show revenue, cost and ROI?
• How flexible are the reports? Can you group and filter by any parameter?

Products differ most on those four points, and they matter more than the category label.

Side-by-side comparison

The table shows typical positions. Individual products fall somewhere between the two columns, so test the ones on your shortlist rather than trusting a category.

Who needs what

You only need a TDS when

• You work with a single network that gives you its own reports, and you only need to split traffic by geo or device.
• Your main pain is bots and junk clicks, and you want to see them in a log.
• You want a stable link in the ad and the freedom to swap offers.
• Your volume is small enough that a spreadsheet and the network's stats answer your questions.

You only need a tracker when

• All your traffic goes to one landing page and one offer, so there is nothing to route.
• The reason you want it is profit by placement, creative or campaign, based on postbacks.
• You already have bot protection elsewhere, for example at the landing page level.

You need both when

• You buy traffic from several sources, send it to several offers and want to know ROI per source.
• You pay for clicks and want to see how many of them were bots before you look at conversions.
• Offers rotate often and you need history that survives the swap.

If the earlier question is whether you need a tracker at all, When you need a tracker goes through the signs that UTM tags and a spreadsheet no longer cut it.

A worked example

Say you spend $200 on 2,000 clicks from two placements, A and B, at $0.10 each. You send them all to one offer that pays $20 per approved lead. Hypothetically placement A gives 1,000 clicks and 6 approved leads, placement B gives 1,000 clicks and 1 approved lead.

• Placement A: cost $100, revenue 6 x $20 = $120, ROI +20%.
• Placement B: cost $100, revenue 1 x $20 = $20, ROI -80%.

Only something that receives postbacks can show you this split. A TDS on its own would tell you 1,000 clicks arrived from each placement and how many of them were bots. It would not tell you that B loses money. Now add a second fact: of B's 1,000 clicks, 400 were flagged as data-center traffic. A TDS shows you that immediately, in the log, with the reason. Together the two tell you B is both weak and polluted, and you can cut it with confidence.

Decision checklist

Go through these and count the yeses in each block.

1. Do you send the same traffic to different destinations depending on country, device, OS, language or time? If yes, you need routing.
2. Do you pay for clicks and suspect some are bots? If yes, you need a bot filter and a click log.
3. Does your network send postbacks and do you need profit per placement? If yes, you need a tracker.
4. Do you change offers or landers more than once a month? If yes, a stable link and central rules save time.
5. Do you run split tests on landers? If yes, you need shares or random distribution among URLs.
6. Do you need to hand reports to a partner or a client? If yes, check the report depth and export options.
7. Is your monthly click volume large enough that a limit on clicks or links on a plan could stop you? If yes, compare limits before you commit.

Yes on 1, 2, 4 or 5 points to a TDS. Yes on 3 or 6 points to a tracker. Yes on both groups points to a product that covers both, or two tools wired together.

Where TDS.SO sits

TDS.SO started as a traffic distribution system. Routing has 20+ conditions, rules are checked top to bottom, and the first match wins. Bot filtering has levels from Off to High, a JavaScript browser check and a custom mode, and filtered clicks are logged with a reason. See traffic filtering and analytics for the full lists.

The tracker part, with postbacks, conversions, revenue and ROI, is in beta. Revenue is counted as approved conversions and cost as all clicks. If you depend on a mature tracker today, say Keitaro or Binom, run a trial of the TDS.SO tracker alongside rather than switching at once. The migration page explains how help works; it is manual, with no one-click import.

FAQ

Can a tracker replace a TDS?

Often yes, if its routing and bot filtering are enough for your traffic. Check the depth of conditions and whether filtered clicks are logged with a reason. If either is thin, you may want a TDS in front of it.

Can I use a TDS and a tracker together?

Yes. A common layout is the TDS link in the ad, with the destinations being tracker campaign links. It does add a hop, so test the load time and make sure the click ID reaches the tracker.

Is a tracker needed if I only use one network?

Not always. Most networks give their own statistics. A tracker becomes useful when you want to compare placements or creatives across sources, or when you have several networks and want one report.

Do I need to know about postbacks to start?

You need the basics. A postback is a request your network sends to a URL on your side when a conversion happens, with the click ID in it. Most networks call that parameter something like {clickid} or {subid}; check your network's docs for the exact macro.

Which one should I set up first?

If bots and mixed geo hurt you now, start with routing and filtering. If your traffic is clean and single-destination, start with conversion tracking.

For the routing and filtering side, see redirect rules and pricing; plans start at $9.99 per week with unlimited clicks, domains and links. You can compare the tools side by side on the compare page.