Session Search

 

 

The session search feature helps you search for a specific user session and understand everything they did along the way and which errors may have impeded their journey. This feature is particularly useful to link customer support tickets to real user sessions to understand what happened to the user and have more information to help prevent other users from experiencing the issue in the future.

You can search for a session using the following data.

 

The more data you have the more narrow your search will be:

 

Step 1: Date: choose the time, date, and time zone that will intercept the customers session. For example if you select 20/05/2020 @09:00 and 20/05/2020 @09:30, this will pull up all user sessions that intersected that time. For example a session that started at 08:30 and ended at 09:01 would be matched to that search criteria.

 

Screen_Shot_2021-02-16_at_5.18.07_PM.png

 

 

Step 2: Adding other Filters:

Screen_Shot_2021-02-16_at_5.17.59_PM.png

Browser ID: This is Noibu specific. See if someone with a certain browser ID came back to make their purchase

 

IP Address: Do you have a chat feature on your website that collects IP Address? Use that to find a session.

 

Issue ID: this allows you to search for specific sessions within a Noibu Issue ID.

 

OS: choose the operating system that the user was on at the time of the issue.

 

Browser: Chrome, Safari, Firefox?

 

User Clicks: any item that the user may have clicked along their journey, for example, add to cart.

 

Last Repro Step: the last reproduction step that a user took before bouncing, for example, place order.

URL: which url they struggled on. For example, if you type "checkout" that will pull up any url that had checkout in it.

 

Min Page Count: # of page visits that the customer took.

 

Min Error Count: # of errors that the customer encountered. Recommend leaving this at 0 because sometimes customers experience a non-technical issues and it's still useful to view their session.

 

Issue ID: this allows you to search for specific sessions within a Noibu Issue ID.

 

Last Repro Step: the last reproduction step that a user took before bouncing, for example, place order.

 

User Clicks: any item that the user may have clicked along their journey, for example, add to cart.

 

Boom! That's it. Once you have found the customer's session, you can implement your regular Noibu investigation process, find bugs, assign them to your team, and get them fixed. 

 

Make customers happier, one filter at a time and one bug-squash at a time! Only with Noibu.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.