Excluding bot traffic from Polar Pixel data
Last updated: October 23, 2026
Polar flags Polar Pixel sessions and events that look like bot traffic, so you can leave them out of your reports.
How bot detection works
Polar doesn't use a fixed blocklist. Instead, it looks for unusual traffic patterns across IP addresses, user agents and URL paths. For example, it flags an IP address that sends the same user agent hundreds of times without adding anything to cart, or a scraper that keeps hitting the same URL pattern.
Flagged traffic is marked with the Is Bot Session dimension, which is available on Polar Pixel sessions and events.
Is Bot Session | Meaning |
|---|---|
True | The session or event was flagged as bot traffic |
False | The session or event is from a real visitor |
Bot traffic isn't removed from your reports automatically. Detection can occasionally flag a real visitor, so Polar gives you the dimension and lets you choose when to exclude it.
Exclude bot sessions from your reports
Add the filter Is Bot Session = False to your reports manually in the report editor or use Ask Polar or the Polar MCP to update your reports.
FAQs
Why do I still see bot traffic in today's numbers?
Detection runs a few hours after each session ends. Until it finishes, today's data can include bot traffic that hasn't been flagged yet.
How far back does bot detection go?
Bot flags are available from October 1, 2025 onwards, so you can compare year over year. Traffic before that date isn't flagged.
Does Polar filter bots out of my sessions by default?
No. Use the Is Bot Session dimension to exclude them, as shown above.