Can I exclude specific pages from replays on the growth plan?

Hi James S., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋

Yes. Session Replay supports programmatic control over where you record, and this is not documented as being limited by plan type.On the web: - Initialize Session Replay normally, then call mixpanel.stop_session_recording() when the user is about to navigate to a page you want to exclude, and mixpanel.start_session_recording() when they leave that page to resume capture.[JS replay][Disable replay]On mobile (iOS/Android): - Use the SDK’s manual capture controls (startRecording / stopRecording) around sensitive or excluded screens.[iOS replay FAQ][Android capture]The docs do not mention any feature restriction on this for Growth vs other plans, so as long as Session Replay is available on your Growth plan (latest plan required), you can exclude specific pages/screens this way.[Session Replay plans]

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Yes—this is web/JavaScript, and you don’t put start_session_recording / stop_session_recording inside the standard mixpanel.init tag. You call them later from your own app logic, after Mixpanel has been initialized.From the docs, the flow is: 1. Initialize Mixpanel with Session Replay enabled (e.g. in your main JS, or via GTM/init tag): js mixpanel.init('<YOUR_PROJECT_TOKEN> ', { record_sessions_percent: 100 // or your sampling rate });LBKS

[JS replay]2. Around the pages you want to exclude, call the manual methods from your routing / navigation code: js // Before navigating to a page you want to EXCLUDE from replay: mixpanel.stop_session_recording();LBKS// When leaving that page and returning to allowed areas: mixpanel.start_session_recording();LBKS These manual calls are documented as separate SDK methods, used “when user is about to access the sensitive screen” and “once they leave this screen,” not as part of the init config itself.[JS replay; Disable replay]So: keep your standard Mixpanel tag / init as-is to enable replay, then add these start/stop calls in your page/router code (or equivalent) where you know the user is entering or leaving pages you want excluded.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

You can’t pre‑stop recording before a first page is loaded—the SDK and Session Replay only exist once your JS has been loaded and mixpanel.init has run. The docs only describe two controls for web: 1. Sampling / global enablement at init You decide whether a given browser session can be recorded at all, via record_sessions_percent in mixpanel.init: js mixpanel.init('<YOUR_PROJECT_TOKEN> ', { record_sessions_percent: 100 // or lower sampling });LBKS This is evaluated when the SDK initializes, not per‑URL. [JS replay capture]2. Manual start/stop once the SDK is running You can stop recording before navigating to a sensitive/restricted area, and start again when leaving it: js // before navigating to a restricted area: mixpanel.stop_session_recording();LBKS// when leaving it: mixpanel.start_session_recording();LBKS This is explicitly documented as “when user is about to access the sensitive screen” and “once they leave this screen.” [JS replay manual; Disable replay]Because the docs do not describe any URL‑based or path‑based exclusion for Session Replay (unlike Autocapture, which has block_url_regexes), there’s no documented way to “pre‑exclude” a landing page before the first load. [Autocapture options]So, based on current documentation: - You can avoid recording an entire session by adjusting record_sessions_percent. - You can stop recording before navigating to certain routes after the first page where Mixpanel is initialized. - There is no documented mechanism to say “never record URL X as a landing page” prior to Mixpanel being loaded on that page.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

Let me check the knowledge base for you again. One moment! 📚

Yes, a separate domain helps, because Session Replay only runs where the JS SDK is loaded and initialized with replay enabled.On the “excluded” domain, do one of the following: 1. Don’t enable Session Replay at all on that domainInitialize Mixpanel without replay options (no record_sessions_percent): js mixpanel.init('<YOUR_PROJECT_TOKEN> ');LBKSSince Session Replay is disabled by default and only runs when record_sessions_percent (or manual start) is used, no replays will be captured on that domain.[JS replay overview]2. Or, don’t load Mixpanel on that domainIf you can, omit the Mixpanel snippet / bundle entirely on the landing-page domain. Then there is no SDK, so nothing (including replays) can be captured on those pages.The docs do not describe any domain/URL-based exclusion inside the replay config itself (unlike Autocapture’s block_url_regexes), so separating by domain and simply not enabling replay (or not loading the SDK) there is the clean, documented approach.[Autocapture options; Replay init options]

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.