Many companies have online stores on multiple sites, and you can configure your Noibu platform to track errors across several eCommerce domains. The Domains module tracks every domain associated to your Noibu account. To gather data from a new domain, Deploy the Noibu Script to the site's HTML
<head> tag, and ask your Customer Success Manager (CSM) to associate the new domain to your account.
Through the Domains module, you can configure unique settings and preferences for each domain. Select a domain to open the Domain Details page.
Through the Domain Details page, you can access detailed information on a specific domain, and determine how Noibu manages the domain's data. The Domain Details page includes five tabs: General, Funnel Settings, Integrations, Issue Labels, and Data Collection.
The General tab lists the domain's most essential details, and allows you to make minor updates to how Noibu manages the domain's data:
- Domain Name: The domain's unique name.
- Site Type: The platform on which the site is built, if applicable.
- 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 per issue to show in the Funnel. This ensures the funnel only includes issues with significant revenue loss.
- Minimum Checkout Down Minutes: Enter the minimum number of minutes your checkout can be down before receiving an alert.
- Slack Webhook: Enable the domain's Slack Integration.
- Issue Notification Interval: Set the delay, in hours, between receiving notifications. For example, if this field is set to 2, there will be at least a two hour delay between notifications. Enter 0 for no delay.
You can also configure whether or not to collect client IP addresses in session captures, and whether to allow HTTP data collection to display in the HTTP Error Details section..
Your domain's Funnel Settings are configured on the backend through your CSM. Contact Noibu Support to set up your domain's funnel settings.
Through the Integrations tab, you can configure the domain's 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. Noibu supports Jira Cloud V3, Cloud V2, and Server V2.
The Jira integration is built using a webhook that listens to two events: issue_updated and issue_deleted. This means that changes to an issue's status in Noibu will reflect in the ticket's status in Jira, and vice versa. Closing or reopening a ticket in Jira will close or reopen the issue in Noibu.
Keep in mind that the Jira integration only applies to the domain in question. To integrate multiple domains with Jira, you must create a distinct integration from each domain.
From the Issue Labels tab, you can Configure Custom Labels to tag issues with similar properties. You may discover disparate issues with a similar root cause, or multiple issues isolated to the same workflow or page, and labels are a great way to group these issues and pull them up later using a filter.
Labels are configured at the domain level. If you have multiple domains connected to your Noibu account, you must configure labels separately for each domain.
Through the Data Collection tab, you can identify URLs to include or exclude from HTTP payload and response data collection. If you're examining an HTTP issue, its Developer tab will include an HTTP Error Details section that lists the error's type, code, message, and URL. By default, this section includes a tab that lists the error's HTTP headers, and you can opt in to collecting and displaying payloads and responses in this section by allowing select URLs. Having Noibu store payloads and responses eliminates the need for engineers to set up “log traps” to smoke out bad data as the root cause of an issue, which may expedite the debugging process.
As collecting HTTP payloads and responses may expose personally identifiable information (PII), we’ve left it up to you to identify URLs on which payload and response data collection should be allowed. You can also identify URLs to exclude or exempt, which may be useful, for example, if you want to collect data on all product pages EXCEPT those with a specific path.
This can be a tricky process, so we recommend reaching out to our solutions team at email@example.com to help configure this list. If you decide to go it alone, review our guide to Allowing or Excluding URLs, and be sure to consult the URL Guidelines.
Learn more about the Company module.