Analytics

guide

Reading the analytics dashboard

A tour of the unified analytics page — time ranges, source filters, and what each panel is telling you.

Overview

Analytics pulls every signal your project collects into one page: support tickets, survey responses, form submissions, status incidents, feature requests, help center views, release views, and roadmap items.

Find it under Analytics in the sidebar. The page is scoped to the organization and project you currently have selected.

Controls at the top

  • Time range — last 7 days, last 30 days, last 90 days, or last year. Everything on the page respects it.
  • Period — Daily, Weekly, or Monthly. This controls how finely the time-series charts are bucketed.
  • Refresh — pulls fresh data without reloading the page.

The four score cards

Across the top sit four summary scores — Friction, Health, Engagement, and Overall. Each shows its value, a grade or trend, and whether it moved since the previous period. They're covered in detail in Friction, health, and engagement scores.

Cross-source activity

A time-series chart of event volume for each selected source. Only sources that have time-series data in the current range are plotted — help center views, release views, and roadmap items contribute to the summary metrics but don't appear as lines here.

Source throughput

A side-by-side comparison of the main volume metric for each selected source over the current range. Each source has its own headline number:

  • Support — total tickets
  • Surveys — total responses
  • Forms — total submissions
  • Status — total incidents
  • Feature requests — total feature requests
  • Help center — total views
  • Releases — release views
  • Roadmaps — total items

Because the units differ, read this as a shape comparison rather than an apples-to-apples ranking.

Content contenders

Ranks individual content items by performance across feature requests, releases, and help center. Toggle between the top three and the bottom three. The low performers are often the more useful list — a help article nobody reads is usually a signal that it's hard to find or answers the wrong question.

Source filters

The source filter panel decides which sources feed the charts. Turn sources off to isolate a signal — for example, view support and feature requests alone to see whether complaints and requests move together. At least one source stays selected at all times.

Score overview

Breaks the selected score into its component factors, so you can see what is pushing it up or down rather than just watching a number change.

Insights and correlation signal

  • Insights — generated observations about the current range, each with a short explanation.
  • Correlation signal — highlights the strongest relationship detected between two sources in the range.

Treat correlations as a prompt to investigate, not a conclusion. They tell you two things moved together; they don't tell you why.

Feature request status and quick links

Feature request status shows the distribution of feature requests by current status for the selected range. Quick links jumps you into the module behind whichever number caught your eye.

Blog performance

At the bottom of the page, a Blog section shows views over time and top posts by views. It carries its own time-range selector, independent of the one at the top of the page.

Permissions

Analytics requires the analytics:view or analytics:* scope. The dashboard needs both an organization and a project selected — if either is missing, the page will prompt you to pick one.

Was this article helpful?

Talk to sales

Tell us what you're running today and we'll map it onto AppGram.

A real human replies within one business day.