Skip to main content

Analytics overview

You came here to read about what our analytics capabilities are. That’s reasonable — this doc is called “Analytics Overview”, after all.

Disc scratch

We’re going to start by talking about what CommandBar analytics do not do.

What CommandBar Analytics are not

At CommandBar, we’re honest folks — we list our real height on dating apps, and we’ll tell you if you have something in your teeth.

CommandBar analytics are not general-purpose product analytics. That means you can’t use CommandBar analytics to do analyses like the following:

  • Track product feature usage
  • Surface usability problems
  • Identify user-facing errors

This is because we consider product analytics a non-feature: something we intentionally haven’t built because we don’t believe it falls within our mandate.

Ok so what do CommandBar analytics do then?

CommandBar analytics are designed with two purposes in mind:

  • (a) Help you understand how users are engaging with CommandBar and the subsequent value CommandBar is driving for your company. If users aren’t engaging with anything CommandBar-related, it’s very unlikely we’re creating value.
  • (b) Help you optimize CommandBar experiences. That might mean comparing the performance of two variants of a nudge via an A/B test. Or looking through deadends to determine new Answers to create for Copilot.

How CommandBar analytics are organized

Analytics dashboard

Each CommandBar experience has a distinct page that lets you do the two jobs (a) and (b) described above.

For Nudge experiences, we have pages for Announcements, Checklists, Product Tours, and Surveys. For Assist experiences, we have pages for Copilot, Spotlight, and HelpHub.

Coming soon, we’ll have other analytics pages that let you drill into important concepts like Deadends that cut across multiple experiences.