> For the complete documentation index, see [llms.txt](https://vampauth.gitbook.io/vampauth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vampauth.gitbook.io/vampauth-docs/features/analytics.md).

# Analytics and live sessions

Checkpoint activity, lifetime key usage, loader deliveries, and live sessions measure different things.

## Date filters

Management analytics accept UTC `from` and `to`. Ranges include the start and exclude the end: `[from,to)`. Default: 30 days. Maximum: 90 days.

Only checkpoint events use that window. Key uses, activations, and resets are lifetime counts. Loader counters begin at their deployment baseline without backfill; `windowed_deliveries` is null.

## Delivery isn't execution proof

Successful loader admission records authorization/delivery, not proof that every script line ran. Early malformed/rate-limited attempts aren't included. Served payloads receive delivery credit; eligible denials belong to the loader URL.

Last-served-key cohort stats include those keys' lifetime uses elsewhere, including standalone checks. They aren't historical per-loader rankings.

## Presence

Advisory sessions are process-local and reset on restart. Durable active leases are unexpired database records. Don't add them and call the result unique users. Analytics domains a teammate cannot access return null.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vampauth.gitbook.io/vampauth-docs/features/analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.