Each page or screen within a FullStory session gets its page/screen start time from FullStory data capture servers. Because these start times originate from the data capture servers, all FullStory sessions will be in sync, regardless of potential time variability in end users' devices. FullStory data capture servers use Google Compute Engine instances, which in turn are synchronized using Network Time Protocol (NTP) to ensure consistency across all server side nodes. This ensures that all sessions should semantically flow in the actual order that they were captured.
After page/screen capture begins, all raw events captured on the client side within the end user's browser or mobile app are captured with a relative timestamp offset from the start of capture. This relative timestamp is then later applied to the server captured start time mentioned above to render the final time value displayed when watching a FullStory session.
Switching to absolute time
You can switch between the relative and absolute time during during session playback by clicking on the the timestamp at the bottom. The timestamps displayed within FullStory's UI will always be based on your computer, device or browser time, not the customer's timezone.
