Why Your Affiliate Payouts Never Match What You Tracked
You counted 400 clicks. The merchant's dashboard says 260. Neither number is necessarily wrong, but the gap is worth understanding.
Almost every creator running affiliate links eventually notices the same thing: their click count doesn't match what the merchant's dashboard reports. It's easy to think "I'm being shortchanged" or "my tracking must be wrong". A more useful way to look at it is that these are two measurements of different things. The gap is information, not automatically a dispute.
Three numbers that are not the same number
A trustworthy affiliate reconciliation keeps three figures distinct instead of blending them into one:
- What you measured yourself: clicks on your links, counted before anyone reaches the merchant.
- What the merchant reported: their clicks, conversions, and the amount they say they owe. If they haven't reported a number, the field stays blank instead of showing 0.
- What actually got paid: the amount that landed in your account. Money either arrived or it didn't.
Collapsing these into one number is exactly how a real discrepancy gets missed, or how ordinary tracking noise gets mistaken for a merchant shortchanging you.
Why your click count usually runs ahead
It's normal for your measured clicks to exceed what a merchant reports for several ordinary reasons. Ad blockers can strip a merchant's tracking pixel before it fires, a tag can load late and miss a fast bounce, and reporting windows may not line up exactly. Their "this week" and your "this week" aren't always the same seven days. None of this means anyone's lying. Click tracking can lose some real clicks between your link and the merchant's dashboard.
When the gap is actually worth a conversation
Not every gap deserves an email to the merchant. Different attribution windows, blocked tracking, and time zones can explain small differences. When the gap is large enough to affect your expected payout, compare the same dates and definitions first, then ask: "I'm seeing more clicks on my end than in your report for this period. Could we check how each side counts them?" Frame it as a reconciliation question, not an accusation.
Making reconciliation less manual
Logging a payout period by hand means entering your clicks, the merchant's reported numbers, and what you received. If a merchant sends a CSV statement, importing it instead of retyping the rows can prevent transcription errors. Preview the parsed rows and detected columns before saving them. A misread column could corrupt your ledger, which is worse than entering the data manually.
Earnings-per-click: only when it's honest
A metric like earnings per click or conversion rate is meaningful only when both sides of the calculation have real numbers. Treating an unreported value as 0 creates a figure that looks precise but means nothing. It is better to show no value than a false number, even if that makes the dashboard feel less complete.
What to actually do with this
- Log your measured number and the merchant's reported number separately for each period. Don't merge them in your head.
- Treat a discrepancy flag as a prompt to ask, not a verdict.
- Record what was actually paid, even when the other numbers don't reconcile. That is the number that pays your bills.
knit.bio's Money Suite compares your measured clicks with each merchant's report and flags significant gaps automatically. This feature is available on Pro and Studio. CSV statement import is available on Studio. See how it works, or start free.