Noibu's primary purpose is issue tracking. When an issue is detected on your eCommerce website, Noibu collects as much data as possible, assigns the issue a descriptive title and Error Signature, and documents the issue on the Issues page. Here, you have access to a high-level look at overall issue impact on your eCommerce site, as well as the tools you need to prioritize, investigate, and resolve the issues.
Noibu tracks the customer's purchase journey through four main stages:
- On Site: /OnSiteDef
- Added to Cart: /AddedToCartDef
- Checkout Started: /CheckoutStartedDef
- Place Order: /PlaceOrderDef
For each stage, the Funnel Statistics view summarizes the number of unique sessions, and how many of those sessions were able to progress to the next stage, within a given timeframe. You can adjust the table to pull data over the past day, or the past 7, 14, 30, or 90 days.
The table also reports the Sessions Lost and Transactions Lost at each stage. These totals are calculated as follows:
Sessions Lost = Total Sessions X Drop in Conversion
Transactions Lost = Sessions Lost X Domain Average Conversion Rate for the remaining steps up to Checkout Started
Transactions Lost and Sessions Lost are only distinct values at the On Site and Add to Cart steps. At later steps, Transactions Lost accounts for organic drop-off due to errors experienced at earlier steps.
It's natural to have some drop-off at each stage of the purchase journey. However, by collecting data to calculate an average conversion rate, the Funnel Statistics view calculates how many sessions and transactions were lost due to issues on your website. It also calculates how much revenue you stand to lose at each stage if the issues go unaddressed.
Learn more about how Noibu calculates Annual Loss.
In Noibu, part of the triaging process is manually sorting issues based on Classification–Unset, Benign, or Pinned–so your engineers know where to focus their efforts. You should pin any issues known to be user impacting for easy reference, and as you can likely guess, the Pinned Issues tab collects and displays any issue in the Pinned category.
To keep things organized, the Pinned Issues tab will not include issues that are Closed-Fixed, Closed-Ignored and Benign, even if they're classified as Pinned.
Periodically, your Noibu CSM will pin visibly impactful issues to on your behalf, saving you the manual effort, but you're free to pin and unpin issues as necessary.
The Priority Issues view helps you focus your debugging efforts by identifying issues that are both revenue-impacting and resolvable. We recommend using the Priority Issues view as your primary view when triaging issues.
The Priority Issues view applies a set of nuanced filters to surface issues that meet a rich set of high-priority criteria. By default, this view will only show issues that meet the following criteria:
- The issue is tagged with the First Party, Stacktrace, Users Clicked, No Conversion, or Checkout Only insights.
- The issue occurs on the Checkout, Collection, or Product page types.
- The issue has ARL greater than or equal to the domain’s minimum revenue loss value.
- The issue’s state is Open, New, or In Progress.
- The issue was last seen within the past 14 days.
Additionally, issues that meet any of the following criteria will be filtered out:
- The issue is tagged with the Dormant insight.
- The issue’s classification is Benign.
The default filters are hidden behind the Filters toggle. To make adjustments or apply additional filters, click the Filters toggle to expand the list.
If you deviate from the default filters, a button will appear to reset the table to the default settings.
While the Priority Issues view helps you prioritize issues, the All Issues view lists all outstanding issues, and allows you to sort, filter, and search for issues of interest. By default, this view orders issues by creation date. The All Issues view is useful for retrieving a specific issue, or uncovering a subset of issues with similar characteristics.
Filtering & Sorting
You're free to filter the table of issues by any column. Any filtering or sorting will persist past your current session, so there's no need to reapply your filters with every session.
Each filter applied appears in the table's header. to remove a filter, click the X icon.
The available filters are:
- Urgency: Filter issues by urgency–Low, Medium, High, or Unprioritized.
- Assignee: Filter issues by assignee. Select a user or show unassigned issues.
- State: Filter issues by state–Open, In Progress, or Unset.
- Note: Closed-Fixed and Closed-Ignore issues are always exempt from Priority view, but you can pull issues of all states in All Issues view.
- Label: Filter the table to show issues with a specific label. You can apply multiple label filters to pull issues that meet multiple criteria.
- Operating System: Filter the table to show issues with >80% of occurrences on a given operating system.
- Browser: Filter the table to show issues with >80% of occurrences on a given browser.
- Insight: Filter the table to show issues with a specific insight. An insight is an attribute that describes the nature of the issue, like Has Stacktrace, No Conversion, or Invalid Coupon.
- Classification: Filter issues by the assigned impact–Pinned or Unset.
- Note: Benign issues are always exempt from Priority View, but you can pull issues of all states in All Issues view.
- Annual Revenue Loss: Filter issues by the annualized revenue loss. You can set a high and/or low limit. For example, you can apply a filter to show issues where Annual Revenue Loss > $10,000, or where Annual Revenue Loss is $10,000-$50,000.
- Leads Lost: Filter issues by number of leads lost. You can apply a high or low limit, or set a range. For example, you can apply a filter to show issues where Leads Lost > 1000, or where Leads Lost is 1000-10,000.
- Users Impacted: Filter issues by number of users impacted. You can apply a high or low limit, or set a range. For example, you can apply a filter to show issues where Users Impacted > 1000, or where Users Impacted is 1000-5000.
- Created At: Filter issues by creation date. Select a timezone, and set a timeframe to examine. For example, you can apply a filter to show issues created before July 19th at 9:00 AM, or issues created between July 19th at 9:00AM and July 20th at 9:00AM.
- Last Seen: Filter issues by the date and time it was last seen. Select a timezone, and set a timeframe to examine. For example, you can apply a filter to show issues last seen between July 19th at 9:00AM and July 20th at 9:00AM.
- Closed Fixed At: Filter issues by the Closed-Fixed date. This refers to the date on which an issue was moved to the Closed-Fixed state.
- Error Source: Filter the table to show errors with a specific origin. Learn more about Error Sources.
- Page Type: Filter the table to show errors that occur one one or more types of webpages. Learn more about Page Types.
- Analytics Period: Adjust the table to show issues with occurrences within a given analytics period. Options are the past day, 7 days, 14 days, 30 days, and 90 days.
How you manage your backlog of issues is up to you, and you have full control over how the Issues tables display data through the Column Configure menu. This allows you reorder columns to suit your prioritization flow, and even disable columns that you aren’t using regularly.
To change your table state, click Manage Columns to open the Column Configure menu. Here, you can drag-and-drop columns to put them in any order, or check/uncheck columns to show or hide them from the table. Rest assured that any change you make to the table state is reversable, so if a disabled column becomes relevant in the future, you can enable it at any time. Once you’re satisfied with the changes, click Save.
Users often notice issues with a similar root cause, or multiple issues isolated to the same workflow or page. Through the Labels column, you can tag an issue with one or more labels to group issues with similar properties. This makes it easier to apply filters to retrieve issues with specific characteristics.
There’s no limit to the number of labels you can apply to an issue. You can also create a new label from the table by clicking Add +.