Why do some parts of my store appear differently in the replay?
Instead of recording a video of a shopper on your site (which would take a ton of bandwidth / slow down your site considerably), Propel Replays uses a third-party recording library to copy your website code and any subsequent changes made to it.
When you view a replay, you're actually viewing a mini copy of your site. Propel Replays plays back changes made to your website code to reflect what the shopper experienced.
This method is very lightweight, and doesn't slow down sites as much as video would, but there are limitations to this method:
- Some CSS and HTML elements may not be fully supported by the third-party recording library used by Propel Replays and so may not display properly in replays (e.g., some CSS animations.)
- In-app browsers used by Meta, TikTok, Facebook, etc have restrictions and limitations that may impact recording accuracy.
- Due to browser security restrictions, Propel Replays cannot record content that appears in an "iframe" (a special HTML element that allows loading of another website's content inside of a website - review apps often use iframes. )
- For videos, Propel Replays can record the frame and background of the video (which can include an error message about needing to enable Javascript), but not the video itself.
- For images not loading, Propel Replays doesn't record the image itself but instead the URL to the image. If the URL to images changes in between when the recording was taken and when the replay was viewed, the images in our replay won't load even though they loaded for the shopper.