Dashboard

Analytics & Reporting

Understand detection analytics, traffic patterns, and AI agent activity

Overview

Vouched KYA provides comprehensive analytics for understanding the AI agent and bot traffic hitting your applications. View detections as they arrive, analyze trends, and export data for reporting.

Activity Feed

The per-request feed is the Activity screen, in the left rail under Detect: see Dashboard Overview.

SDK, Pixel, and Beacon rows land here within roughly a second. Gateway rows are batched and can take up to 30-40 seconds to appear, so "real-time" describes the client and SDK surfaces, not the Gateway. See Detection Semantics for why.

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 Activity feed by:

  • Detection class: ai_agent, bot, human, or incomplete
  • Verdict: allow, block, redirect, instruct, or challenge
  • Agent name or session ID, in the search field
  • Time: the live last 24 hours, or a date range of up to 7 days

Links from other pages can also narrow the feed to one page path or to one policy's decisions.

Session Grouping

Detections are grouped into sessions by the session ID the visitor's browser sends. Two browsers are never merged into one session, even when they share a network address, user agent or device fingerprint. A browser that starts a new session ID counts as a new session, and a request that carries no session ID counts as a session of its own.

Sessions are never inferred from IP address, user agent or fingerprint, and there is no time window that merges them.

Analytics

The Analytics screen, in the left rail under Detect, groups the selected project's detection data into sessions.

Lenses

Pick a lens to choose which sessions the page shows:

LensRows
AIOne row per AI agent (ChatGPT, Claude, Perplexity, Gemini, and others), ranked by sessions
HumansOne row per human session
BotsOne row per bot (Googlebot, Bingbot, scrapers, and other automated tools), ranked by sessions
BlockedOne row per session with at least one blocked request
UnclassifiedOne row per session with too few signals to classify

On an AI or Bots row, Activity opens the Activity feed for that agent, and Details opens the agent's own page. On a Blocked row, Inspect opens the session, with what it did and why it was blocked. The search field narrows the rows to matching agents, humans, or DIDs.

Summary and chart

Above the rows, a summary counts the sessions, requests, agents, users, and blocked sessions in the window. users counts identified users, with the share of sessions that were identified. The Humans and Unclassified lenses show sessions, requests, and blocked only.

A chart plots sessions across the window, with blocked sessions drawn underneath when there are enough to show. On the Blocked lens, it plots blocked sessions as bars.

Date Range Selection

On Analytics, pick Last 7 days, Last 30 days, or Last 90 days.

Activity shows the last 24 hours live. Pick a date range to see up to 7 days at a time.

Cross-Project Analytics

With no project selected in the project switcher, Analytics aggregates data across all projects, giving you a bird's-eye view of agent activity across your properties.

Policy Tuning Workflow

  1. Start in detect mode (no enforcement)
  2. Review Activity for false positives, and note the confidence of the requests you would act on
  3. Set enforcement threshold (choose it from the band model; the high band starts at 71)
  4. Enable enforcement with tuned policy
  5. Monitor continuously for changes

Identified Users

If your site calls window.Checkpoint.identify() when users log in (see the Pixel JavaScript API), identified-user data appears throughout the dashboard.

Activity Feed Badges

Once a user is identified, their information appears as a blue badge next to each session in the Activity feed, following the same email > userId > anonymous attribution fallback used throughout the dashboard:

  • Email badge: Shows 👤 john.doe@example.com if email trait was provided
  • User ID badge: Shows 👤 user-123 if only userId was provided (no email)

Quick Find: Look for the blue badge with a user icon (👤) next to a session. This badge only appears for identified users.

Session Details Panel

When you expand a session row, the details panel shows:

  • User ID: Displayed in the connection information
  • Email: If provided in user traits
  • Name: If provided in user traits
  • Custom traits: Additional properties you sent via identify()

If a session that should be identified has no user badge, see User badge not appearing in dashboard in the Identify Users cookbook.

Next Steps