Filter a Single Metric

Every KPI card and tier-3 table row on an Analytics v2 question page carries its own filter control, separate from the page’s global filter bar. Use it when you want to ask “what does this one number look like for email only” without re-scoping every other card on the page.

This article covers the per-card control. For the filter bar that scopes the whole page — date range, channel, team, and so on — see Filter and explore Analytics. The two work together: the card control narrows on top of whatever the page filters already set.

Opening the control

Each KPI card and each row of a tier-3 table has a small filter icon on it. Click it to open the card’s own filter popover.

The popover shows the same dimension (channel, team, priority, and so on) the page’s filter bar uses — but only for that one measure. Any narrowing already set by the page filters is named inside the popover rather than pre-ticked, so a value the page has already picked isn’t silently discarded if you pick something else; you choose explicitly what this card should use instead.

Setting a metric-only filter

Pick a value in the popover and it drafts while the popover stays open — nothing is sent until you close it, so a run of clicks costs one request, not one per click. Close the popover to commit the override.

Once set, the card face shows a note under the number:

This measure only: Channel: Email

If your pick replaces a value the page filter bar had already set for that dimension, the note names both:

This measure only: Channel: Email — instead of the page’s Channel: Voice

That note is the only thing that tells you a number on the card is measured over a different population than the rest of the page. If a card shows no such note, it’s reading the page’s filters like everything else.

The override lives per metric and per dimension — you can narrow a card’s channel without touching its team filter, and narrowing one card’s Response Time doesn’t touch any other card’s Response Time on the page. It also survives navigation: it’s carried in the page URL and remembered per tenant, so reopening the same question page brings the override back.

Priority note: if you filter by priority and a ticket has no priority set, it’s grouped under (No priority) — folded into “normal,” the same rule Inbox uses — rather than being dropped from the count.

What gets a control, and what doesn’t

Not every chart on a page is a candidate for narrowing on its own:

• Single-measure panels — sliced rates, matrix breakdowns, backlog, clocks, CSAT — Follow the card’s own filter, and say so on the card face.
• Add-up pictures — call funnel, flow charts — Always draw the whole page’s population; a card control here would break the arithmetic the picture depends on. Any term narrowed elsewhere on the page is still named.
• Comparison measures — Don’t offer a control at all — their mix panel is describing the page’s population by design, so there is no “this measure only” to show.

If a chart has no filter icon on it, that’s why.

Drills and evidence follow the override

Click through from an overridden card into its drill-down or evidence chart, and the merged scope travels with it — the population you narrowed the card to is exactly what the drill and the evidence chart are built from. You never land on a drill that answers a different question than the number you clicked.

This is deliberate: one measure is one population everywhere it appears — the card, its evidence chart, its drill, and the answer sentence all read the same merged filters. If the override’s own request fails, the card blanks that slot rather than quietly falling back to the page’s number for that measure.

Clearing the override

Reopen the card’s filter control and clear the selection, then close the popover to commit. The “This measure only:” note disappears and the card returns to reading the page’s own filters.

If a chart is empty only because of a card-level filter (the page’s own filters would show data), the empty state offers a Clear action directly — use it instead of hunting for the control.

How this differs from the page filter bar

The page’s filter bar (see Filter and explore Analytics) sets the scope every card and chart on the page reads by default. The per-metric control on a card only ever narrows that one measure, on top of whatever the page has already set — it never changes what any other card sees, and it never widens a page-level narrowing, only replaces it for that one card and says so.

Reach for the page filter bar when you’re asking one question about the whole page. Reach for a card’s own control when you need one number answered for a different slice than everything else on the page.