Why BotRefund Might Reject Your Submitted Evidence — and How to Fix It

BotRefund doesn't reject evidence out of spite. It rejects evidence when the submission doesn't match its own independent record of the conversion. In practice, that means three things: your evidence is incomplete, it's been tampered with, or it arrives outside the allowed review window. Here's what to check before you resubmit.

BotRefund scores every affiliate conversion as Approve, Review, Hold, or Reject. A Reject score means "clear evidence of manipulation," according to its own definition. When you submit evidence that disagrees with the behavioral signals and attribution path BotRefund recorded, you'll get a rejection — and usually a clear reason why.

The three main reasons your evidence gets rejected

Rejections aren't random. They fall into three categories you can diagnose yourself.

• Incomplete evidence: Your submission lacks key identifiers — UTM parameters, click ID, affiliate ID, or a payout CSV — so BotRefund can't match your claim to its recorded conversion path.
• Tampered evidence: Your logs or screenshots show signs of editing or don't line up with the conversion path BotRefund reconstructed. Even accidental mismatches (e.g., a wrong timestamp) can trigger a rejection.
• Timing discrepancy: The conversion date or click-to-conversion interval falls outside the expected window. BotRefund analyzes click-to-conversion timing, so evidence that doesn't match the recorded timing will be flagged.

These aren't the only possible causes, but they cover the vast majority of rejections. Let's look at each one in detail.

How BotRefund evaluates your evidence

BotRefund audits every conversion using behavioral signals, attribution path analysis, and click-to-conversion timing. It reconstructs which affiliate ID and click ID drove each conversion directly from your traffic's UTM data. This means your evidence is compared against an independent, machine-built record of what actually happened.

The system uses 106 independent checks to build a reliable picture of whether a visit is human or automated. A single anomaly is not a bot verdict — privacy tools, corporate networks, and unusual devices can produce unexpected behavior for genuine people. BotRefund keeps each signal as evidence, not a verdict, and cross-checks it against browser, network, device, and behavior data. So when you submit evidence, it's weighed against this corroborated picture.

If your evidence contradicts that picture, you'll see a Reject score. If it doesn't fully agree but isn't clearly fraudulent, you'll get Review or Hold. The same scoring applies to the evidence you submit — it's held to the same standard as the original conversion data.

Diagnose your rejection in three steps

Before you resubmit, run through this sequence:

1. Check identifiers. Does your evidence include the exact affiliate ID, click ID, and UTM parameters? Without these, BotRefund can't match your claim to its attribution path. Missing any one of these is an automatic rejection risk.
2. Check consistency. Compare your evidence against the BotRefund report. Do the timestamps, device, and referral pattern match? If your screenshot shows a click at 3:00 PM but the report says 3:05 PM, that's a mismatch that can trigger a reject.
3. Check the time window. Is the conversion date within the allowed review period? BotRefund uses click-to-conversion timing, so evidence for a conversion that happened too long after the original click — or one that's older than the platform's retention policy — will be refused.

If all three check out, your evidence should pass. If any one fails, fix it before resubmitting.

Incomplete evidence: missing identifiers

The most common rejection cause is missing data. BotRefund reconstructs the conversion path from UTM and click IDs. If your evidence doesn't include these, there's nothing to match.

For example, if you submit a screenshot of a sale confirmation page but omit the click ID that led to it, BotRefund can't verify that this sale came from your affiliate link. The same applies if you forget to attach the payout CSV or fail to connect your affiliate platform.

What counts as complete evidence? A full audit trail: the click ID, UTM parameters, timestamp, and the conversion event itself. If you're using BotRefund's dashboard, the report already contains these. When you submit your own logs, make sure they include every field BotRefund expects.

Tip: Always export your payout CSV from your affiliate platform and include it with any dispute. Don't crop or edit the file — that's tampering, even if you're only removing irrelevant rows.

Tampered evidence: when the story doesn't match

BotRefund cross-checks your evidence against its own independent record. If your logs show a different path, a different device, or a different time than what BotRefund captured, it will flag the discrepancy.

This isn't just about deliberate fraud. Accidental edits — like cropping a screenshot to focus on the amount, or adjusting a timestamp in a spreadsheet — can make your evidence look inconsistent. BotRefund's checks are designed to catch these mismatches.

What does tampering look like? A log that doesn't include the full click path, a screenshot with a different browser tab visible, or a CSV that's been manually altered. Even if the core facts are true, the submission may be rejected because it doesn't match the verified record.

The safest approach is to submit evidence exactly as it came from the source — no edits, no cropping, no reformatting. If you need to redact personal data, do it in a way that doesn't alter the conversion details.

Timing discrepancies: why the window matters

BotRefund analyzes click-to-conversion timing as part of its audit. That means it knows how long a legitimate conversion should take after a click. If your evidence shows a conversion that happened too quickly (e.g., within 1 millisecond) or too long after the click, it won't match the pattern.

Additionally, most affiliate programs have a cookie window — typically 30, 60, or 90 days. If you submit evidence for a conversion that falls outside that window, BotRefund will reject it because the attribution isn't valid.

There's also the platform's own review period. BotRefund needs to process claims within a reasonable time. If you submit evidence months after the payout cycle, it may be outside the allowed window.

What counts as a valid timing? A natural click-to-conversion interval — minutes to days, not milliseconds or years. If your evidence shows an impossible speed or an old date, that's a red flag.

What happens after a rejection and how to resubmit

When BotRefund rejects your evidence, you'll see the reason in the dashboard. The rejection is not permanent. You can correct the issue and resubmit.

Start by reviewing the diagnostic steps above. Identify which category your rejection falls into: incomplete, tampered, or timing. Fix the specific problem — add the missing identifier, re-export a clean CSV, or confirm the conversion date is within the window.

If you believe the rejection is a false negative — BotRefund made a mistake — you can request a manual review. But first, double-check that your evidence is complete and consistent. In most cases, the issue is on your side.

Resubmit through the same channel you used originally. Make sure the new evidence addresses every point in the rejection reason. If the rejection mentions a missing click ID, include it. If it mentions a timing mismatch, verify the timestamp.

Key facts about BotRefund evidence

The table above summarizes the key standards your evidence must meet.

Frequently asked questions

How long do I have to submit evidence?

BotRefund doesn't publish a fixed deadline, but its timing analysis means you should submit evidence within the standard conversion window (typically 30–90 days after the click) and before the payout cycle ends. If you wait months, your claim will likely be rejected as stale.

Can I resubmit after a rejection?

Yes. A rejection isn't final. Fix the specific issue — missing ID, timing mismatch, or tampering — and resubmit. The dashboard shows the reason, so you know what to correct.

Does BotRefund ever reject evidence incorrectly?

It can, because single anomalies aren't enough for a decision. BotRefund cross-checks across 106 signals, so a false rejection is unlikely when your evidence is complete. If you believe it's a mistake, request a manual review with supporting documentation.

What evidence does BotRefund accept?

BotRefund accepts evidence that includes the full attribution path: click ID, UTM parameters, timestamp, and conversion event. A clean payout CSV or connected affiliate platform provides the most reliable proof.

What happens if my evidence is rejected?

The commission is scored as Reject, meaning it should be declined. You'll see the reason in the evidence dashboard. Correct the evidence and resubmit before the next payout cycle.

Does BotRefund require me to submit evidence at all?

No. If your affiliate platform is connected or you upload a payout CSV, BotRefund can generate its own evidence. Manual submissions are only needed when you're disputing a specific conversion or providing additional context.