See how users interact with your site before they submit a bug

Session Replay is like a time machine for your website. It lets you see what your users did right before they reported an issue—no extra effort needed from them. This feature makes it easier for developers to reproduce and fix problems by providing direct insight into user actions.

What Is Session Replay and How Does It Work?

Session Replay records your users’ experience on your site, capturing both what they see (like screen content) and what they do (like clicking or scrolling). Whenever someone reports an issue, you can "rewind" and watch what led up to that moment.

With Session Replay, you can answer questions like:

Which elements aren't working as expected?
What features are confusing users?
When and where are users getting frustrated?

Where to Find the Replay

Once enabled, you'll see a replay button next to reported issues on your Marker.io dashboard. If your project is connected to an integration like Jira, you’ll also get a direct link to watch up to the last 2.5 minutes of activity before the issue was created.

How to Set Up Session Replay

Install Marker.io on Your Site
We recommend installing using one of our supported methods:
- JavaScript snippet
- NPM package
- CMS plugins
Enable Session Replay in Project Settings
Go to your project’s settings in Marker.io and navigate to Widget > Session Replay. Flip the switch to enable it.

Frequently Asked Questions (FAQ)

Does Session Replay cost extra?

Session Replay is included in the our custom plans. Contact us for details.

Will it slow down my website?

No, Session Replay runs quietly in the background, similar to tools like Google Analytics. It won’t affect your site’s performance. See here for more details on Marker.io and website speed.

Are there limits on how many sessions are recorded?

Up to 100 simultaneous visitors’ sessions.
Contact us for details if you need more capacity.

Note: During the free trial, you can track up to 500 simultaneous visitors.

What happens if no issue is reported?

If no issue is reported, the session data is automatically deleted within 15 minutes (up to a day in rare cases).

Can I control who sees the session recordings?

Yes, only members of your Marker.io account can view replays. You can manage permissions through user roles.

Does Session Replay capture everything on my site?

It can record most user actions, but there are some limitations. For example, content created with Canvas or WebGL won’t be captured. We’re working on a video screen recording feature to cover more content types.

What about sensitive information like passwords?

Passwords are automatically hidden. We’ve also developed a data masking feature that helps you hide other fields / values and assets. Check out the details here.

The session replay video isn't playing smoothly?

Here are two quick tips:

Close any apps or browser tabs you don’t need. This can help free up resources.
Make the video bigger by dragging the line below it downwards.

Check out this short video for a quick demo:

Why some dialogs might not appear in session replay?

In some cases, dialogs or modals on your website might not be visible in session replay videos. This is usually due to how and where these elements are rendered in the DOM, especially when they exist in environments that our replay tool can’t fully access.

Common reasons:

Closed Shadow DOM: If a dialog is rendered inside a closed Shadow DOM, it’s completely hidden from external tools like our replay engine.
Open Shadow DOM: Even open Shadow DOMs are not yet supported—content inside won’t be captured.
Unconventional rendering methods: Some dialogs use advanced rendering that can affect visibility, including:
- Canvas or WebGL: These render UI visually on the screen but outside the DOM, so our tool can’t capture them.
- Portals or framework-specific solutions: For example, Vue's Teleport moves dialogs to another DOM location. These are usually captured as long as they're not in a Shadow DOM.

How to make sure dialogs are visible?

To ensure your dialogs are captured in session replays:

Avoid rendering them inside Shadow DOMs.
If using advanced framework features (like Vue Teleport), make sure the destination element is part of the main document.

Coming soon: native `<dialog>` support

We’re actively working on full support for native <dialog> elements triggered with .showModal(). These render in the top layer of the page and will soon be reliably captured in replays.

New feature: visual screen recording

We are also developing a video recording feature that can be attached when reporting issues. This screen recording will capture all visible UI—regardless of how it is implemented in the DOM—including dialogs inside Shadow DOMs, canvas-rendered elements, and other complex renderings. Add your vote to the feature request here.