Skip to Content
Filtering your reports

Filtering your reports

You’ve always been able to click a row to focus a report on one thing — one country, one page, one browser. Now you can stack those choices and ask a much sharper question: “Chrome visitors, from Germany, who landed on /pricing.” Every report on the page then recomputes for exactly that slice.

This is being rolled out gradually, so it may not be switched on for your account yet. It only appears when you are signed in — it never shows on a public or shared dashboard.

How to add a filter

Click any row in a breakdown panel — Top Pages, Top Referrers, Top Countries, Top Devices, Browsers, OS, a campaign, a region, a city. That value becomes a filter, and the whole page updates to show only that slice.

Keep clicking to narrow further. Each click adds another filter on top of the last one.

The filter bar

Every filter you add appears as a chip in a bar near the top of the page, so you can always see exactly what slice you’re looking at — for example:

Country: Germany Browser: Chrome Page: /pricing

To remove a filter, click its chip (or focus it and press Enter, Delete, or Backspace). The page immediately recomputes for the remaining filters. Remove them all and you’re back to your full site.

Your filters live in the page’s web address, so you can bookmark a filtered view or share the link with a teammate who has access, and they’ll open the same slice.

How stacking works

  • Different things narrow (AND). Adding Germany and then Chrome shows visits that are both from Germany and on Chrome.
  • Same thing widens (OR). Clicking two countries — say Germany and France — shows visits from either country.
  • Up to five at once. You can stack filters across as many as five different dimensions (country, device, page, and so on) at a time. That’s plenty to answer a precise question without slicing so thin the numbers stop meaning anything.

”Slice too small” on some numbers

On a Mode B (Anonymous visitors) site, if you filter down so far that fewer than 25 visitors match, Voris will hide the visitor-based numbers for that slice — unique visitors, bounce rate, and session duration — and show Slice too small in their place.

This is a privacy protection, not an error. When a slice gets tiny, those numbers could start to point at a single, identifiable person, and Voris is built so that can’t happen. Pageviews and other non-personal counts still show normally. Widen your filter — remove one, or add a second value to an existing one — and the visitor numbers come back as soon as the slice is large enough.

You may also see Mode B required on those same numbers if your site is on Mode A. That’s a different message with a different cause — see Privacy modes explained. “Slice too small” means Mode B, but this particular filtered slice is too small; “Mode B required” means this metric needs Mode B in the first place.

Good to know

  • Filters respect your period. A filtered view still honours the time range in your period selector.
  • Region and city filters need Mode B. On a Mode A site those two aren’t collected, so they can’t be filtered on; every other dimension can.
  • A filtered link only works for people who can see the site. Sharing the URL doesn’t grant access — the other person still needs to be signed in with permission for that site.
Understanding your dashboardRegions and cities