Some environments block direct access to third-party analytics and monitoring domains like rec.sessionrewind.com or api.sessionrewind.com. This can happen due to:

To ensure Session Rewind works reliably in such environments, you can proxy traffic through your own domain. This causes Session Rewind’s analytics to be treated the same as first-party traffic.

These are the required steps:

  1. Proxying the script loader.
  2. Proxy the recording data endpoints.

1. Proxy the Scripts (CDN‐like Traffic)

What to Proxy

All GET requests that would normally go to https://rec.sessionrewind.com/* should be routed through your proxy.

Suppose your domain is example.com, and you decide to proxy the loader scripts via https://sr-cdn-proxy.example.com/*

Those requests should get forwarded internally to the SessionRewind loader endpoint at https://rec.sessionrewind.com/*

Updating the Script Reference

You need to update your HTML to load srloader.js through your newly proxied URL instead of the default domain. For example: