How to Enable Session Replays in Rudderstack Destination Configuration?

·Mar 26, 2026 04:52 PM·

Hi! I'm terribly confused about how to turn on Session Replays when I'm using Rudderstack- is that something I set up in my Rudderstack destination config? Is there documentation on how to do that?

🎫

1

2 comments

· Sorted by Oldest

Zach Reid
APP
·
·
Hi Kara 👋 Zach here from Mixpanel Support! Mixpanel Session Replay is not configured in your RudderStack destination settings. It's set up at the code level, with RudderStack and the Mixpanel JS SDK running side by side. Steps to set it up 1. Install and init the Mixpanel JS SDK with Session Replay enabled. We recommend starting with a 100% sample rate so you can monitor performance and make sure your privacy rules align with your policies before dialing it back. 2. Add the RudderStack middleware You can add middleware to RudderStack's SDK that pulls the anonymousId from RudderStack, passes it to Mixpanel as the device_id, and injects the session replay properties ($mp_replay_id) into every event call. 3. **Handle identity **You'll want to make sure identify calls are also passed through to Mixpanel so user identity is consistent between the two SDKs. If you have any questions specific to your project or implementation then I can move this to a Support ticket and we can follow up there 🙂
🙌1
Kara F.
·
·
Got it- thank you!

Zach Reid
APP
·
·
Hi Kara 👋 Zach here from Mixpanel Support! Mixpanel Session Replay is not configured in your RudderStack destination settings. It's set up at the code level, with RudderStack and the Mixpanel JS SDK running side by side. Steps to set it up 1. Install and init the Mixpanel JS SDK with Session Replay enabled. We recommend starting with a 100% sample rate so you can monitor performance and make sure your privacy rules align with your policies before dialing it back. 2. Add the RudderStack middleware You can add middleware to RudderStack's SDK that pulls the anonymousId from RudderStack, passes it to Mixpanel as the device_id, and injects the session replay properties ($mp_replay_id) into every event call. 3. **Handle identity **You'll want to make sure identify calls are also passed through to Mixpanel so user identity is consistent between the two SDKs. If you have any questions specific to your project or implementation then I can move this to a Support ticket and we can follow up there 🙂
🙌1
Kara F.
·
·
Got it- thank you!