An affiliate tracking discrepancy is the gap between what your traffic source, your tracker and the affiliate network each report for the same traffic. Some gap is always normal, because each system counts at a different moment and filters differently. A discrepancy becomes a problem when it is large, suddenly changes, or affects conversions and revenue rather than just clicks.

This guide explains the usual causes, how to set an acceptable range for your own campaigns and the signs that a gap is hiding broken tracking, bots or under-reporting.

Why the numbers never match exactly

Picture the journey: an ad is served and clicked, the traffic source counts a click, the visitor's browser requests your tracker, the tracker redirects to a lander or offer, and the network records a click when its page loads. Visitors drop out at every step, and each system applies its own rules.

Mechanical causes (normal)

  • Drop-off between steps: visitors close the tab, hit back or lose signal before the next request completes. Slow redirects and heavy landers increase this.
  • Different definitions: one system counts every click, another counts unique clicks per visitor per day.
  • Filtering: traffic sources, trackers and networks each filter bots, duplicate clicks and blocked GEOs differently.
  • Time zones and cut-off times: a click at 23:50 in one system may fall into the next day in another.
  • Reporting delays: conversions reported hours or days later shift between date ranges.
  • Currency conversion: revenue in EUR at the network and USD in the tracker will differ by the exchange rate used and when.

Problem causes (investigate)

  • Broken links or redirects stripping parameters.
  • Missing or misconfigured postbacks.
  • Bot traffic or click fraud at the traffic source.
  • Browser restrictions removing cookies or click IDs.
  • Program-side under-reporting or reversals.

Traffic source vs tracker clicks

This is the gap media buyers see first. The traffic source counts the click on its side; your tracker only counts it when the visitor's browser reaches your tracking domain. Anything that stops the browser getting there widens the gap: slow mobile connections, aggressive pop-up blockers, accidental clicks closed instantly, and bots that register a click without following the redirect.

Gaps are typically wider on formats prone to accidental or automated clicks, such as pop and push traffic, than on search or native. If one placement shows a much larger gap than the rest of the campaign, treat it as a quality signal. Our guides to detecting bot traffic and whitelisting and blacklisting placements show what to do next.

Tracker vs network stats

Between your tracker and the network, clicks should be closer, because both are counted by the browser following your redirect. Common causes of remaining gaps:

  • Visitors who see your lander but do not click through to the offer (the network never sees them, which is expected).
  • The network counting unique rather than raw clicks.
  • Redirect chains at the network, such as smart links routing to different offers, losing visitors on the way.
  • Network filtering of traffic it considers invalid or out of GEO.

For conversions, the network is usually the record you are paid against. If your tracker shows fewer conversions, the postback is the first suspect; if it shows more, check for duplicate postbacks or reversals the tracker does not know about. Our guide to conversions not tracking has a full diagnostic flow.

What is an acceptable tracking discrepancy?

There is no official industry standard, and you should be sceptical of anyone quoting a universal percentage. Acceptable gaps depend on the traffic type, the device mix, the number of redirects and each system's filtering. The practical approach is to set your own baseline:

  1. For each traffic source and offer, record the click and conversion gaps over two to four normal weeks.
  2. Treat that as your baseline, separately for clicks and conversions.
  3. Set a tolerance band around it, and investigate when a campaign moves outside it.
ComparisonWhat a stable gap usually meansWhat a sudden change usually means
Traffic source vs tracker clicksNormal drop-off and filteringBots, a new placement, slow redirects
Tracker vs network clicksLander drop-off, unique countingBroken link or network redirect change
Tracker vs network conversionsTiming, minor postback gapsPostback broken, platform change, reversals
Network conversions vs paymentsApproved versus pendingReversals or under-reporting

Hypothetical example: a buyer's baseline shows the tracker counting 8% fewer clicks than the traffic source on a native campaign. One week, a single placement shows 40% fewer. The campaign average barely moves, but that placement is either bot-heavy or delivering accidental clicks, and should be paused pending a refund request.

When a discrepancy signals a real problem

Investigate promptly if you see any of the following:

  • A sudden step change on a specific date, especially after a site, link, consent or platform change.
  • Conversion gaps much larger than click gaps. Click gaps are mechanical; conversion gaps usually mean tracking or reporting failures.
  • Gaps concentrated in one browser or device, pointing at browser privacy features. See Safari ITP and affiliate tracking.
  • Gaps concentrated in one placement or sub-source, pointing at traffic quality.
  • Conversion rate dropping only for you while the program says the offer is stable, which deserves careful evidence-gathering. Our guide to spotting affiliate shaving explains how to build a case.

Fraud can cut both ways: bots inflating clicks at the source, or incentivised and fake conversions creating reversals later. Our overview of types of affiliate fraud covers both.

How to reduce discrepancies

  • Cut redirects: every hop loses visitors. Use direct tracking where possible and fast tracker servers near your GEOs.
  • Use your own tracking domain to reduce ad-blocker losses.
  • Use S2S postbacks rather than pixels for conversions.
  • Align time zones across tracker, traffic source and network reports.
  • Pass the source's click ID into your tracker so you can match clicks one to one when disputing.
  • Reconcile weekly on your top campaigns, and keep exports as evidence.

A simple weekly reconciliation routine

  1. Export the same seven-day period from the traffic source, your tracker and the network, all set to one time zone.
  2. Line them up by campaign, then by placement or sub-ID for the biggest spenders.
  3. Calculate the click gap and the conversion gap for each row as a percentage of the larger figure.
  4. Flag any row outside your tolerance band, and any row where the conversion gap is much wider than the click gap.
  5. For flagged rows, check the change log and run a test click or conversion before contacting anyone.
  6. Save the exports. If you later need a refund from a traffic source or a correction from a network, dated evidence is what gets results.

Half an hour a week on your top campaigns catches most problems before they cost a month of margin.

Frequently asked questions

Which number should I trust?

For spend, the traffic source's bill. For revenue, the network's approved conversions. Your tracker is the tool that joins them, so use it for decisions, but reconcile it against both.

Can I get refunds for click discrepancies?

Some traffic sources accept refund requests for clearly invalid traffic, usually with evidence such as tracker logs and bot flags. Policies vary, so check the source's terms before you buy.

Why does my tracker show more conversions than the network?

Typically because of duplicate postbacks, test conversions, or reversals that the network has removed but not reported to your tracker. Use transaction IDs to deduplicate and reconcile against approved figures.

Next steps

Build a baseline for your top three campaigns this week. If you buy traffic, our guide to buying adult traffic in Europe covers source quality in more depth, and you can browse more tracking and analytics guides.