Auto-detected — zero configuration

Session Replay Integration

Callout auto-detects PostHog, LogRocket, Hotjar, and FullStory. Replay links are attached to every bug report so your team can watch the full user journey.

TL;DR

If your app uses PostHog, LogRocket, Hotjar, or FullStory for session recording, Callout detects it automatically and includes the replay URL in every bug report. Your team clicks the link and watches exactly what the user did before reporting the bug — no manual lookup, no extra configuration.

Replay links
included automatically.

No API keys to enter. No webhooks to configure.

1

Callout scans for replay tools

When the widget loads, Callout checks for global JavaScript objects from PostHog, LogRocket, Hotjar, and FullStory. If any are present, it knows a session replay is running.

2

Replay URL is extracted

Callout calls the replay tool's API to get the current session recording URL. Each tool has its own method — Callout handles all of them. The URL points directly to the session that matches the bug report.

3

Link delivered with the report

When the user submits a bug report, the session replay link is included alongside the screenshot, console errors, and device details. Your team clicks the link in the GitHub issue or ticket and watches the full session.

Watch the bug
happen live.

Zero Configuration

No API keys, webhooks, or integration setup. If PostHog, LogRocket, Hotjar, or FullStory is already on your page, Callout detects it and includes the replay link. It just works.

Full User Journey

Session replays show everything the user did before reporting the bug — clicks, scrolls, navigation, and interactions. This gives your team far more context than a screenshot alone.

Multi-Tool Support

Using more than one replay tool? Callout detects all of them and includes every replay link in the report. PostHog and FullStory running together? Both links are attached.

Faster Reproduction

Instead of asking users to describe their steps, your team watches the session replay. This eliminates back-and-forth and dramatically reduces the time from report to reproduction.

Common
questions.

Which session replay tools does Callout support?

Callout auto-detects PostHog, LogRocket, Hotjar, and FullStory. If any of these tools are running on your page, Callout finds the current session replay URL and attaches it to the bug report automatically.

Do I need to configure session replay integration?

No configuration is needed. Callout detects session replay tools by checking for their global JavaScript objects on the page. If PostHog, LogRocket, Hotjar, or FullStory is loaded, the replay link is included in the report automatically.

How does the session replay link appear in bug reports?

The replay link is included as a clickable URL in the GitHub issue, Linear ticket, or Jira ticket. Your team can click it to watch the full user session leading up to the bug, seeing exactly what the user did.

What if I use multiple session replay tools?

Callout checks for all supported replay tools and includes links from every one it detects. If you run both PostHog and FullStory, both replay links will be attached to the bug report.

Try Callout free — no account required

Session replay links in every bug report. Free forever.

Get Started Free