How to View the Browser Signals BotRefund Is Checking

To see what browser signals BotRefund is checking, log in to your BotRefund dashboard and open the detection logs. There you'll find each flagged signal, such as CPU Concurrency Lie or window.open Tamper, along with the evidence behind it. If you haven't set up BotRefund yet, run the free bot audit to see which signals are triggered on your site.

Step 1: Log in to Your BotRefund Dashboard

If you already have a BotRefund account, sign in at botrefund.com. The dashboard is where all your detection data lives.

If you haven't added BotRefund yet, you can start with a free bot audit. The homepage says you can add it to your website in about one minute and turn on the free AI audit. No credit card is required for the audit.

Once you log in, you'll see an overview of your site's traffic. The dashboard organizes signals by category, such as Click behavior, Trap behavior, Pointer behavior, Motion behavior, Speed behavior, Path behavior, Engagement behavior, and Session behavior. These categories come from the homepage and help you spot patterns at a glance.

Step 2: Navigate to the Detection Logs or Signals Section

Look for a menu item labeled "Detection," "Signals," or "Logs." This section lists every check BotRefund ran for each visit. You'll see the 106 independent checks that BotRefund uses, such as CPU Concurrency Lie and window.open Tamper. The "How we detect bots" page explains that these are independent checks used to build a reliable picture of whether a visit is human or automated.

The logs are presented as a table. Each row shows a visit with columns for date, time, IP address, browser, and the signals that were triggered. You can filter by date range or by signal name. For example, you can set a filter to see only visits that triggered CPU Concurrency Lie. This helps you isolate specific issues.

To understand the full list of checks, visit the "How we detect bots" page. It links to detailed descriptions for each of the 106 checks. You can browse them one by one to learn exactly what each one evaluates.

Step 3: Review Flagged Signals

In the log, each visit will show which signals were flagged. For example, you might see "CPU Concurrency Lie" or "window.open Tamper" marked as a potential bot indicator. Click on a signal to see the specific evidence. The dashboard shows what a real browser usually reveals versus what an automated browser often reveals.

For the CPU Concurrency Lie check, the evidence panel might show that the browser reported a certain CPU model, but the graphics, fonts, audio, or processor behavior did not match. The normal user side shows a real browser reports hardware details that naturally fit together for that device. The bot side shows a mismatch that a real browsing session does not normally create.

For window.open Tamper, the evidence might show that clicks and scrolls happened without natural timing or hesitation. A real visitor produces imperfect, varied behavior with pauses and hesitation. Scripts send clicks and scrolls but cannot match the human timing.

Remember, a single anomaly is not a bot verdict. BotRefund cross-checks signals against independent browser, network, device, and behavior data before deciding.

Step 4: Understand What Each Signal Means

Each signal has its own page on the BotRefund site. For example, the CPU Concurrency Lie page explains that it looks for a mismatch between reported hardware and graphics, fonts, audio, or processor behavior. The window.open Tamper page explains that it checks for scripted clicks and scrolls that lack humanlike timing and hesitation.

You can browse all 106 checks from the "How we detect bots" page. This helps you know exactly what BotRefund is evaluating for your traffic. The homepage also lists several signals with brief explanations. Ghost click detection catches click activity without natural human intent. Trap behavior watches for bots that respond to hidden elements. Robotic linear mouse movements flag unnaturally straight pointer paths. Absence of humanlike mouse tremor looks for the tiny imperfections of human movement. Superhuman input speed (<1ms) identifies faster-than-human interactions. Grid-aligned movement patterns detect snapping to precise lines. Absence of clicks or scrolling highlights static sessions. Unnatural session durations catch visit lengths too short, too long, or too uniform.

Step 5: Check the Signal Evidence and Context

In the dashboard, you can see the raw data behind each flag. Look for the "evidence" or "context" panel. It shows what signal was triggered, what the expected human behavior would be, and what the visit actually did. This is the same evidence BotRefund uses to build a case for refunds from Google and Meta.

