Checkpoint Docs
Dashboard

Analytics & Reporting

Understand detection analytics, traffic patterns, and AI agent activity

Overview

Checkpoint provides comprehensive analytics for understanding the AI agent and bot traffic hitting your applications. View real-time detections, analyze trends, and export data for reporting.

Detection Monitor

The Monitor tab provides a real-time feed of detections as they happen.

Each entry shows:

FieldDescription
TimestampWhen the detection occurred
Detection Classhuman, ai_agent, bot, or incomplete_data
ConfidenceScore from 0–100
Agent NameIdentified agent (e.g., ChatGPT, Googlebot)
IP AddressSource IP of the request
User AgentThe request's user agent string
PathURL path that was accessed
SessionConsolidated session identifier

Filtering

Filter the monitor feed by:

  • Detection class (AI agent, bot, human)
  • Confidence range
  • Time period
  • Agent name
  • IP address

Session Grouping

Detections are grouped into sessions. Checkpoint consolidates requests from the same visitor into a single session, even if the client-side session ID resets (which happens every 30 minutes for privacy). This gives you an accurate count of unique visitors rather than inflated session numbers.

Session consolidation uses multiple signals (fingerprint, IP address, user agent, agent type) to group related requests within 30-minute windows.

Analyze

The Analyze tab provides aggregated analytics across your detection data.

Key Metrics

MetricDescription
Total SessionsUnique visitor sessions in the selected period
Detection RatePercentage of sessions classified as agents or bots
AI Agent SessionsSessions classified as AI agents
Bot SessionsSessions classified as traditional bots
Human SessionsSessions classified as human visitors

Agent Type Breakdown

A visual breakdown of traffic by detection class:

  • AI Agents — ChatGPT, Claude, Perplexity, Gemini, and other AI assistants
  • Bots — Googlebot, Bingbot, scrapers, and automated tools
  • Humans — Regular browser traffic
  • Incomplete Data — Requests with insufficient signals

Historical charts showing detection patterns over time:

  • Detection volume by day/week/month
  • Classification distribution over time
  • Confidence score distribution
  • New vs returning agents

Top Agents

Ranked list of the most frequently detected agents, showing:

  • Agent name
  • Detection count
  • Average confidence score
  • First and last seen dates

Date Range Selection

All analytics views support custom date ranges:

  • Last 24 hours — Recent activity
  • Last 7 days — Weekly overview
  • Last 30 days — Monthly trends
  • Custom range — Pick specific start and end dates

Cross-Project Analytics

Organization-level analytics (available at the organization Analyze page) aggregate data across all projects, giving you a bird's-eye view of agent activity across your properties.

Understanding Detection Data

Detection Rate

The detection rate is the percentage of sessions classified as non-human:

Detection Rate = (AI Agent Sessions + Bot Sessions) / Total Sessions × 100

A typical detection rate varies by industry:

IndustryTypical Detection Rate
E-commerce30–50%
Content/Media40–60%
SaaS20–40%
API50–70%

Confidence Distribution

Review the distribution of confidence scores to tune your enforcement policies:

  • High cluster (80–100) — Strong detections, safe to enforce
  • Medium cluster (50–79) — Review manually, consider logging only
  • Low cluster (0–49) — Likely noise, avoid enforcing

Use the confidence distribution to choose your enforcement threshold. Start by logging everything, then set your block threshold based on where the clusters fall.

Policy Tuning Workflow

  1. Start in detect mode (no enforcement)
  2. Review Monitor for false positives
  3. Analyze confidence score distribution
  4. Set enforcement threshold (typically 80+)
  5. Enable enforcement with tuned policy
  6. Monitor continuously for changes

Next Steps