On-Site Bot Evidence Generation: What It Means for Refund Claims

On-site bot evidence generation means your website automatically creates a verifiable record that a specific click or interaction was performed by an automated script, not a human shopper. This record is built from behavioral signals captured on your own site—like mouse movement, click timing, and session patterns—and stored as proof you can submit to ad platforms when requesting a refund for invalid clicks.

In practice, it turns your website into a witness. Instead of relying only on Google or Meta's internal filters, you collect your own evidence that a click was fraudulent. That evidence becomes the foundation of a refund dispute, giving you something concrete to show the Click Quality team when you ask for your money back.

What on-site bot evidence actually is

On-site bot evidence is not a single data point. It is a collection of behavioral and technical signals that, when combined, paint a clear picture of whether a visit was human or automated. These signals are captured in real time as a user interacts with your page.

Common signals include:

• Ghost click detection – catches clicks that happen without the natural sequence of human intent.
• Honeypot trap interactions – watches for bots that respond to hidden or intentionally deceptive page elements.
• Robotic linear mouse movements – flags unnaturally straight pointer paths that rarely appear in real user sessions.
• Absence of humanlike mouse tremor – looks for the tiny imperfections and jitter typical of human movement.
• Superhuman input speed – identifies interactions that happen faster than a person could realistically perform.
• Grid-aligned movement patterns – detects movement that snaps to precise lines or blocks instead of natural curves.
• Absence of clicks or scrolling – highlights sessions that stay too static to match a real browsing journey.
• Unnatural session durations – catches visit lengths that are too short, too long, or too uniform to be human.

These are just a few examples. A robust system like BotRefund uses 106 independent checks to build a reliable picture of whether a visit is human or automated.

How on-site evidence is generated

The process happens in the background, usually through a small script added to your website. When a visitor lands on your page, the script starts observing their behavior. It tracks mouse movements, click timing, scroll patterns, and even technical details like browser type and device fingerprint.

Each signal is recorded as an objective fact. For example, a window.open tamper check looks for a mismatch that a real browsing session does not normally create. Scripts can send clicks and scrolls, but they struggle to reproduce the varied timing, movement, and hesitation of real people.

Critically, a single anomaly is not a bot verdict. Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior for genuine people. So the evidence is cross-checked against independent browser, network, device, and behavior data. Only when multiple signals agree does the system classify the visit as a bot.

This corroboration is what makes the evidence strong. As BotRefund explains, accuracy comes from corroboration, not one browser tell. The system sends all signals into a prediction AI that evaluates the complete picture, achieving 99% accuracy in identifying bot versus human visits.

Why ad platforms miss bots (and why you need your own evidence)

Google and Meta have their own invalid traffic filters, but they are not perfect. Modern fraud networks use AI to simulate human mouse curvature, click intervals, and page scrolling. They route clicks through residential proxy networks made of hijacked smart devices, presenting legitimate IP addresses that bypass location-based exclusions.

As a result, thousands of dollars in wasted ad spend slip through the platforms' nets. Google's automated systems frequently fail to identify modern residential proxy networks and competitor click fraud. That's why you need your own on-site evidence—it gives you a second, independent layer of proof that the platform's filters missed.

When you file a refund request, you are essentially saying, "Your system didn't catch this, but my website did." The evidence you generate on-site is what makes that claim credible.

Using on-site evidence in a refund claim

To turn on-site evidence into a refund, you need to export it in a format that ad platforms accept. The typical workflow looks like this:

1. Install a detection script on your website. This usually takes about a minute and requires no credit card.
2. Let it collect data on every visit, building a log of behavioral signals and click IDs.
3. Export a detailed report that shows which clicks were flagged as bot traffic.
4. Submit the report to Google's Click Quality team or Meta's billing team as part of a formal refund request.
5. Follow up with your ad platform representative to ensure the claim is reviewed.

Google officially categorizes invalid clicks into segments they agree to credit back if you provide sufficient proof. These include competitor click activity, publisher click fraud, and bot traffic & web scrapers. Your on-site evidence directly supports these categories.

BotRefund's approach is to prove bot clicks, negotiate with Google and Meta, and get your money back. They even recover refunds from Google Ads spend dating back to 2017.

Limitations and when on-site evidence isn't enough

On-site bot evidence is powerful, but it has limits. First, it only works if you have the script installed before the fraudulent clicks happen. You can't retroactively generate evidence for past traffic.

Second, a single signal is never enough. As BotRefund notes, a single anomaly is not a bot verdict. Privacy tools, corporate networks, and unusual devices can produce false positives. That's why the evidence must be cross-checked against multiple independent signals.

Third, ad platforms may still reject your claim if the evidence isn't formatted correctly or if the platform's own analysis disagrees. You need to present the evidence in a way that aligns with their refund policies.

Finally, on-site evidence generation is not a substitute for good campaign hygiene. It helps you recover wasted spend, but it doesn't prevent bots from clicking in the first place. You still need to monitor your campaigns and adjust targeting.

Key facts about BotRefund

Terminology you'll see in refund disputes

Understanding the language helps you navigate the process. Here are key terms:

• Invalid click – a click that Google or Meta deems fraudulent or accidental, and may credit back.
• Ghost click – a click that happens without the natural sequence of human intent, often generated by scripts.
• Honeypot trap – a hidden page element that bots interact with but humans don't, revealing automation.
• Residential proxy – a network of hijacked devices that routes bot traffic through real IP addresses, making it look legitimate.
• Click ID (GCLID/FBCLID) – a unique identifier Google or Meta assigns to each click, used to track conversions and disputes.
• Pixel poisoning – a tactic where bots send fake conversion signals to damage your targeting data.

FAQ

How long does it take to generate on-site bot evidence?

Evidence is generated in real time as visitors interact with your site. The moment a bot clicks, the script records the behavioral signals. You can export a report at any time, but you need the script installed before the fraudulent activity occurs.

Can I use on-site evidence for refunds from both Google and Meta?

Yes. The same behavioral proof can be formatted for both platforms. BotRefund specifically negotiates with Google and Meta to recover refunds from billing disputes.

What if a real user triggers a false positive?

That's why corroboration matters. A single anomaly is not a bot verdict. The system cross-checks multiple signals before classifying a visit as a bot, reducing false positives.

Do I need technical skills to set up on-site evidence generation?

No. Adding a detection script to your website typically takes about a minute and requires no credit card. The tool handles the data collection and reporting for you.

How far back can I claim refunds?

BotRefund recovers bot-click refunds from Google Ads spend dating back to 2017. The exact lookback period depends on the ad platform's policies.

What makes on-site evidence stronger than just using ad platform reports?

Ad platform reports only show what the platform detected. On-site evidence captures signals the platform's filters miss, especially modern residential proxy traffic and AI-simulated behavior. It gives you independent proof to support your claim.