You can also export your report. The homepage says you can turn on the free AI audit, export your report, and send it to your Google or Meta representatives. For Google disputes, the blog on Google Ads refund requests explains that you need to collect GCLID logs to prove invalid clicks. These logs are part of the exported report. For Meta, similar evidence from the detection logs is used.

When you export, you get a file that lists each flagged signal and the supporting evidence. This makes it easy to attach to a billing dispute.

Step 6: Verify with a Free Bot Audit

If you're not a customer yet, run the free bot audit. It will analyze your site traffic and show you which signals are being triggered. The homepage says you can start a free audit without a credit card.

This verification step confirms that you're seeing the correct data and gives you a clear picture of your bot traffic. The audit is a one-time snapshot, not a live view of every check.

Understanding the Signal Catalog

BotRefund uses 106 independent checks to evaluate a visit. Here are the signals described in BotRefund's public materials. The full catalog includes many more, but these are the ones shown on the site.

These signals cover click behavior, pointer movement, speed, path, engagement, and session patterns. Each adds one objective fact about the visit. The AI model weighs the complete pattern.

Limitations and When This Doesn't Apply

Seeing a single flag doesn't mean a visitor is a bot. Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior for genuine people. For example, a VPN can make a user appear in a different location. A corporate proxy can change IP addresses mid-session. An unusual browser, like a text-based one or an old version, may not generate the same signals as mainstream browsers.

BotRefund handles these cases by cross-checking signals. The principle is that a single anomaly is not a bot verdict. Each signal adds evidence, and the AI evaluates the full picture across browser, network, device, and behavior data. This is why BotRefund claims 99% accuracy based on corroboration, not one browser tell.

If you don't have a BotRefund account, you won't see the logs. You need to install the script first. The free audit is a one-time snapshot, not a live view of every check. It shows which signals are triggered at that moment, but it doesn't give you the historical logs.

The signal list is updated as new bot techniques appear. The ad fraud trends blog discusses how fraudsters use AI to simulate human behavior, so detection must evolve. Check the "How we detect bots" page for the latest list.

Frequently Asked Questions

What is the CPU Concurrency Lie check?

It's one of BotRefund's 106 signals that looks for a mismatch between what a browser claims about its hardware and what it actually reports in graphics, fonts, audio, or processor behavior. A real device shows consistent data.

How many signals does BotRefund check?

BotRefund uses 106 independent checks to build a reliable picture of whether a visit is human or automated.

Can I see all the signals without paying?

You can run a free bot audit to see which signals are triggered on your site. The audit is a starting point; the full dashboard with historical logs is part of the paid service.

Will the dashboard show me why a visitor was flagged?

Yes, each flagged signal includes evidence showing what the real browser would do versus what the automated browser did. You can see the specific mismatch that triggered the check.

Do privacy tools like VPNs trigger signals?

They can produce unexpected behavior, but BotRefund cross-checks signals and does not treat a single anomaly as a bot verdict. The AI evaluates the complete pattern.

How do I use this information to get a refund?

You can export your detection report from the dashboard and send it to Google or Meta as proof of invalid clicks. The homepage mentions that BotRefund negotiates with these platforms.

How often are signals updated?

BotRefund updates its signal catalog as new bot techniques emerge. The ad fraud trends blog describes how fraudsters are using AI to mimic human behavior, so the detection system must adapt. Check the "How we detect bots" page periodically for the latest checks.

Can I see signals in real time?

Yes. Once BotRefund is installed on your website, the dashboard shows detection logs in near real time as visits occur. The free audit is a one-time snapshot, but the full dashboard provides ongoing, live signal data.

Next Step: See Your Own Signals

To see exactly what BotRefund checks on your site, start a free bot audit. You'll get a live report of flagged signals and a clear path to protect your ad spend.

Start your free bot audit to see your site’s flagged signals.