Get Started
Data
Analytics
Session Replay
Feature Experiment Web Experiment
Admin
SDKs APIs
Partners
FAQ
Overview of Amplitude Data Getting set up with Amplitude Data Autocapture Visual Labeling Data structure video walkthrough Debug with the Amplitude Chrome extension Manage your Amplitude Data settings Data backfill
Plan your taxonomy Planning and instrumentation workflow Create a tracking plan Work with branches Ampli and developer tools Monitor your data with observe Protect your schema from unexpected data Integrate Jira with Amplitude Data Manage access to sensitive data with Data Access Control
About user properties and event properties Event and property descriptions Event and property display names Event categorization Set an event's activity status Property types IP address and location properties Override a property definition Revert an overridden property definition Using property groups Cross-project analysis with Portfolios
Organize your tracking plan with Data Assistant Remove invalid or incorrect data Block bot web traffic Change the description of an event or property Fix your data with transformations Time to Live (TTL)
Custom events Object management Derived properties Lookup Tables Channels
Warehouse-native Amplitude: Overview Build a warehouse-native data model Warehouse-native Amplitude: Best Practices Warehouse-native Bulk Model Management Warehouse-native DBT Integration
Amplitude Audiences overview
Sync to third-party destinations
Data
/

Block bot web traffic

This article helps you:

  • Understand how bot traffic can affect ingested data from third party sites

  • Learn how to create a block filter to exclude bot web traffic

If you're tracking events on public, unauthenticated websites, your metrics may be affected by bot web traffic from crawlers, scrapers, and other similar tools. Amplitude Data allows you use a block filter to prevent that data from being ingested at all.

How bot blocking works

Bot traffic is blocked based on User-Agent, as identified by the IAB/ABC International Spiders and Bots List. This applies by default to data sent via the legacy JavaScript SDK or the TypeScript Browser SDK (version 1.10.0 and later). You can also provide the user_agent field directly on events sent via the HTTP API or Batch API. Be careful when doing this, as the value must represent a valid browser or the event will be dropped.

Any data filtered out by a block filter cannot be recovered because it is never ingested in the first place.

Create a block filter for bot web traffic

To create a block filter for bot web traffic, follow these steps:

  1. Make sure you’re on main, as filters are not accessible from any other branch.
  2. In the left-hand sidebar, click Filters, then select the Block Filters tab.
  3. Click + Create Block Filter to open the Filter Configuration fly-out panel.
  4. Select Bot Traffic from the Block drop-down.

block_filter.png
5. When you’re ready, click Block Data to initiate the block filter.

Was this page helpful?

Thanks for your feedback!

June 5th, 2024

Need help? Contact Support

Visit Amplitude.com

Have a look at the Amplitude Blog

Learn more at Amplitude Academy

Terms of Service Privacy Notice Acceptable Use Policy Legal

© 2024 Amplitude, Inc. All rights reserved. Amplitude is a registered trademark of Amplitude, Inc.