Skip to main content

Everything you need to switch from Optimizely Classic to X in one place: See the Optimizely X Web Transition Guide.

Optimizely Knowledge Base

Bot and spider filtering in Optimizely X

  • Optimizely X Web Experimentation
  • Optimizely X Web Personalization
  • Optimizely X Web Recommendations

This article will help you:
  • Identify which bots are filtered out by Optimizely X Web
  • Learn how bots affect experiment results, monthly unique visitors (MUVs), and billing

Internet bots and spiders are software applications that run repetitive, automated tasks over the Internet. Optimizely X Web uses the IAB/ABC international spiders and bots list to classify non-human traffic and filter it out of your results. The IAB/ABC list is an actively maintained record of user agents used by known spiders and bots. The list is updated on a monthly basis.

How does bot and spider filtering affect my results?
Bots and spiders don't behave like real users. They typically run repetitive, automated tasks over your website or app at a much higher rate than real users, with the purpose of crawling your content and analyzing it. As a result, bots and spiders usually inflate the volume of traffic to your site and may skew your conversion metrics.
Removing bot and spider traffic from your results generally decreases the volume of traffic, such as the total number of visitors or sessions, and makes your measurements more accurate.
How does bot and spider filtering work?
Optimizely reads the User-Agent header for each request and determines whether it matches with an entry in the IAB/ABC list. If there is a match, Optimizely classifies the request as non-human and automatically excludes it from the results.
Are there any prerequisites for using bot and spider filtering?
Bot and spider filtering relies on the client’s User-Agent header to work. For web traffic, the User-Agent header is normally sent with every request, so Optimizely X Web customers will automatically benefit from it.
Since the IAB/ABC bot list relies on the browser's user agent strings to identify bots, Optimizely X bot filtering has no effect on Full Stack results.
Optimizely Full Stack only filters results automatically for JavaScript SDK network requests for events from the browser. In this case, the User-Agent request header contains the same value in navigator.userAgent(the visitor's browser's user agent string). This means that events coming from the JavaScript SDK will automatically use Optimizely's bot filtering.
To filter traffic from bots in Full Stack experiments, you can use Optimizely's JavaScript SDK or implement one of the following customizations:
  • If you can identify bots on your own, use getVariation() for bots and activate() for real visitors. This will forego dispatching a decision event for bots, which means Optimizely will not count them on the Results page.
  • Use getVariation() instead of using activate() in your backend. Include the Javascript SDK on the page and call activate() on the page instead of in your backend. This moves the decision event to the front end, where user agents are captured and bot filtering will take effect.
  • Customize the Optimizely SDKs to pass each visitor's user agent string in the User-Agent request header when dispatching events. This solution will probably require a non-trivial amount of work.
Can I opt out of bot and spider filtering?
No. Optimizely X Web automatically applies bot and spider filtering to all traffic as long as the User-Agent header is present in the request.
Does bot and spider filtering affect the way search engines crawl my site?
No, search engine crawlers will still see your site. To make sure that your SEO is not affected, take a look at our article on A/B testing and search engine optimization.
How does bot and spider filtering affect my monthly unique visitor (MUV) allotment?
Traffic from bots and spiders that are filtered is not included in the MUV allotment for your account.
Am I billed for bot and spider traffic in my experiment?
We will waive any overage charges incurred as a result of bot or spider traffic. Please contact your Customer Success Manager if you believe you have incurred overage charges due to bot or spider traffic.
How can I estimate bot and spider traffic levels for my site?
Contact your Customer Success Manager to learn more about your site’s historical bot and spider traffic levels.