Baresquare features

Familiarize yourself with the basic Baresquare features and terminology

Updated over a week ago

Baresquare UI components can be grouped into the following categories:

Action detection

This section's components refer to the automated output of our Diagnostics engine. This is precisely where our anomaly detection system reports incidents like traffic spikes, conversion sinks, or broken buttons.

Tickets feed timeline

The tickets feed timeline holds all tickets produced, including a short description of the metric behavior, ticket number, date, impact, and progress status. You can easily select a specific ticket to see the detailed summary by clicking on it, which results in the ticket opening on the main ticket screen. You can also choose to "Sort by" Newest or Oldest. Same date tickets will be automatically sorted by impact.

You can also use the filter bar to filter tickets by status, assignee, priority, date range, and many more.

Ticket screen

The ticket screen contains details of the selected incident automatically produced by the diagnostics engine.

Starting from the top, the incident title briefly describes the anomaly detected. In the main section, our diagnostics text generation engine produces a detailed description of the incident in plain English. This description contains all the information necessary to take action, including the specific dimension(s) that contributed to the reported incident.

It also includes the following information: impact, trend view & expected limits, related metrics, related incidents, follow-up analysis, revenue opportunity and additional comparisons (vs. previous day, same day last week, avg. of last 4 weeks).


The following features allow you to act fast and collaborate seamlessly with your team on reported incidents by sending clear next steps:


You can leave a note or add additional information, including attachments to guide the rest of the team.

Just type your comment, attach the files you want to include, and click the "Post" button. Mention a team member to request action or keep them looped in.

Comments also document how the team resolved a case for future reference.

Assign to:

You can assign a ticket to your team member to delegate ownership.

Share a ticket:

You can share a ticket with colleagues and teams either on Baresquare or through other collaboration tools like Jira (available soon) or Slack.

Define a priority:

By defining the priority of a ticket your team knows what to focus on.

Drive efficiency

Based on your previous actions, approvals, and automations, Baresquare’s AI learns what metrics matter most to your business, and gets smarter over time.

The more actions you take, the better our predictions and recommendations become.

Mute priority:

"Mute" is your way of saying that you don’t want to see items like these. This category helps Baresquare learn what’s important to your team.

Resolution comment:

When the work is done, you can mark the ticket as resolved, and document how the team resolved this case for future reference.

Resolved and "not incident"

Resolving a ticket and marking it as “not an incident” indicates that similar tickets are necessary, but this specific ticket was not of value after further analysis. This can help filter resolved tickets by differentiating the ones which were resolved and the ones which were resolved but were not valuable.

Did this answer your question?