Seatext library / BotRefund evidence
How to Implement BotRefund's 106 Checks on Your Website
Implement BotRefund's 106 checks by adding a JavaScript snippet to your website, configuring your dashboard, and testing with live traffic. Setup takes about a minute, needs no credit card, and the checks feed an...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
To implement BotRefund's 106 checks on your website, you add a JavaScript snippet, configure your dashboard, and then test with real traffic. The full installation typically takes about one minute, and no credit card is required. Once live, the 106 independent checks work together to classify each visit as human or automated, using evidence from browser, network, device, and behavior signals.
What Are BotRefund's 106 Checks?
BotRefund uses 106 independent checks to build a reliable picture of whether a visit is human or automated. Each check looks for a specific mismatch that a real browsing session normally doesn't create. For example, the CPU Concurrency Lie check looks for a device claiming one set of hardware while its graphics or fonts tell another story. The window.open Tamper check looks for scripts that send clicks and scrolls without the varied timing of a human user. The Impossible Tab Speed check tracks interactions that happen faster than a person could realistically perform.
These checks also include behavioral signals like ghost click detection, honeypot trap interactions, robotic linear mouse movements, absence of humanlike tremor, superhuman input speed, grid-aligned movement patterns, absence of clicks or scrolling, and unnatural session durations.
The key point is that a single anomaly is not a bot verdict. Privacy tools, travel, 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 independent browser, network, device, and behavior data. The complete pattern is weighed by an AI model, which identifies a visit as bot or human with 99% accuracy.
Prerequisites Before You Start
Before you install the snippet, make sure you have the following ready:
- Admin access to your website (to edit the header or footer).
- A BotRefund account (free to create).
- Your monthly ad spend range for Google Ads or Meta (to configure refund preferences).
- A test browser or device you can use to verify the installation.
- Access to your website's tag manager if you use one.
Step-by-Step Implementation
Step 1: Create Your BotRefund Account
Go to botrefund.com and click Create account. You can start with a free bot audit—no credit card required. During signup, you'll be asked to select your ad spend range, which helps BotRefund tailor your refund and protection settings.
Step 2: Get Your JavaScript Snippet
After logging in, navigate to the dashboard and locate the installation code. BotRefund provides a small JavaScript snippet that contains the core tracking and detection logic. Copy this snippet exactly as shown.
Step 3: Add the Snippet to Your Website
Paste the snippet into the <head> section of your HTML, ideally on every page you want to protect. If you use a tag manager like Google Tag Manager, you can add it there instead. For CMS platforms like WordPress, use a plugin that inserts custom code in the header. For other platforms, edit the theme or layout template directly.
Make sure the snippet loads on all pages, especially landing pages where ad traffic arrives. If you only place it on a few pages, the checks won't see the full session.
Step 4: Configure Dashboard Settings
In your BotRefund dashboard, confirm your ad spend range and set any preferences for refunds. You can adjust these later, but the initial setup uses them to map out a recovery plan. The dashboard also shows you which signals are being recorded for your site.
Step 5: Test with Real Traffic
Once the snippet is live, test it by visiting your website from a regular browser. Open a private window to simulate a new session. Then log into your BotRefund dashboard and check that your visit appears as a human session. You should see the checks that were triggered (or not) for that session.
For a more thorough test, you can use a headless browser (like Puppeteer or Selenium) to load your site. This may trigger bot signals. If the dashboard flags that session, the checks are working as intended.
How to Verify the Checks Are Running
After installation, verify that the snippet is active in a few ways:
- Open your browser's developer tools (F12) and go to the Network tab. Look for requests to BotRefund's domain.
- Check the console for any errors from the snippet.
- In your BotRefund dashboard, view the recent sessions and confirm that new sessions are being recorded.
You should see a mix of signals per session, but not every signal will fire on every visit. The AI model weighs the complete pattern, so uniform sessions are actually more suspicious than varied ones.
Key Facts About BotRefund's 106 Checks
| Feature | Detail |
|---|---|
| Number of independent checks | 106 |
| Accuracy | 99% (based on AI prediction using the full signal pattern) |
| Setup time | About 1 minute |
| Credit card required? | No, the free audit has no credit card requirement |
| Refund eligibility | Google Ads spend dating back to 2017; Meta disputes also supported |
| Bot click share | Bot clicks can steal up to 20% of Google and Meta ad budget |
Readiness Checklist
Before you install, make sure you can answer yes to these items:
- I have admin access to my website's HTML or tag manager.
- I have a BotRefund account (or I'm ready to create one).
- I know my approximate monthly ad spend for Google or Meta.
- I have a test browser to verify the installation.
- I understand that a single anomaly is not a bot verdict.
Limitations and What the Checks Don't Do
BotRefund's 106 checks are powerful but not infallible. A single anomaly—like a corporate proxy or a privacy extension—can trigger a signal for a real user. That's why the AI model cross-checks all signals before making a verdict. If you see false positives, you can review the evidence in the dashboard and adjust your settings.
The checks are not a replacement for other website security like SSL, firewalls, or rate limiting. They focus on detecting automated visits and providing audit trails, not on blocking traffic in real time. You'll use the evidence to request refunds from Google and Meta or to suppress conversion events.
Also, if your site is behind a very heavy CDN or a service that modifies headers, some device or browser signals may be altered. In such cases, the checks still work, but you should validate with a test session.
Common Mistakes and How to Avoid Them
- Placing the snippet only on the home page. Bots often land on deep pages. Install it site-wide.
- Skipping the dashboard configuration. Without your ad spend range, refund recommendations aren't tailored.
- Ignoring early false positives. Use the dashboard to see which signals were triggered; don't block a legitimate user based on one signal.
- Not re-testing after site updates. If you change your theme or move to a new CMS, verify the snippet still loads.
Frequently Asked Questions
How many independent checks does BotRefund use?
BotRefund uses 106 independent checks, each looking for a specific discrepancy between what a real user and an automated browser would do.
Do I need a credit card to start?
No. The free bot audit and initial setup require no credit card.
How long does installation take?
Most sites are installed in about one minute, assuming you have admin access to the header or a tag manager.
Can I get refunds from Google and Meta?
Yes. BotRefund helps you recover bot-click refunds from Google Ads spend dating back to 2017, and it also supports Meta billing disputes.
What if a legitimate user triggers a bot signal?
A single anomaly is not a verdict. The AI model cross-checks all signals, so one unusual behavior won't classify a real person as a bot unless the broader pattern supports it.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.