Here is a step by step guide on how Noibu works. Noibu dashboard is your go to assistant to detect, monitor, prioritize and fix critical ecommerce errors. Noibu also integrates seamlessly into your existing workflow by sending you instant + weekly reports via email:
Instant: Anytime a high priority issue occurs, you will be notified.
Weekly: All low, medium, high priority issues for the previous week are send in a weekly report which contains a weekly summary plus detail on every error so that you can prioritize and decide what errors need immediate attention.
The instant and weekly reports come in similar format with an email summary and attached error report that points to the dashboard. Here is the breakdown of the Noibu reporting system and how to use it:
The email summary provides you with a quick glance of your errors from the previous week. In this summary you can see the total number of errors, revenue impact, and high priority vs low priority errors.
In the email summary is link which contains your error report. Click the link to access your report directly.
Once you've opened up the report in your browser, the first thing that you see is the error summary. The error summary is the part of the report that you as an ecommerce professional can use to make decisions on prioritization and actioning of errors. The summary is designed to give you a quick glance at each error and highlight the important information needed to prioritize and action an error.
Each error is equipped with the following information:
-ID: Unique Error ID for each individual error
-Name: Unique Error Name for each individual error
-Times: # of times the error occurred for this week
-# Times Last Week: # of times the error occurred last week
-Weekly Revenue: An estimated revenue impact per error for the week
-# of Users: # of users affected by the specific error
Each unique error is equipped with error tags that you can use to prioritize errors that are occurring on your website. The tags are designed to be actionable for an ecommerce professional with limited technical knowledge. The error tags are as follows:
Severity: High, Medium, Low to help you prioritize what should be fixed first.
New: Indicating new errors from last week.
Checkout: Indicating an error related to the checkout process.
Cart: Indicating an error related to cart system.
Serverfail: Indicating a failure of the server for all or some users.
Brokenlink: Indicating a broken url.
Coupon: Indicating an error while entering a coupon.
UI: A user interface error that can result in broken experiences for customers.
UX: A user experience error that can result in broken experiences for customers.
Ratelimit: Server is blocking certain users from accessing all or certain components of the website.
Adblock: Indicating an error related to an ad blocker.
Analytics: Indicating an error related to an analytics software plugin.
Flowio: Indicating an error with flow.io plugin.
GTM: Indicating an error with Google Tag Manager.
Plugin: Indicating an error with a plugin.
DevTools: Indicating an error with developer tools such as Rollbar.
Social Media: Indicating an error with a social media integration.
Multibrowser: Indicating the error happened on multiple browsers.
Multidevice: Indicating that the error happened on multiple devices.
Hover over each tag to get more information. See below:
Each error is equipped with a developer packet that you can use to get more detailed information about each error and send to your developer so that the error can be fixed. To access the developer pack click on the error name.
The top portion of the developer packet contains the following data:
Name: Name of the error.
Unique Error Signature: Unique error identifier.
First Detected: Day the error was first detected.
Weekly Revenue Impact: The weekly revenue impact of this unique error
Error Code: 400 codes, 500 codes, etc.
Occurrences: # of unique occurrences this week.
Users Impacted: # of unique users impacted by the error.
The middle portion of the developer packet contains the insight information. Insights help with understanding the type of error (checkout, cart, serverfail, etc.), browser data, and device data.
The bottom portion of the developer packet contains sample raw data from real users experiencing this issue. The raw data includes:
Timestamp: Precise time when the user experienced the unique error.
On Url: The specific url that the unique error occurred on.
Error Url: The error url that the user generated with the unique error.
Referring Url: The url that the user visited prior to the error occurring.
Err Code: Error code of the unique error.
User Agent: Browser + device of the user that experienced the unique error.
Client IP: Unique IP of the user that experienced the unique error.