Skip to main content

Verify capture and investigate issues

After installation, validate that captured sessions are complete enough for support and product debugging.

Capture Verification Checklist​

  1. Confirm new sessions appear within expected time.
  2. Open a replay and verify page transitions are visible.
  3. Check user interaction timeline for key events.
  4. Confirm session metadata (environment, identifiers, key attributes).

Investigation Workflow​

  1. Start from the customer conversation.
  2. Open related replay.
  3. Reproduce the reported issue from timeline and event sequence.
  4. Add root-cause notes back into conversation/internal systems.

What Good Data Looks Like​

  • Session starts at meaningful entry point.
  • Critical UI interactions are visible.
  • Relevant event names are present and interpretable.
  • Masking works without over-redacting operationally useful fields.

If Sessions Are Missing​

  • Check install tracker status.
  • Check environment targeting.
  • Check permission visibility for the current role.
  • Check Sessions URL/auth configuration.

Tip: Keep one "known-good" test account and scripted path so you can quickly re-validate capture after frontend releases.

Next Steps​