How are the timestamps for sessions in a user card chosen?

After building a segment, you'll see a list of users that match the specific User and Event Filters that you are searching by. Depending on whether you are searching for these events "within the same session" or "across any number of sessions," the Session Playlist will link to any matching sessions (indicated by a circular play icon) or to a Fullstory clip (indicated by a clapperboard play icon).  

Screen_Shot_2022-07-08_at_12.28.39_PM.png

Each user in Fullstory is assigned a User Card, which is accessible by clicking on the user's Display Name. Here, you'll find information regarding the user such as when this user was first seen in Fullstory, the total number of sessions this user has, as well as any custom user variables that have been set via either FS.setUserVars or FS.identify

Screen_Shot_2022-07-08_at_12.30.52_PM.png

On the User Card, you'll notice that there are two tabs. One for "Matching Sessions" (or, when relevant, "Matching Clips") and another for "All Sessions." It's important to note the difference between the timestamps displayed for each of these tabs.

  • For the "Matching Sessions" or "Matching Clips" tabs, the timestamp displayed will be based on the last matching event that was indexed within that session, based on your current search segment. For example, if you are searching for sessions where users visited your homepage, this timestamp would reflect the last navigation event where they visited your homepage within that session.
  • For the "All Sessions" tab, the timestamp displayed will be based on the last event indexed within that session, regardless of whether that event matched any of the Event Filters used in your current search segment. Circling back to the previous example, this timestamp would reflect the last event indexed within the session, even if this event wasn't a navigation event for your homepage.

 


Was this article helpful?

Got Questions?

Get in touch with a Fullstory rep, ask the community or check out our developer documentation.