Requirements and restrictions for Session Replay 2.0 β
- Support for the outdated code snippet
- By default, Yandex.Metrica uses a new code snippet for the tag. To use Webvisor 2.0, replace the old snippet with the new one on all of your site's pages. You can find it on the Settings page. If the site has the old snippet installed and you want to use Session Replay 1.0, select the Obsolete code snippet option.
- Limit on period for storing recordings
- Data is stored for 15 days, including the current day.
- Limit on number of recordings per day
- Session Replay records up to 150,000 sessions a day with a margin of error. The system provides a representative sample by recording a spread of sessions throughout the day.
- Using Session Replay 2.0 if the site has multiple tags
- In this case, enable Session Replay 2.0 on just one of the installed tags. If Session Replay 2.0 is enabled for all the tags, the data will be recorded by the tag that initializes first on the site.
- Recommended site encoding
- Session Replay records user actions correctly if UTF-8 encoding is used on the site.
- Valid HTML layout on pages
- If there are a large number of HTML markup errors (unclosed tags, incorrect nestings, etc.), this may lead to inaccuracies in session replays. Session Replay usually adapts to such errors, but having correct HTML structure on site pages is preferable.
- Recording pages with flexible layout
- Sessions on pages with flexible layouts will be replayed correctly, even if the resolution of the user’s screen is not the same as the replay screen. During playback, you might see small cursor jumps due to different relative positioning of elements on the recorded and replayed pages.
- Using Session Replay 2.0 for frequently updated CSS files
If your site frequently updates CSS, add the content hash to the style file names. Then, when you change the file's content, its name will change. For example: style.390b32d4d49d5e7d.css will be changed to style.0c573d460df87d4de5a4.css. This lets Session Replay use the style that the site visitor sees when it records a session.
- Canvas support
- Session Replay doesn't record site content if it is displayed using the canvas element.
- Recording video and audio content
- Session Replay doesn't record the content of HTML audio and video elements or how the user interacts with them if the Audio and Video objects are modified inside these elements.
- Recording Flash content
- Session Replay records Flash content on the site, but it doesn't play back the user's interaction with this content.
- Support for Shadow DOM
Session Replay supports Shadow DOM technologies.
- Browser support
Session Replay supports session recordings for most modern desktop browsers, including Yandex Browser, Google Chrome, Firefox, Safari, Opera, and Microsoft Edge. There is limited support for recording in beta versions and in certain mobile browsers. There is also limited support for session recording and playback in Internet Explorer (any version).
Different browsers may process the same page in different ways. This means that to accurately replay a session, you should use the same browser as it was originally recorded in.
- Processing styles
If the site uses runtime styles (including from the Data Styled Components series), Session Replay does not record sessions or records them incorrectly. We recommend using classic styles.
- Processing WebP media files
Session Replay does not have the ability to process media files in the WebP format.
- Recording browser tabs in private browsing mode
- Session Replay may incorrectly record information about tabs in private browsing mode (for example, Incognito in Yandex Browser).
- Recording pages with layout errors
- Session Replay may inaccurately record sessions on pages with a layout that does not meet W3C standards.
- Recording iframe contents from another domain
- For Session Replay to record iframe contents where the address differs from the site address, configure the tag in a special way.
- Processing media requests
- Yandex.Metrica may incorrectly process certain media requests.