Analytics

Understand aggregate Cap and organization engagement.

Cap records aggregate viewing and collaboration activity for shared recordings. The exact dashboard depends on whether you are looking at one Cap or an organization.

Per-Cap activity

The recording owner and authorized organization members can see the Cap's view count alongside comments and reactions. The view count is based on distinct analytics session identifiers within the requested period rather than a promise that every refresh is a new person.

Cap does not identify every anonymous viewer by name. Treat the count as aggregate reach, not an attendance register.

Organization analytics

The organization analytics dashboard supports these ranges:

• Last 24 hours
• Last 7 days
• Last 30 days
• Lifetime

It includes totals for Caps, views, comments, and reactions, plus time-series and breakdown views for countries, cities, browsers, operating systems, devices, and top Caps. Results can be filtered to an individual space or Cap.

Interpret the numbers carefully

• A session identifier is not the same as a verified human identity.
• Anonymous and signed-in playback can both contribute to aggregate data.
• A view count does not prove that the viewer watched the full recording.
• Short windows can change as new telemetry arrives.
• Organization, space, and Cap filters change the population being measured.

Use comments, reactions, and the recording's context alongside views when assessing engagement.

Review analytics with an agent

An agent can query a bounded organization range and then compare it with the context from relevant Caps.

cap guide --json
cap organizations list --json
cap analytics --organization <organization-id> --range month --json

Ask the agent to state the time range and filters, separate observed metrics from interpretation, and avoid changing anything. See Agent Workflows.