Excluded IPs & bots
Exclude internal traffic and bot activity.
Last updated June 3, 2026
Excluded IPs, explicit internal or QA visitor IDs, and bot filtering keep reports focused on real visitors instead of your team, test devices, uptime checks, crawlers, and automated traffic. Bot filtering also detects distributed, zero-engagement crawler cohorts that rotate IP addresses and browser versions across the same cloud network. Bot diagnostics retain capped request and network-owner evidence for 30 days outside normal reports and exports. Raw IP addresses are discarded after country lookup. If that lookup fails, the IP is encrypted in a restricted retry record for no more than 24 hours and erased after success or expiry. When a signed-in workspace member has a matching tracking visitor cookie, Grometrics automatically marks that visitor as internal. Authenticated customer visitors who are not members of the tracked workspace remain included.
Event model
| Event | Used for |
|---|---|
| excluded_ip | Prevents internal visits from entering reports |
| excluded_visitor | Removes named staff devices and QA installs while retaining raw records |
| bot_filter | Removes crawler and automation traffic |
| test_event | Keeps setup checks separate from production reporting |
What happens next
Existing staff and QA visitors can be excluded immediately from their visitor profile. Future matching workspace-member visitors are excluded after their next successful sign-in. Manage or remove excluded visitors in Tracking settings.
Troubleshooting
Data is missing
Confirm the tracker is installed, the site ID is correct, and the event is not blocked by consent or an ad blocker.
Data looks duplicated
Confirm the tracker is initialized once per page or app boot.
Was this page helpful?