Seatext library / BotRefund evidence
Why 99% Accuracy in Bot Detection Changes the Economics of Paid Advertising
99% accuracy matters because each percentage point below it translates directly into wasted ad spend and polluted conversion data. At 95% accuracy, a site spending $100,000 monthly on ads could lose $5,000 to undetected...
✓ Built for advertisers who need clear, refund-ready traffic evidence.
Bot detection accuracy is not an abstract metric. It determines how much of your advertising budget reaches actual humans versus automated scripts, and whether your optimization decisions are based on real behavior or contaminated data. When a detection system misses bots, you pay for clicks that never convert. When it flags real visitors as bots, you lose legitimate customers and skew the signals that ad platforms use to find more like them.
The source of BotRefund's 99% claim is a three-layer approach: each visit generates over 100 independent browser, network, device, and behavioral signals; those signals are cross-checked against each other so a single anomaly never triggers a verdict; and a prediction model weighs the full pattern instead of relying on any one rule. As the documentation puts it, "Accuracy comes from corroboration, not one browser tell."
What 99% accuracy actually means in practice
Accuracy in bot detection is usually expressed as the combination of two rates: the true positive rate (catching bots) and the true negative rate (letting humans through). A 99% figure typically means the system correctly classifies 99 out of 100 visits, whether bot or human. The remaining 1% splits between false negatives (bots that slip through) and false positives (humans blocked or mislabeled).
For a site spending $50,000 a month on Google and Meta ads with a 20% bot click rate — a figure BotRefund cites from its client base — that's $10,000 in bot traffic each month. At 95% detection, $500 of bot clicks still get billed. At 99%, only $100 does. Over a year, that's $4,800 saved. The same math applies to false positives: if 5% of your real visitors are misclassified, you lose their conversions and corrupt the audience signals that platforms use to optimize delivery.
The hidden cost of false positives
False positives are quieter but often more damaging than missed bots. When a real visitor is flagged as automated, three things happen: you lose that potential customer immediately; the ad platform records a non-converting click from what it thinks is your target audience; and your conversion rate drops, which can raise your cost per acquisition across the whole campaign.
BotRefund's documentation emphasizes that "privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior for genuine people." This is why the system treats every signal as evidence, not a verdict. A visitor using a corporate VPN with a locked-down browser might trigger a console debug anomaly, but if their mouse movement, scroll behavior, and session duration all look human, the AI weighs the full pattern and classifies them correctly.
How bot detection accuracy is measured — and where claims break down
Most vendors report accuracy on curated test sets. The MIT Sloan study found that high accuracy scores often come from training data that doesn't reflect the diversity of real-world traffic — different devices, networks, privacy tools, and bot sophistication levels. A confusion matrix (true positives, false positives, true negatives, false negatives) on a representative sample is the only way to know if a 99% claim holds in production.
BotRefund's approach is to run 106 independent checks per visit. These include browser API consistency (Console Debug Evaluator), timing anomalies (Impossible Tab Speed), window management tampering (window.open Tamper), and behavioral vectors like ghost clicks, honeypot interactions, linear mouse paths, missing micro-tremors, superhuman input speed, grid-aligned movement, absent engagement, and unnatural session durations. Each check adds one objective fact. The AI then evaluates how all signals fit together.
Why single signals fail and corroboration wins
A single anomaly — a missing browser property, a too-fast click, a linear mouse path — is not a bot verdict. Legitimate users on unusual setups generate anomalies constantly. The Console Debug Evaluator page states it plainly: "A single anomaly is not a bot verdict. Privacy tools, travel, corporate networks, and unusual devices can produce unexpected behavior for genuine people."
This is where the three-step process matters. First, each signal stands as independent evidence. Second, the system tests whether other signals support the same story — does the same visit also show impossible tab speed, missing mouse tremor, and honeypot clicks? Third, the prediction model weighs the complete pattern. Only when multiple independent vectors align does the system classify the visit as automated.
The role of AI in weighing evidence
Rule-based detection fails because bots evolve. A hard threshold on mouse speed catches today's scripts but misses tomorrow's that add random delays. A model trained on the joint distribution of 100+ signals across browser, network, device, and behavior dimensions can recognize the pattern of automation even when individual values look plausible in isolation.
BotRefund's documentation describes this as: "Our model weighs the complete picture across browser, network, device, and behavior evidence. By seeing how all signals fit together, it identifies a visit as bot or human with 99% accuracy." The key is that the model sees the relationships between signals — a visit with perfect browser APIs but inhuman timing and no scroll behavior is still flagged, while a visit with one odd API but natural behavior passes.
Real-world impact on ad budgets and lead quality
The financial stakes are concrete. BotRefund's homepage states: "Bot clicks steal up to 20% of your Google and Meta ad budget." The FinTrust case study shows a neobank recovering $140,000 in ad spend with a 14% average bot click rate and an 18% conversion rate increase after suppressing bot conversion events. The VP of Acquisition noted: "Enterprise-grade security is in our DNA, but ad fraud happens outside our product walls. BotRefund audit trails are the gold standard that Meta ad reps accept."
On Meta, invalid traffic often masquerades as a lead quality problem. The Meta invalid traffic guide explains: "Meta Ads Invalid Traffic can look like a campaign-performance problem before it looks like fraud. Ads Manager may report a steady cost per lead while the sales team receives unreachable contacts, copied messages, or enquiries that never progress." The distinction matters because treating every bad lead as fraud can make a team exclude a valuable audience. The guide recommends a structured audit comparing ad-platform data, website sessions, and CRM outcomes before changing targeting or requesting refunds.
Limitations and when accuracy claims need scrutiny
No detection system is perfect. The 99% figure applies to the overall classification across the traffic mix BotRefund sees. Performance can vary by bot sophistication, traffic volume, and how well the model has been exposed to similar patterns. New bot frameworks, residential proxy networks, and human-in-the-loop click farms are designed specifically to mimic the behavioral signals that detectors rely on.
Google's own documentation acknowledges this: automated filters "frequently fail to identify modern residential proxy networks and competitor click fraud." That's why the refund request process exists — advertisers must compile client-side behavioral proof (GCLID logs, session recordings, interaction timelines) to win disputes. BotRefund's value proposition includes capturing video proof for each bot click and negotiating with Google and Meta on the advertiser's behalf, with refunds recoverable back to 2017.
Accuracy also depends on implementation. The script must load correctly, fire on every page, and not be blocked by ad blockers or privacy tools. BotRefund claims "typical time to add BotRefund to your website and start your free bot audit" is about one minute with no credit card required, but real-world integration can involve CSP headers, tag manager configurations, and single-page app routing that affect coverage.
Key facts
| Metric | Value | Source |
|---|---|---|
| Independent checks per visit | 106 | S1 |
| Claimed classification accuracy | 99% | S1, S5, S6 |
| Bot click share of ad budget (client base) | Up to 20% | S2, S7 |
| FinTrust ad spend recovered | $140,000 | S4 |
| FinTrust average bot click rate | 14% | S4 |
| FinTrust conversion rate increase after suppression | +18% | S4 |
| Refund lookback window for Google Ads | 2017 | S2, S7 |
| Setup time for free bot audit | About one minute | S2, S7 |
| Detection vector categories | Click, Trap, Pointer, Motion, Speed, Path, Engagement, Session | S2, S7, S9 |
Hypothetical scenario: the 95% vs 99% difference over a year
Imagine two identical e-commerce brands, each spending $100,000 per month on Google and Meta ads. Both have a 20% bot click rate ($20,000/month in bot traffic) and a 3% conversion rate on human traffic. Brand A uses a 95% accurate detector. Brand B uses a 99% accurate detector.
Brand A misses 5% of bots — $1,000/month in wasted spend. It also misclassifies 5% of humans as bots. With 80,000 human clicks/month at $1.25 CPC, that's 4,000 real visitors blocked, losing roughly 120 conversions (3% rate). At $150 average order value, that's $18,000 in lost revenue monthly. Total monthly cost: $19,000.
Brand B misses 1% of bots — $200/month wasted. It misclassifies 1% of humans — 800 visitors blocked, 24 conversions lost, $3,600 in lost revenue. Total monthly cost: $3,800.
Over 12 months, Brand A loses $228,000. Brand B loses $45,600. The 4% accuracy gap costs $182,400 annually. This is why the accuracy number matters — it compounds across every campaign, every month, every platform.
FAQ
How do I know if my current bot detection is below 99%?
Run a side-by-side audit. Install a second detector in parallel for 30 days and compare classifications on the same traffic. Look for discrepancies in conversion rates, audience quality scores in ad platforms, and refund approval rates on invalid click disputes. BotRefund offers a free bot audit that maps bot percentage by campaign, placement, and device.
What happens when a new bot framework evades the 106 checks?
The AI model retrains on the new pattern once enough labeled examples appear. Because the system relies on corroboration across 100+ signals, a bot must simultaneously spoof browser APIs, timing, movement, engagement, and session behavior to slip through. That raises the cost of evasion significantly compared to single-signal detectors.
Does 99% accuracy apply to all bot types equally?
The claim reflects overall classification accuracy across the traffic mix BotRefund processes. Sophisticated residential proxy bots with human-in-the-loop interaction are harder to catch than basic headless Chrome scrapers. The system's strength is behavioral biometrics — micro-tremors, hesitation, varied timing — which are expensive to fake at scale.
Can I get refunds for bot clicks from past months?
Yes. BotRefund's documentation states they recover bot-click refunds from Google Ads spend dating back to 2017. The process involves exporting client-side behavioral proof logs, compiling GCLID evidence, and filing formal disputes with Google's Click Quality team and Meta's billing support.
How does bot detection affect my ad platform's optimization?
Ad platforms optimize toward your conversion events. If bot conversions pollute that signal, the platform learns to find more bots. Suppressing bot conversion events — as FinTrust did — retrains the platform's audience model on verified humans, which improved their conversion rate by 18%.
What's the difference between BotRefund and Google's built-in invalid click filters?
Google's filters are real-time and automated but "frequently fail to identify modern residential proxy networks and competitor click fraud," per the refund guide. BotRefund adds client-side behavioral collection (106 checks), video proof per click, and a managed dispute process. The two layers are complementary — Google catches the obvious, BotRefund catches what slips through.
Is there a traffic minimum for the free bot audit?
The pricing tiers shown start at "Under $10,000/mo" ad spend, but the free audit offer appears open to any site willing to install the script. The audit maps bot percentage by campaign, placement, device, and geography, giving you a baseline before deciding on paid protection.
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.