Session Replay
Bug reports include a timestamped link to the user's session in PostHog, LogRocket, FullStory, or Hotjar.
When a user submits a bug report, Callout automatically detects your session replay tool and includes a timestamped link. Your engineers click it and see exactly what the user was doing — no guessing, no back-and-forth.
Supported Providers
| Provider | Setup |
|---|---|
| PostHog | Add your project ID and host URL at Feedback > Integrations > PostHog |
| LogRocket | Automatic — no configuration needed |
| FullStory | Automatic — no configuration needed |
| Hotjar | Automatic — no configuration needed |
As long as the provider's SDK is loaded on the same page as Callout, the session link is included in every bug report. Callout checks for providers in the order listed above and uses the first one it finds.
Callout only reads the session ID from your replay tool. It doesn't send any data to them or affect their behavior.
If you have multiple replay tools installed, Callout uses the first one it finds (PostHog > LogRocket > FullStory > Hotjar). Only one link is included per report.
What It Looks Like
The session replay link appears in your GitHub issue or email report, timestamped to about 7 seconds before the user submitted — giving full context of the moments leading up to the bug.
The link takes your team directly to the recording at the exact moment — no scrubbing through a 20-minute session to find what happened.
Don't Have a Replay Tool?
No problem. Bug reports still include annotated screenshots, console errors, and browser details. Session replay links are a bonus — everything else works without them.
When you're ready to add a replay tool, Callout will detect it automatically on the next page load.