Documentation to Request for Verifying Commission Calculations: A Readiness Checklist

To verify commission calculations, ask for a CSV export of all sales, API logs with click IDs and UTM parameters, behavioral evidence reports, and signed affidavits when available. These documents let you cross-check each conversion's attribution path and timing before you approve payment. Start with the data you already have—your payout CSV—then add layer by layer.

What counts as verification-ready documentation?

Not every file your affiliate platform gives you is useful. The documents that actually help you verify commissions are the ones that show the complete story of a conversion: where the click came from, what the user did after the click, and whether the commission claim matches the behavior you'd expect from a real customer.

Verification-ready documentation has three qualities:

• It includes the click ID and UTM parameters. These tie a conversion to a specific affiliate and campaign.
• It captures the full attribution path. This shows whether the conversion was actually driven by the affiliate or if it was hijacked in the final seconds.
• It includes behavioral evidence. Session recordings, mouse movement data, and timing signals help you spot bots or manipulated sessions.

The readiness checklist: 5 documents to request

Request these five items to build a complete verification file. Keep them organized by payout cycle so you can compare them easily.

• CSV export of all sales — a raw list of every transaction, with date, amount, affiliate ID, and click ID.
• API logs of conversion events — server-side logs that record the click ID, UTM parameters, and timestamp for each conversion.
• Behavioral evidence reports — session-level data showing mouse movement, scroll depth, time on page, and other interaction signals.
• Attribution path analysis — a document that reconstructs the sequence of touches leading to the conversion, including any cookie drops or redirects.
• Signed affidavits (when available) — a written statement from the affiliate or sales team attesting that the conversion was genuinely driven by their efforts. These are not always provided, but you can request them if your contract allows.

Why each document matters

The CSV export is your baseline. It tells you what you're paying for. But a CSV alone can be gamed—cookies can be stuffed, and last-click hijacking can hide the real source.

API logs give you the raw event data to cross-check the CSV. Look for mismatches in click IDs or timestamps. If the click ID in the CSV doesn't match the one in the API log, that's a red flag.

Behavioral evidence reports are the most powerful. They show whether a user acted like a real person. A conversion that happens in 0.2 seconds with no scrolling is a strong sign of bot activity.

Attribution path analysis ties everything together. It shows the full chain from the affiliate's link to the conversion, including any third-party redirects or cookie injections.

Signed affidavits are a legal layer. They're not used by every program, but they can be useful for high-value commissions where you need written confirmation.

How to use the documents together

Don't evaluate each document in isolation. Use them as a cross-checking system.

1. Download your payout CSV and mark every commission that's due this cycle.
2. Pull API logs for each click ID and timestamp in the CSV. Verify they match.
3. Review behavioral evidence for any conversion that looks unusual—fast timing, no scroll, or repeated patterns.
4. Run an attribution path analysis to see if any redirects or cookie drops occurred in the final seconds before conversion.
5. Request signed affidavits for high-value or suspicious commissions.
6. Approve, hold, or reject each commission based on the evidence stack you've built.

This process gives you a clear decision rule: approve when all documents align, hold when there's a mismatch, and reject when you find clear evidence of manipulation.

Common mistakes to avoid when requesting documentation

• Only asking for the CSV. The CSV is a summary, not proof. You need the underlying logs and behavior data.
• Ignoring API logs. Many platforms hide these, but you have a right to them if your contract mentions performance data.
• Expecting affidavits from every affiliate. These are rare. Use them as a bonus, not a requirement.
• Not preserving data before making changes. If you change your tracking setup before you pull logs, you lose the ability to verify past commissions. Save what you have first.

Limitations: when documentation won't be enough

Some situations will defeat even a good documentation set. For example, if the affiliate uses a browser extension that injects cookies at the moment of purchase, the behavior may look normal because the user was genuinely interested. The attribution path will show a cookie drop, but without deep analysis, you might miss it.

Also, if you don't have a tracking script installed on your site, you won't have behavioral evidence at all. In that case, you'll need to rely on server-side logs and manual checks.

Lastly, some affiliates work in networks that bypass your tracking entirely. If you suspect fraud but can't document it, consider changing your tracking infrastructure before you fight the claim.

Key facts about commission verification

Terminology

CSV export — a comma-separated file with rows of sales data.

API log — a server-side record of events like clicks and conversions.

Attribution path — the sequence of referrals that led to a conversion.

Behavioral evidence — data about how a user interacts with your site, such as mouse movement and scrolling.

Affidavit — a signed, notarized statement from an affiliate confirming that they drove the sale.

Frequently asked questions

What if my affiliate platform won't give me API logs?

Check your contract. Most platforms provide at least basic conversion data. If they refuse, you can request a third-party audit or switch to a platform that gives you raw access.

How much does it cost to get behavioral evidence?

You'll need a tracking solution that records sessions. Prices vary. Some tools are free for basic setups, but professional solutions like BotRefund offer a free audit to get started.

Can I verify commissions without a tracking script?

Yes, but with less certainty. You can use server-side logs and manual checks, but you'll miss client-side manipulation like cookie stuffing. Adding a tracking script is the most reliable way.

What should I do if two documents disagree?

Hold that commission. When you see a mismatch between the CSV and the API log, or between the behavior data and the attribution path, don't pay until you resolve it.

Are signed affidavits legally binding?

They can be, but enforcement depends on your jurisdiction and contract. Use them as supporting evidence, not as your primary proof.