Skip to main content

Dashboards, alerts, and events

Use this area to move from one-off debugging to continuous product and support observability.

Dashboards​

Dashboards summarize behavior and trends across sessions.

Recommended starting views:

  • Session volume over time
  • Funnel drop-off in critical flows
  • Error-prone screens/events
  • Segment performance by device or region

Alerts​

Set threshold-based alerts for anomalies, for example:

  • Sudden replay volume spikes
  • Key event failure increase
  • Conversion path degradation

Alert ownership should map to response teams (support ops, product, engineering).

Events And Activity​

Use activity feeds to inspect behavior traces and operational changes.

Good practice:

  1. Define an event naming convention.
  2. Keep event payloads minimal and useful.
  3. Document event semantics for support and product teams.

Cross-Team Usage Pattern​

  • Support identifies customer impact patterns.
  • Product validates UX friction with replay evidence.
  • Engineering confirms root cause and release fix impact.

Note: Exact dashboard metric set may vary by enabled Sessions features and workspace permissions.

Next Steps​