Fixing Asterisk Issues in Session Recordings for Accurate Page Details
With session recordings, all of the on page details are asterisks and not the actual page details. How do we fix that
With session recordings, all of the on page details are asterisks and not the actual page details. How do we fix that
Hi Golibe O., 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> đ
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
To address the issue of all on-page details appearing as asterisks in session recordings, you'll need to adjust the default masking settings in Mixpanel's Session Replay. By default, Mixpanel masks all non-input text on your webpage for privacy reasons. Here's how you can fix this:1. Change the default masking behavior:
To unmask all non-input text, you need to modify the record_mask_text_selector setting.
```LBKSLBKS This changes the default value from "*" (which masks all text) to an empty string, making all text elements no longer masked.LBKS2. Selectively mask sensitive elements:
After unmasking all text, you can then choose to mask specific sensitive elements individually using CSS selectors or by adding the class name ".mp-mask" to elements you want to mask.LBKS
html
kapa.ai is still learning and improving, please let me know how I did by reacting below.
âšī¸Â 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, there is a way to adjust the recording rate for specific events in Mixpanel's Session Replay. While the default setting is to record 1% of all sessions, you can implement a more targeted approach to capture 100% of certain events while maintaining a lower rate for others. Here's how you can achieve this:1. First, set the default recording rate to a low percentage (e.g., 1%) during SDK initialization:LBKSmixpanel.init("<YOUR_PROJECT_TOKEN> ", { record_sessions_percent: 1 // records 1% of all sessions by default })LBKS2. Then, you can use the Session Replay Methods provided by Mixpanel to start and stop recording programmatically based on specific conditions or events. Here's an example of how you might implement this:LBKS// For events you want to record 100% of the time if (specificEventOccurs) { mixpanel.start_session_recording() }LBKS// When the specific event interaction is complete mixpanel.stop_session_recording()LBKSThis approach allows you to have full control over when to start and stop recording, enabling you to capture 100% of specific events while maintaining a lower overall recording rate.It's important to note that this method requires you to implement the logic in your application code to determine when to start and stop recording based on your specific criteria.For more details on these methods and implementation examples, you can refer to the Session Replay Methods documentation.Remember to consider privacy implications and ensure compliance with data protection regulations when implementing this approach. Also, be mindful of the potential impact on your session replay quota and storage.Mixpanel SDKs: Javascript
kapa.ai is still learning and improving, please let me know how I did by reacting below.
âšī¸Â 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, you're correct in wanting to clarify this important point. When you use the targeted approach with mixpanel.start_session_recording(), it will indeed record the entire session from that point forward, not just the particular event that triggered the recording.Here's how it works:1. When you call mixpanel.start_session_recording(), it begins recording the session from that moment.
2. The recording will continue until either:
- You explicitly call mixpanel.stop_session_recording(), or
- The user's session naturally ends (e.g., they close the browser or leave the site)This means that once you start the recording based on a specific event, you'll capture all subsequent user interactions and page changes until the session ends or you manually stop it.For example, if you implement something like this:LBKSif (userPerformsImportantAction) { mixpanel.start_session_recording() }LBKSThe recording will start when the important action occurs and will continue to record the entire user journey from that point onward.This approach allows you to capture the full context of the user's actions after the important event, which can be incredibly valuable for understanding user behavior and troubleshooting issues.Remember to manage your recording quota carefully with this approach, as longer sessions will consume more of your allotted storage.For more details on how to implement and manage session recordings, you can refer to the Session Replay Methods documentation.Mixpanel SDKs: Javascript
kapa.ai is still learning and improving, please let me know how I did by reacting below.
âšī¸Â Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.