Recording/Session Playback limitations
Currently session playback is recommended for landing pages or pages that don't contain a lot of dynamic content.
The current recording system is very well optimized, but has some limitations:
Interactions over or inside iframes are not recorded (browsers do not propagate events from iframes to the parent document)
Recorded pages content, versions or updates are not stored. This happens because userTrack only stores the URL of the recorded pages, this means that the page content is only loaded when the record is being played and it is always the latest/current version of the page at that URL.
As a consequences of the previous point: if a user has to log-in in order to access a specific area of the website you will not be able to view recordings on that area as long as you are not logged in as well. Also, if you are logged in as a different user you may see their actions done on your user panel.
Currently userTrack does not work well with web components and the shadow-DOM or frameworks that use those technologies (like Polymer). This happens because encapsulated elements do not correctly respond to external artificially triggered events (eg: click).
As all actions done by the user are actually replayed on your site, you should add the class UST_noClick on the HTML elements that lead to a final action (eg. finalizing an order), so that the click will be shown but the action will not be executed.
An alternative session playback system is being implemented that will be more accurate and have less limitations, but it will use more resources. The advantage of the current playback system is that it uses few resources and provides much higher user privacy as unique page content is not stored.
Because userTrack is self-hosted the maximum number of recordings stored depends on your server configuration, usually it is a good idea to limit the recordings to only store latest 50k-200k recordings on low-power servers. You can safely track around 30k-50k monthly sessions on a cheap $5/mo VPS. For more details see the server specifications guidelines.