Hi,
There are several reasons why Session Replay is not captured for every user, and what you describe (VPN users, cookie blocking, external clients) fits the typical root causes. Session Replay recording requires multiple technical conditions to be fulfilled in the browser, and when even one of them fails, the replay won’t start.
1. If the browser blocks cookies, scripts, or uses aggressive privacy settings (Safari ITP, Brave, some VPN proxies), the RUM JavaScript may not load correctly.
To verify:
Check that both JS agents load in Network tab:
ruxitagentjs_*Q*.js
ruxitagentjs_*D*.js
Ensure the script isn’t replaced with an empty payload (some proxies do this).
2. Session Replay beacons blocked
Session Replay uses binary POST beacons (rb_bf) with Content-Type: application/octet-stream.
Many systems block these:
- WAFs
- Firewalls
- Proxies
- VPN gateways
- Load balancers
If the beacon can’t be sent (or returns non-200), the replay never gets uploaded.
3. Client browser limitations.
I mean several technologies prevent recording
4. IFrame restrictions
If an IFrame doesn’t have the RUM script injected, replay will be incomplete or not recorded at all.
5. Network / performance limits
Session Replay sends ~100 KB per minute of binary data.
Here you have some community/documentation links:
Session-replay-restrictions-web
When session is not recorded, what we should check on the browser?
Problem with sessions, not all sessions are being recorded in Dynatrace