Bot Center
The Bot Center shows you everything Clickport's bot protection does for your site. It is one card in Settings → Bot Center, split into numbered sections. Everything on it is automatic: there is nothing to configure, and blocked traffic never reaches your analytics. All numbers cover the last 30 days unless a section says otherwise.
01 · Protection
The header answers the question that matters most: is the protection working. The green dot means it is active, with the number of detection layers running and when the blocklists were last refreshed.
The three numbers below it: how many visits were blocked today (this ticks live while you watch), the 30-day total with its change against the prior 30 days, and how much of your raw traffic was bots.
Do not be alarmed by a big share. On most sites, well over half of raw traffic is bots. That is exactly what the protection is for.
02 · Detections
One bar per day for the last 30 days, so you see the rhythm of the blocking at a glance. Steady bars are normal background noise. A sudden spike is usually a scraper wave. Hover a bar for the exact count of that day. Below the bars: how long ago the protection last fired, updated live while the page is open. The Learn more link in this corner brings you here.
03 · Blocked by method
The last 30 days, grouped by the layer that caught the traffic. Headless signals catch automated browsers pretending to be real ones. Datacenter IPs catch requests coming from cloud servers instead of homes and phones. Bot user agents catch crawlers that identify themselves. The share column tells you what your bot traffic is mostly made of.
04 · Top blocked
The specific signals, networks, and crawlers behind the blocks. A scraper wave usually shows up here as one name with a suddenly big number, often the cloud provider it runs on.
05 · AI crawlers
AI-related crawlers that visited, grouped by what they were doing: indexing for AI search, collecting model training data, or fetching a page live for an answer. This section counts them. The full AI picture, with verified reads and citations per engine, lives in AI Agents.
06 · Zero-engagement sessions
A health gauge, not a block count. It shows the share of counted sessions with zero engagement: no scroll, no click, no meaningful time on the page. Some zero-engagement traffic is human. A rising share can mean a bot pattern the layers have not caught yet. Expand a device row to see the screen sizes behind it.
07 · AI agent verification
Every hit that claims to be a known crawler is checked against the operator's published IP ranges. Verified means the request really came from that operator. Spoofed means something pretended to be a known bot; those hits are excluded from every AI number in the dashboard. Unverifiable means the operator publishes no ranges to check against.
This section appears once the AI Agents connector is set up, because the raw hits arrive through it.
08 · Blocklist coverage
The always-on lists behind the automatic blocking, refreshed daily: datacenter IP ranges (including Google Cloud's published VM ranges), datacenter ASN ranges, curated and community user agent signatures, spam referrer domains, and VPN ranges. When a scraper hides behind a normal browser profile on a cloud server, these lists are what catch it.
Flagging sessions yourself
If something slips through, you can flag any session as a bot from the Sessions panel. Flagged sessions are excluded from all future analytics. Bot stats are retained for 90 days.