Filters — Abner Docs

Narrow down your data by dimension, at query time, via the REST API or MCP server.

How filtering works

Abner's web dashboard is deliberately minimal — a site list and a per-site last-24h visitors/pageviews view. There is no dashboard filtering UI. Instead, filters are applied at query time when you request data from the REST API or the MCP server.

Filtering via the REST API

Pass filter.<dimension>=value as a query parameter on any read endpoint. You can combine multiple filters in a single request:

GET /api/v1/stats?filter.country=US&filter.browser=Chrome

Filtering via MCP

The MCP query_metrics tool accepts a filters argument with the same dimension/value pairs:

{ "filters": { "country": "US", "event_name": "signup" } }

Filterable dimensions

You can filter on any of the following dimensions:

pathname
referrer_host
country
region
city
browser
device_type
utm_source
utm_medium
utm_campaign
event_name

The full, always-current vocabulary of metrics and dimensions is also available live at GET /api/v1/meta.

Learn more

See the REST API reference for the full list of endpoints, and the MCP documentation for details on connecting Claude, Cursor, or your own MCP client.