Small gaps between your tracker and the network are normal. Larger ones usually mean a postback, pixel or attribution setting needs attention.
Main points
- A 1 to 5 percent difference between your tracker and the network is typical and comes from timing, rounding and deduplication.
- Pixel tracking loses conversions to ad blockers and slow-loading pages, while server-to-server postbacks record events regardless of browser settings.
- Timezones, attribution windows and postback status settings change when and whether a conversion reaches your tracker.
- Filtering for off-target clicks, duplicate leads and canceled orders makes the network’s count smaller than yours.
- Reconcile by matching date ranges, timezones, click IDs and postback logs before treating a gap as lost revenue.
Your tracker reports 212 conversions this month and the network’s dashboard shows 198. Before assuming either system is broken, know that some difference between the two reports is normal, because each platform counts conversions under its own rules. The real task is telling ordinary counting variance apart from a setup problem that costs you money.
Is a Mismatch Between My Tracker and the Network Normal?
Yes. Different tracking and analytics platforms report data in different ways depending on how they are configured, so some variance should be expected even when both systems work correctly. Each side keeps its own ledger and applies its own attribution logic, so the same event can be recorded differently on each side. One conversion appearing in several reports at once is normal operation, not fraud.
Do Time Zones Change When a Conversion Gets Counted?
They can. Most systems stamp events in the timezone set in the reporting panel, and a conversion recorded at 11:30 PM in one timezone can land on the next calendar day once converted to UTC. Comparing a Monday-to-Sunday range in your timezone against the same dates on the network’s side puts different events at the edges of the range. Switch one report to match the other’s timezone before comparing anything.
Setup timing matters too. If your postback link was configured partway through the month, conversions recorded before that point were never sent to your tracker. Networks can often edit and re-send those older conversions, so ask your manager.
How Do Pixel and Postback Tracking Methods Cause Gaps?
Browser-based pixels are a frequent source of missing conversions. A pixel fires from the user’s browser when a confirmation page loads, and it fails in predictable ways. Ad blockers block tracking scripts by default, and their adoption exceeded 40 percent on desktop in 2025. On slow mobile connections, JavaScript-heavy confirmation pages can take three to five seconds to load, and buyers close the tab before the script runs.
Postback tracking sends conversion data directly from one server to another, so browser settings cannot suppress the event. Advertisers who move from pixel-only setups to server-to-server tracking have reported 15 to 25 percent more recorded conversions. If your tracker relies on a pixel while the network tracks server-side, expect the network’s count to run higher. Our guide to Postback URLs Explained: Server-to-Server Conversion Tracking covers how the click ID and postback handoff work.
Why Does the Network Deduplicate or Cap Conversions Differently?
Because each side applies its own rules to repeated and delayed events. If the same click ID fires twice, your tracker may record one conversion while the advertiser counts both. Attribution windows differ too: one major social platform’s default credits a purchase when an ad click happened up to a week before checkout or when an ad was viewed within the previous day, while a major search platform defaults to a 30-day click window, and neither deduplicates against the other.
Status settings create gaps as well. Many postback configurations fire only on approved conversions, so pending or declined conversions sit in the network’s report and never reach your tracker. Many conversions also start as pending while the advertiser validates the action, checking lead quality, payment status, geography and duplicates. Our article on Conversion Windows and Attribution in Affiliate Tracking explains how window length decides who gets credit.
What Does Fraud Filtering Do to Each Side’s Numbers?
Filtering usually makes the network’s number smaller than yours. Clicks outside the offer’s targeting rules, such as the wrong geography, device or operating system, can be rejected by the network while your tracker counts every outbound click. Leads with disconnected phone numbers, fake emails or duplicate submissions can track correctly on your end and still fail the advertiser’s validation, and canceled or unpaid orders are a common source of reversed conversions in e-commerce and subscription campaigns.
The reverse, a network reporting far more than your tracker, usually points at a broken postback on your side.
How Large a Discrepancy Should Worry Me?
A gap of 1 to 5 percent is typical and comes from timing, rounding and deduplication. Revenue totals can differ slightly from currency exchange rounding alone. Approval cycles also shift conversions between reporting periods: a three-day approval cycle means conversions appear three days after the action, and both reports look wrong until you account for the delay.
Wider gaps deserve investigation. Pixel-based mobile tracking has been reported to attribute only 60 to 70 percent of conversions accurately, against near-complete accuracy from server-side tracking, so a large gap can mean the tracking method itself is the problem rather than fraud.
How Do I Reconcile the Two Reports Step by Step?
Work through the comparison in this order:
- Set both reports to the same date range and timezone.
- Confirm the attribution window and which conversion statuses trigger a postback on each side.
- Match individual conversions by click ID or by the sub IDs in your links, since these let you trace one user’s path from click to conversion. Our guide to Sub IDs: Tracking Which Traffic Actually Converts covers how to set them up.
- Check postback logs for delivery errors. Any HTTP code other than 200 means the conversion was not delivered, and a 404 usually means the click ID was not found.
- Ask the network to share their postback logs so you can verify what was sent.
- Compare totals only after accounting for the approval cycle.
Pro tip
Choose one source as your payout record, normally the network’s approved conversions, and use your tracker for optimization decisions. The two ledgers answer different questions, so adding them together and expecting one total is where most confusion starts.
Once you know which gaps are routine, the ones worth fixing usually come down to tracking setup or traffic quality. Our article on spotting fraud and invalid traffic in CPA campaigns lists the traffic warning signs to check before you scale a campaign.
Frequently asked
How much difference between my tracker and the network is normal?
A gap of 1 to 5 percent is typical, caused by timing, rounding and deduplication. Wider gaps usually point to a tracking setup problem worth investigating.
Why does the network show fewer conversions than my tracker?
Networks and advertisers filter out clicks that miss targeting rules and reject leads with fake details, duplicates or canceled orders. Those events stay in your tracker but never get approved.
Why does the network show more conversions than my tracker?
Usually a broken postback, a pixel that fails to fire, or a status setting that only sends approved conversions. Check your postback logs for HTTP codes other than 200.
Which numbers should I use for payout decisions?
Base payouts on the network’s approved conversions, since that is what you actually get paid on. Use your tracker for optimization decisions instead.
This article is general information for marketers, not legal advice. Advertising, privacy and consumer protection rules vary by country and change over time, so check the current rules and your network’s terms, and get legal advice where needed before running campaigns.
