Fixing Broken Sessions
If you've recently updated your CSS files, this may impact how session replays appear, potentially making them look broken. Since Userback doesn’t store complete copies of CSS files, images, or videos, any changes to these assets can cause issues if they’re no longer accessible when loading a replay.
To avoid this, we recommend keeping your CSS files accessible for at least a few months. This ensures that session replays remain accurate while you’re actively reviewing and responding to feedback.
⚠️ If your site uses 3D Canvas or WebGL, please note that these elements are currently incompatible with our session replays and won’t be visible within the recorded sessions.
Fixing Missing Sessions
Ensure Your Domain is Enabled: Confirm the correct domain is active in your settings.
Check for Errors in Your Logs: Look for error messages that might indicate why sessions aren’t recording.
Common Errors
CSP Error: To fix CSP (Content Security Policy) issues, you'll need to whitelist our Session Replay URL: https://events.userback.io.
CORS Error: If CSS files aren’t loading properly due to a CORS (Cross-Origin Resource Sharing) issue, you'll need to adjust the CORS rules on your end to allow the CSS file to be loaded in our app.
Need More Help?
If you've tried the above steps and still face issues, or if you have more questions, feel free to reach out. We're here to help!