Having trouble with recordings? Below are some tips for getting past some common issues
Recordings are not being captured
There are a few common reasons that you may not see recordings appear in your project.
1. Authorized domains for recordings
In your project settings page, there's a section for 'Authorized URLs'. This is the list of domains where posthog will capture recordings. You should make sure it's not too restrictive.
For example, you may have https://www.example.com in the list. This will stop PostHog from capturing recordings on https://example.com.
If no domains are set here, PostHog will capture recordings on all domains.
2. posthog-js configurations
If you had previously disabled session recordings, you may have set the disable_session_recording option to true in posthog-js.
To re-enable session recordings you want to either remove the disable_session_recording option or set it to false.
You can read more about posthog-js configurations here.
3. Content security policy
When recordings are enabled, postHog-js will fetch a recorder.js script from the PostHog server. (This is not included in the default posthog-js to minimize the default bundle size)
Depending on your content security policy, this script may be blocked. If you have a default-src, script-src, script-src-elem, or connect-src directive in your CSP, you may need to add https://app.posthog.com (or your host URL if you are self hosted) to your list.
If PostHog is being blocked by your content security policy, you should see an error message in your developer console with more details.
4. Ad/tracking blockers
Some ad/tracking blockers will block PostHog from fetching posthog-js. If you're testing your app locally, you may need to disable any ad/tracking blockers that you're running in your browser.
Replay of recording looks incorrect or buggy
If you're having issues with recordings not looking correct, there are a few things you can:
1. Enable the V2 Recorder
From the recordings tab in PostHog, open the Configuration and enable the "V2" recorder. We are slowly rolling this out to everyone as it fixes a lot of issues regarding things like ShadowDOM elements and more. For some web frameworks the results are immediately much better.
2. Ensure your website permits PostHog CORS
Most assets rendered on your website or app are captured inline – meaning we keep a copy of the icon, css etc. to use when replaying. For some assets however, this is either too difficult or too costly to do, so instead we load them directly from the original webserver (just like your website does). This can lead to CORS issues where the webserver does not permit app.posthog.com (or eu.posthog.com) to load the required asset. Unfortunately we cannot easily detect when this happens, but the browsers's developer tools (Option + ⌘ + J, or Shift + CTRL + J) will log when these errors occur saying something like:
If you see errors like this, please add app.posthog.com to the list of permitted domains in your webservers CORS configuration.
Update posthog-js
We're always making improvements to the recordings feature, so you'll want to make sure that you're running the latest version of posthog-js on your website.
To check the version that you're using, you can run the following in your console:
Browser freezes or crashes when recordings are enabled
Some Cookie banners or "CMP"s modify the webpage in reaction to any changes to cookies, which can cause an infinite loop. If you are using a tool like this and experience the webpage becoming unresponsive or slow then try configuring posthog to use persistence: "localStorage+cookie". This will use localStorage for the majority of storage needs, bypassing the infinite loop issue sometimes caused by cookie management tools.
Recorder Limitations
Due to the complexity of browser rendering and replay, some web resources are unable to be recordered or playedback. These include:
- Canvas - Technically this is currently recordable but playback is not possible without introducing security issues. This issue tracks the progress if this could change in the future.
- WebGL
- Object elements - Most object elements cannot be played back. Non-HTML native plugins such as Flash or Silverlight cannot be recorded
- Heavy animations - Some heavier animations such as SVG or Lottie animations may be throttled or ignored entirely due to the performance overhead in recording and replaying
- Iframes - iframes from the origins under your control can be recorded and played back. See iframe recording for more info.
Report your specific issue
To report a specific problem, you can open a GitHub issue. To help us figure it out as quickly as possible, please include the following information:
- The URL of the page that you're trying to record
- The version of posthog that you're using
- The version of posthog-js that you're using
- Details about the specific issue with your recording (e.g. how it looks and how it should look)
- If you're on posthog-cloud, a link to the specific recording
- Any unique details about your website (e.g. the frameworks that you're using etc.)