After Deploying the Noibu Script to collect error data on your eCommerce site, you'll have access to a shiny new Noibu platform. There's a lot to do here, so we've assembled a list of tasks to complete within your first week with Noibu. An onboarding rep will be available to walk you through many of these tasks, but the sooner you get your Noibu platform set up, the sooner you can start resolving errors and preventing revenue loss.
1. Confirm Domain Information
One of Noibu's essential functions is to calculate the Annualized Revenue Loss of each error on your eCommerce site. /ARLdef This calculation depends on an Average Shopping Cart Value, which you must configure manually in your domain's profile. Your Noibu platform may track data across multiple domains, and you must configure each domain's settings separately.
- Visit the Domains tab and configure each domain's settings. The most crucial settings are:
- Average Shopping Cart Value: Configure the value of an average purchase on the domain. Noibu uses this figure to calculate Annualized Revenue Loss.
- Minimum Revenue Loss: Set a minimum amount of projected revenue loss considered high loss. This affects how issues appear in the Priority Issues view.
- Minimum Checkout Down Minutes: Enter the minimum number of minutes your checkout can be down before receiving an alert.
- Add a Staging Domain. This is optional, but recommended.
2. Create User Logins & Configure Sign-on Options
Noibu is best with company. Think about who on your team should have access to the Noibu platform, and create user accounts accordingly. You should also think about how your team will access Noibu, and if necessary, configure Single Sign-On (SSO).
- Add Teammates. Fortunately, there's no limit to the number of users you can add to your Noibu platform. If necessary, you can grant access to your entire team.
- Pay special attention to each user's Role and Notification Settings.
- Configure SSO via OAuth2. This is optional, but many Noibu clients use OAuth2 authentication for added security.
3. Establish Integrations
The best way to incorporate Noibu into existing workflows is to set up integrations with other task management and communication tools. Most Noibu clients benefit from the following integrations:
- Jira Integration: Noibu's integration with Jira creates a direct path between issues in Noibu and tickets in Jira. After triaging an issue, you can sync the issue to Jira to create a corresponding ticket with all the information your developers need to solve the issue.
- Slack Integration: Through an integration with Slack, Noibu can send notifications for major errors to a dedicated Slack channel.
- Release Monitoring: Create a webhook to pull release information from your CI/CD tool into Noibu's Events page.
4. Customize Your Experience
Noibu tracks a variety of data on issues affecting your eCommerce site, and there's room in the Noibu console to customize your experience to more easily sort issues in a way that makes sense for your team.
- Add Issue Labels. Noibu gives you a menu of filters to isolate issues that meet a set of criteria, but you're also free to add custom labels to group issues by other characteristics.
- Familiarize yourself with the NoibuJS software development toolkit–or SDK. Through the SDK, you can interact with captured session data by creating custom attributes.
- Create Specialized Alerts to notify you when an issue appears with specific characteristics.
5. Identify & Resolve Your First Error
Noibu can be overwhelming at first. You may have a huge backlog of errors to dig through, and it's difficult to know where to start. It takes practice to learn to efficiently investigate and prioritize errors, and Noibu provides resources, both in-app and in the Knowledge Base, to help you triage your backlog and start resolving errors.