From 6dac5ffd873a56082170df499754a50d7ad9eb32 Mon Sep 17 00:00:00 2001 From: Donna <6880495+Tofufu@users.noreply.github.com> Date: Wed, 2 Oct 2024 11:37:38 -0700 Subject: [PATCH] Update session-replay-web.md (#1479) adding info about full page loads for session replay (web) Co-authored-by: Patrick Mackle --- pages/docs/session-replay/session-replay-web.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/pages/docs/session-replay/session-replay-web.md b/pages/docs/session-replay/session-replay-web.md index c611829a3e..9434acc416 100644 --- a/pages/docs/session-replay/session-replay-web.md +++ b/pages/docs/session-replay/session-replay-web.md @@ -272,6 +272,10 @@ How the SDK works on your site – the gist: We've tested the SDK extensively and it generally has minimal impact on how your website performs. The initial snapshot takes a bit of work, and naturally, more complex and interactive pages generate more data for rrweb and Mixpanel to handle. So, it's always a good practice to do some performance testing after you've implemented Session Replay, just to be sure everything's running smoothly. +### How do Session Replays work when navigating between pages that are full page loads? + +If your web application relies on full page loads (where the entire page is reloaded when navigating from one page to another), a new Session Replay recording `$mp_replay_id` will be created when navigating to each page. This occurs because the Mixpanel instance is reloaded again when navigating between pages. + ## Appendix: Session Replay Privacy Controls **Last updated July 30th, 2024**