Filtering the list of Sessions can help you find a specific user session or a subset of sessions that demonstrate evidence of an error impacting a user. Clicking the Filters toggle will show the Add Filters button.
Session recordings can be filtered on any of the following:
| Field | Description |
| Date & Time | The time and date range in which a session occurred |
| Browser ID | This is a Noibu-specific feature, and can be useful for tracking multiple sessions by the same user. For example, a user who encountered an error that prevented them from checking out might come back after a few days to try again. |
| IP Address | A user's IP address. |
| Issue ID |
Sessions that include a specific Noibu Issue ID. Visit the Issues page to retrieve an Issue ID. |
| Help Code | A six-digit code provided by a shopper to identify their session. Learn more about Help Codes. |
| OS | Operating system: Android, iPhone, MacOS/iPad, or Windows. |
| Browser | Sessions on a specific browser: Safari, Chrome, Firefox, Internet Explorer, Edge, or Webview. |
| User Clicks | Sessions where a user clicked on a specific button. For example, Add to Cart. |
| CSS Class | Sessions where a user interacted with a specific CSS class. For example: button-checkout, lock-smith, css-pretty. |
| Last Repo Step | The last step a user took before an encountering the error. For example, Place Order. |
| URL | The URL path where the user encountered the problem. For example, enter "checkout" to pull up sessions that include any URL that includes "checkout." |
| Min Page Count | Sessions that include a minimum number of distinct pages visited. Options are 3, 5, and 10. |
| Min Error Count | Sessions that include a minimum number of errors. We recommend leaving this at 0; sometimes customers experience issues that don't involve technical errors, like bad UX design. These sessions are still worth viewing to improve the customer experience. |
| Session Symptom | Sessions that include a specific session symptom. |
| Web Vitals | Web vitals represent elements of the user experience in a session that can be measured, quantified, and rated on a three point scale: Good, Needs Improvement, or Poor. Learn more about Web Vitals. |
| Last Funnel Step | Sessions that end after a specific funnel step. These options align with the high-level stages of the purchase journey as outlined in the Funnel Statistics section: On Site, Added to Cart, Checkout Started, Place Order, and Checkout Completed. |
| Contains Funnel Step | Sessions that contain a specific funnel step. These options align with the high-level stages of the purchase journey as outlined in the Funnel Statistics section: On Site, Added to Cart, Checkout Started, Place Order, and Checkout Completed. |
| Custom ID Name | Sessions that contain a custom ID entered via the NoibuJS SDK. This filter must be an exact match to pull up relevant sessions. |
| Custom ID Value | Sessions that contain a custom ID value entered via the NoibuJS SDK. This filter accommodates both exact and partial matches, which allows you to pull a specific value or a range of similar values. |
Example Use-Cases
Finding Sessions at a specific date and time
If you're diagnosing an error that occurred at a specific time, filter the list of sessions by selecting a specific time zone and a start and end time.
- For example, if a customer reports an error encountered on Tuesday at 9:15 AM PST, filter by the customer's time zone, set the start time to Tuesday at 9:10 AM and the end time to Tuesday at 9:20 AM. This should retrieve results that include the customer's session.
Finding evidence of web performance issues
If you're diagnosing web performance trends uncovered through our performance monitoring features, you can filter by page URL and associated web vital to find examples of customer sessions that may have been impacted by the performance issue.
- For example, you might filter to “URL contains outerwear“ and “CLS = poor“ within a given date range to find a list of session recordings that show how a low CLS score impacted your customer.