Analytics & Operations
This documentation covers SCaptcha 2.3.0. Configuration-dependent features are identified separately.
Analytics deep dive
Use the analytics dashboard to track verification results over time and validate tuning changes.
Filters let you isolate spikes by outcome, form, country, ASN, device, or time window so you can investigate without noise.
Request logging & event types
All outcomes are logged via SCaptchaRequestLogger into scaptcha_request_log with IP, user agent, browser/OS/device, ASN/provider, country/region/city, request URI, reason, and serialized Sentinel/JS payloads.
Event types are verification, sentinel, and fallback. Analytics charts aggregate verification and sentinel events only; fallback is logged but not charted.
Analytics UI coverage
The ACP analytics view includes a time-series chart, summary totals, and top lists for devices, browsers, OS versions, app versions, providers, ASNs, countries, regions, and cities.
A log grid with filters and a payload details dialog lets you inspect individual requests and Sentinel/JS payloads.
Export and retention
CSV export supports field selection, filters, output options, and clipboard download for fast incident reviews.
Request-log retention defaults to 90 days and can be configured from 1 to 3,650 days. The cleanup job removes rows older than the cutoff and keeps rows exactly on it.
Analytics and retention
Request analytics are on by default. Logs can contain linkable operational data, including IP address, user agent, request, network and location fields, reasons, and submitted browser telemetry. Retention defaults to 90 days and can be set from 1 to 3,650 days. Turning analytics off stops new collection but does not erase existing rows or exports.
What operators need to review
Document enabled features, limit access to security logs, and assess optional external services separately. SCaptcha does not replace legal review or accessibility testing of the complete website.