Seatext library / BotRefund evidence
How to Test If BotRefund Detects Your Headless Browser Setup
Start with BotRefund's test endpoint when your account has one. You can also add the BotRefund JavaScript to a test page and drive it with Playwright or Puppeteer. The dashboard then shows how BotRefund...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Start with BotRefund's test endpoint
BotRefund's test endpoint is the first option to try. It lets you check how BotRefund sees your headless browser. Check with BotRefund for the endpoint URL and the parameters it expects.
If your plan does not include the endpoint, use the snippet method. Add the BotRefund JavaScript to a test page. Run your Playwright, Puppeteer, or Selenium script against that page. Then review the session in the dashboard.
BotRefund's individual signal pages cite 106 independent checks. The homepage cites 110+ behavioral, browser, hardware, network, and attribution signals. This article uses 106 when describing the checks and 110+ when describing the full homepage signal set.
What BotRefund checks when a headless browser visits
BotRefund groups its evidence into browser, network, hardware, behavior, and attribution signals. The homepage says it combines 110+ of these signals to identify automated traffic with 99% confidence.
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. It cross-checks independent browser, network, device, and behavior data before the AI model weighs the complete pattern.
The signal pages show concrete checks. Playwright Init Scripts looks for browser API mismatches that automation tools create. Clean Context Iframe checks a browser's APIs from an isolated frame. Scrollbar Width Leak measures whether scrollbar dimensions match a real browser. These checks are part of the 106 independent checks.
The homepage also lists behavioral checks. They include ghost click detection, honeypot trap interactions, robotic linear mouse movements, absence of humanlike mouse tremor, superhuman input speed below 1ms, grid-aligned movement patterns, absence of clicks or scrolling, and unnatural session durations.
Prerequisites before you run a test
You need a BotRefund account with dashboard access. The dashboard is where you read the signal-by-signal breakdown.
You need a page where you can install the BotRefund JavaScript. The page must be reachable by BotRefund. A public staging URL works. A local-only page will not create a session in the dashboard.
You need a headless script that matches your production setup. Use the same browser, launch flags, viewport, user-agent, and stealth plugins you normally use.
Step-by-step: run a controlled detection test
- Confirm endpoint access. Ask BotRefund whether your account includes the test endpoint. If it does, use that first. If not, continue with the snippet method.
- Create a test page. Add the BotRefund JavaScript to a simple page. Load it in a normal browser. Confirm the dashboard records a clean human session.
- Run your headless script against the same URL. Keep your real configuration. Do not add test-only flags that you would not use in production.
- Wait for the session. Open the dashboard after the visit completes. Look for a new session with your test traffic.
- Inspect the signal breakdown. Look at the browser-internal checks and the behavioral checks. Note which signals pass, fail, or stay neutral.
- Read the AI verdict. The dashboard shows the final bot or human classification with a confidence score.
How to interpret the signal breakdown
Playwright Init Scripts is one of the 106 checks. The signal page says automation tools often patch or hide browser APIs, but those changes can break when the browser is checked from another angle. If this check fails, your stealth layer is probably changing something visible.
Clean Context Iframe works the same way. A normal browser runs standard browser APIs as designed. The check looks for a mismatch that a real session does not create.
Scrollbar Width Leak focuses on behavior. Real visitors produce imperfect, varied behavior. Scripts can send clicks and scrolls, but they struggle to reproduce varied timing, movement, and hesitation. A zero-width or non-standard scrollbar can be one clue.
Behavioral checks are harder to spoof. The homepage lists robotic linear mouse movements, absence of humanlike mouse tremor, superhuman input speed below 1ms, grid-aligned movement patterns, and absence of clicks or scrolling. If your script does not add realistic pointer paths, click delays, and scroll variance, these checks will fail.
No single failed check means the visit is a bot. Accuracy comes from corroboration. BotRefund sends all signals into the prediction AI, which weighs the complete picture.
What the results mean for your automation workflow
If the dashboard shows Human with high confidence, your current headless setup passes BotRefund's checks. That does not mean it passes every detection system. Each vendor uses different signals.
If the verdict is Bot, look at the failed groups. Browser-internal failures suggest your stealth configuration needs work. Behavioral failures mean your interaction patterns look too mechanical. Network or hardware failures may point to your test infrastructure.
BotRefund's goal is to protect advertisers from invalid traffic. The homepage says bot clicks steal up to 20% of Google and Meta ad budgets. BotRefund proves bot clicks, negotiates with Google and Meta, and gets money back.
Across 2,500+ brands audited, 83% of clients recover funds. BotRefund builds refund-ready reports with click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. The homepage says this is the format Google and Meta accept.
Key facts about BotRefund's detection
| Attribute | Detail |
|---|---|
| Independent checks | 106 checks on individual signal pages; 110+ signals on the homepage |
| Reported confidence | 99% bot-detection confidence |
| Client recovery rate | 83% of 2,500+ audited brands recover funds from Google and Meta |
| Report format | Refund-ready with click IDs, campaign details, timestamps, session recordings, signal-by-signal reasoning |
| Detection layers | Browser, network, hardware, behavior, and attribution signals |
| Behavioral examples | Ghost clicks, honeypot traps, robotic mouse paths, no tremor, superhuman speed, grid paths, no clicks or scrolling, unnatural session durations |
| Integration | Client-side JavaScript |
Limitations of this testing approach
- The test endpoint may not be available on every plan. Check with BotRefund for access.
- The site uses two signal counts. Individual signal pages cite 106 checks. The homepage cites 110+ signals. Read the count in context.
- BotRefund's model can change. A setup that passes today may be flagged after a retrain.
- BotRefund's checks are not the same as other bot-detection vendors. Passing BotRefund does not mean passing all systems.
- One visit is only a snapshot. Run several visits with the same configuration to see a consistent pattern.
Frequently asked questions
How do I use BotRefund's test endpoint?
Ask BotRefund for the endpoint URL and access details. Run it with your headless setup, then confirm the result in the dashboard. The test endpoint is the first option in this workflow. If you do not have access, use the snippet method described above.
Can I test with a local HTML file opened via file:// protocol?
No. The page must be reachable by BotRefund. Use a public staging URL or a tunnel so the session can appear in the dashboard.
How many test visits should I run?
Run at least 5 to 10 visits with the same configuration. BotRefund's AI evaluates patterns, not a single tell.
If my script passes BotRefund, does it pass all bot detection?
No. Each vendor uses its own signal set. Passing BotRefund means your setup evades BotRefund's checks. Other systems may catch different signals.
What if my legitimate workflow gets flagged?
A single anomaly is not a bot verdict. Review the full signal breakdown and run more visits. If you need an exception, check with BotRefund.
Can I use the signal breakdown as evidence for ad refunds?
Yes. BotRefund creates refund-ready reports with click IDs, campaign details, timestamps, session recordings, and signal-by-signal reasoning. The homepage says this is the format Google and Meta accept.
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.