> ## Documentation Index
> Fetch the complete documentation index at: https://docs.puntego.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Analytics and Sessions

> Trace one customer outcome cohort to the exact conversations, actions, Experiences, and evidence behind it.

# Analytics and Sessions

Puntego separates customer outcome analysis from runtime/model diagnostics. The
Analytics workspace follows one retained cohort through exposure, engagement,
guidance, action, verified resolution, repeat contact, and equivalent contact
value. Runtime latency, cache, model, and token diagnostics remain a separate
operational view.

## Global filters and evidence

Analytics and Sessions support URL-backed filters for customer, account,
audience, role, route, Experience, action, environment, event, experiment,
variant, outcome, and date range. Known duplicated, malformed, or oversized
parameters are rejected instead of silently broadening the result.

Every outcome count links to the matching retained sessions. Action-completion
links require a completed action result on the same conversation; Experience
completion links require the completed Experience event rather than any event
from that Experience.

## Workspace saved views

Use **Save for workspace** to preserve the current canonical filter link. Saved
views are shared with every current workspace member and are limited to 12
Analytics views and 12 Sessions views per workspace. The creator can remove a
view; owners and admins can remove any view. Removing a saved view does not
invalidate links that teammates already copied.

Older browser-only saved views are not uploaded silently. The view panel offers
an explicit **Import browser views** action, validates every link on the server,
and discards pagination cursors and unknown query parameters before sharing it.

## Data boundaries

* Routes are retained as paths only; origins, credentials, query strings, and
  fragments are not exposed as route dimensions.
* Empty Postgres results stay empty and never fall back to unrelated in-memory
  development fixtures.
* Every aggregate and supporting-session lookup is scoped by organization ID in
  addition to row-level security.
* Saved views contain filter links and labels, not transcript text or provider
  credentials.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.