Understand Retention and Event-Level Statistics

Read time-series and event results with freshness, retention, and deletion context.

Best for: Authorized producers, analysts, accessibility leads, organization owners, and support staff.

Before you start

Availability depends on role, event access, plan entitlements, retained source data, export/AI/statistics features, and privacy policy.

• Confirm exact organization, event, language, and reporting period.
• Verify requester, recipient, and retention/privacy authorization.
• Preserve raw source data before cleanup, editing, or deletion.

What to know

1. Confirm retention. Transcript/session/audience/technical availability.
2. Open event stats. Verify event/date/team.
3. Inspect timeline. Relate peaks/gaps to cues/incidents.
4. Inspect language/output. What was live.
5. Interpret retention. Session/browser not people.
6. Correlate audit. Operations/incidents.
7. Account for deletion. Removed data may not return.
8. Export evidence. Label scope/freshness.

What this unlocks: The deliverable or analysis is correct for the intended scope, reviewed, reproducible, and protected according to policy.

Check your understanding

• Trends avoid unsupported causation/identity.
• Time zone/window recorded.
• Retention explicit.

Common misconceptions

Gap

Check live state, retention, service, filter.

Inflated peak

Review refresh/embed/bots/shared devices.

History absent

Check deletion/retention/org.

Good to know

• Data can be personal/technical.
• Do not deanonymize.
• Follow retention.

Related guides

• Use Statistics Filters and KPIs
• Review Audit and Session History
• Export Analytics as CSV or JSON

Documentation status: Draft for operational, privacy, and analytics review before publishing.