Analytics and Retention

Understand usage metrics, reporting periods, quotas, and analytics retention.

Open Analytics in a workspace to review API usage and validation activity.

Reporting period

The reporting-period control filters the overview cards, charts, geographic data, version adoption, and event log. Requests today always means requests since midnight in the workspace timezone; it is not limited to the selected period.

Metrics

• Total requests: events in the selected period.
• Unique keys: distinct masked license keys observed in the selected period.
• Success rate: successful 2xx/3xx responses divided by total requests.
• API activity: successful and failed requests over time, including the seven-day moving average.
• Status distribution: response-code breakdown.
• Top countries: traffic by resolved region when geographic data is available.
• Version adoption: client versions reported by requests.

Empty charts mean no data was collected for the selected period; they do not indicate an outage.

Event log

Use the event log search and endpoint filter to find requests by masked license key, IP address, or endpoint. Export the filtered results as CSV when you need an operational report.

Quotas and retention

The quota card shows requests remaining on the current plan and the next reset date. Retention varies by plan. A free-plan warning appears when the selected range includes days outside the plan’s retained window; those earlier days may be empty.

Analytics masks license keys and should be treated as operational telemetry, not a source for recovering raw secrets.