Session Recording
There are two distinct session recording systems that you can choose from:
You can select the tracking system for each page when the tracker is installed, by including either the default tracker or the full session tracker (ust.min.js vs ust-rr.min.js). The two recording systems can be used at the same time on different pages: a session playback can work even if some pages are recorded with one system and others with the other system.

A. Default page recording

Lightweight, very efficient tracking system that only stores the URL of the visited page and the actions taken by the users.
This system is best used for recording static pages. When viewing the recording, the current content of the page will be loaded based on the URL.
The biggest drawbacks of this method are:
  1. 1.
    It doesn't work well with dynamic content or behind login-protected pages (as the page is loaded in your browser based only on the URL)
  2. 2.
    The tracked website must be shown in an iframe when viewing the recording.
  3. 3.
    Actions are actually executed again when viewing a recording.
The default session recording system uses around 1MB / 100 recordings.

B. Full page recording

Accurate tracking that records the page content (HTML) and all changes and actions that happen on the page.
Note: This system has been added since version 4.0.0
This system should be used for recording highly dynamic pages, dashboards or pages where the same URL can show different content.
The biggest drawback is that the size of each recording and the data sent from the user to your server is larger.
Use this with caution!
The full recording system uses around 1MB per page recorded!!
In order to keep the database size small, you might want to regularly delete old recordings.
โ€‹
Last modified 1mo ago