CRO Glossary
Bot Traffic Filtering
The process of identifying and excluding non-human traffic from experiment data so results reflect real user behavior.
Bot traffic filtering is the practice of detecting and removing automated, non-human visits — search engine crawlers, scrapers, monitoring services, and increasingly AI agents — from the data used to analyze an experiment. If left in the dataset, bots can inflate traffic counts, skew conversion rates, and in some cases falsely trigger or suppress a winning variant simply because bots behave very differently from real users (for example, never completing a purchase, or hitting every page at machine speed).
Practitioners care about this because even a small percentage of bot traffic concentrated in one variant, due to imperfect randomization or crawler scheduling, can distort results enough to create a false positive or mask a real effect. It's a quieter cousin of sample ratio mismatch: the traffic split may look fine in aggregate, but the composition of that traffic is contaminated.
A common example is an experimentation platform that logs a spike in "conversions" from a variant overnight, only to discover the traffic came from a monitoring bot repeatedly pinging the page. Most mature testing tools filter known bot signatures (user-agent lists, IP ranges, click patterns) automatically, but teams running custom instrumentation should build explicit filtering rules and periodically audit raw logs, especially after seeing an unexplained metric spike.
Good practice includes filtering both at collection time (via known bot lists and behavioral heuristics) and at analysis time (via anomaly checks like implausibly high click rates or zero time-on-page), since no single filter catches every bot.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply bot traffic filtering.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.