Product capabilities
Combining Bot, VPN, and Proxy Filtering Signals
Bot behavior and intermediary networks answer different questions, so a sound filter keeps their evidence separate before applying policy.
Separate client behavior from network path
Bot indicators describe possible automation in the browser or request sequence, while VPN and proxy indicators describe how traffic reached the service. A real visitor may use a VPN, and an automated client may connect from an ordinary access network.
Combine evidence without hiding its source
Evaluate browser capabilities, request consistency, repetition, reputation, ASN type, proxy observations, and campaign context as distinct inputs. Decision records should retain the contributing factors rather than collapse everything into an unexplained blocked label.
Assign actions by confidence and purpose
Use exact rules for verified allowlists or explicit campaign boundaries, and reserve scored treatment for uncertain combinations. A conservative destination can handle ambiguity where an irreversible rejection would create unnecessary loss.
Protect legitimate operational paths
Corporate gateways, privacy services, accessibility tools, preview fetchers, QA automation, and known partner integrations may trigger parts of the filter. Document narrow exceptions with owners and expiry conditions instead of weakening controls for all traffic.
Release with reason-level monitoring
Replay labeled fixtures, enable changes on a bounded flow, and compare decisions by reason, source, market, and network category. Review threshold-adjacent events and roll back if the affected population differs from the test expectation.