From c68abb2b27c81b8c8891f7cb8c9365766cc4cdae Mon Sep 17 00:00:00 2001 From: no value <163026311+dhaval-valotia@users.noreply.github.com> Date: Wed, 15 Jul 2026 18:07:30 +0000 Subject: [PATCH] Add note for SR CRW --- docs/session-replay.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/session-replay.mdx b/docs/session-replay.mdx index dbf96552..6ce570ba 100644 --- a/docs/session-replay.mdx +++ b/docs/session-replay.mdx @@ -297,6 +297,10 @@ On our mobile SDKs (iOS, Android, and React Native), you control capture with a By default, replays are stored for 30 days after the time of ingestion. Once a replay is expired, there is no way to view that replay. Enterprise plan customers with the paid session replay add-on can customize this retention period between 7 days and 360 days. For more information, reach out to your Account Manager or our sales team. + + Purchasing a custom retention period does not change your retention period automatically. Once the entitlement is provisioned, an org Owner or Admin needs to set the desired retention period from the Session Replay settings in the UI. + + #### Why does it say the player failed to load? To maintain a high level of security, Mixpanel runs your session replays in an isolated domain through an iframe. Occasionally, this domain may be blocked by an ad blocker or specific browser settings. We recommend disabling any ad blockers, or whitelisting the Mixpanel domain.