Looking for session by dfullStoryId

• 

  Lindsay Zubrickas

  August 14, 2023 16:52

  Hey @Lior.kooznits! Thanks so much for your question! 😊

  It’s my understanding you may be searching for user sessions using information from data export. You are correct in that the format of session URLs did change. If you are looking to build a session url programmatically from your exports, you also need the session id from the export.

  You can use this format to locate the session:

  https://app.staging.fullstory.com/ui/thefullstory.com/session/user_id:session_id

  Please let me know if you have any more questions! If this is not what you’re looking to do, please reply with a bit more information about your use case as I’d be happy to work with you to find a solution! 

   

  0
• 

  lior.kooznits

  August 22, 2023 11:08

  Thanks for answering.

  I was trying to follow your suggestion. indeed, I‘m trying to programticly build a URL based on a fullstory id exported into our company logs.

  I’ve tried to follow your suggestion but couldn’t build the appropriate URL. it will. 

  I’ll try to give you a real-life example and if possible, can you advise how it should be formatted?

   

  A URL copied from our company fullstory account: https://app.fullstory.com/ui/W1MPQ/session/8522575381381083001:8522575381381083001!2226405805421615497

   

  A real fullStoryid stored in our logs:

  #W1MPQ#16840382-d3e7-4a00-8413-f83575fa9000:a1c90f7b-1f5e-4edd-a6c0-9ad16b50eff0:1692691209537::2#/1693849285

   

  How can I amend the URL (based on the fullStoryId) so I would be able to load the session? as mentioned? 

   

  0
• 

  Lindsay Zubrickas

  August 22, 2023 22:49

  Hey @Lior.kooznits! Thanks so much for reaching out and providing that example!

  I’m happy show you how to format this:

  When looking at a session's URL while watching it in FullStory, you'll see a pattern that looks like this:
  https://app.fullstory.com/ui/<ORG_ID>/session/<FS_INTERNAL_USER_ID>:<SESSION_ID>!<PAGE_ID>

  As an example: https://app.fullstory.com/ui/W1MPQ/session/5620933053812736:6755569665295052784

  However, the values provided in the browser at the time a session is captured are slightly different.

  Let's take the value you provided from your logs. This is the contents of our `fs_uid` cookie. The cookie's pattern looks like this:
  #<ORG_ID>#<FS_INTERNAL_USER_ID>:<SESSION_ID>:...rest

  As an example:
  #W1MPQ#16840382-d3e7-4a00-8413-f83575fa9000:a1c90f7b-1f5e-4edd-a6c0-9ad16b50eff0:1692691209537::2#/1693849285

  As you can see though, the values in the cookie no longer match the values in the corresponding session URL where those IDs are numeric. In fact, if you call FS.getCurrentSessionURL() from your browser while you are capturing a session, you would get a URL that looks like this (based off the cookie above):
  https://app.fullstory.com/ui/W1MPQ/client-session/16840382-d3e7-4a00-8413-f83575fa9000:a1c90f7b-1f5e-4edd-a6c0-9ad16b50eff0

  There is one key difference to point out: The URLs with the hashed IDs use the path `/client-session/` whereas the numeric IDs rely on the `/session/` path. You'll also note that visiting the hashed version redirects to the numeric.

  So to summarize, if you're using cookie values like this:
  #W1MPQ#16840382-d3e7-4a00-8413-f83575fa9000:a1c90f7b-1f5e-4edd-a6c0-9ad16b50eff0:1692691209537::2#/1693849285
  Then you'll need to create the URL so that it looks like this:
  https://app.fullstory.com/ui/W1MPQ/client-session/16840382-d3e7-4a00-8413-f83575fa9000:a1c90f7b-1f5e-4edd-a6c0-9ad16b50eff0
  And once you visit the session, you'll be redirected to a session with this URL:
  https://app.fullstory.com/ui/W1MPQ/session/5620933053812736:6755569665295052784

   

  I hope this helps! If you have any other questions, please don’t hesitate to let me know!

  0

Please sign in to leave a comment.