Dashboard filters

Filters narrow the dashboard to a specific segment of visitors or pageviews. They are applied through the URL, so filtered views can be shared with teammates who have access to the same site.

Available filters#

PureStats supports filters for:

• Pathname and landing page.
• Referrer and traffic source.
• UTM source, medium, campaign, term and content.
• Country, device, browser and operating system.
• Event names, configured custom dimensions and website areas.
• 404 diagnostics, separate from success goals.
• Bot, spam and AI traffic modes.

Applying filters#

Open the filter panel, choose a dimension, select an operator and enter a value. After saving, the dashboard reloads with the filter encoded in the URL.

Example encoded filter:

{
  "utm_campaign": "spring_launch",
  "source": "newsletter"
}

Removing filters#

Reopen Filter to change individual rules, or choose Clear all. Traffic mode is controlled separately by the traffic selector.

Operators and cohort semantics#

Each rule has an operator: Equals, Does not equal, Starts with, Does not start with, Path and descendants, Excludes path and descendants, Contains or Does not contain. Add separate rules instead of entering comma-separated text. Commas in a value are literal characters. Regular expressions are not accepted.

Channel, website-area and diagnostic filters support only Equals and Does not equal. Channel labels are computed categories, not raw referrer strings; path operators apply to page and landing-page values.

Positive rules for one dimension are alternatives (OR). Negative rules are exclusions (AND); a missing value is not treated as a match for an excluded value. Different dimensions combine with AND. path:/app includes /app and /app/devices, but not /application. !path:/app/admin does not exclude /app/administer. Prefix and contains values treat SQL wildcard characters as literal text.

{
  "page": ["path:/app", "!path:/app/admin"],
  "custom:12": "!eq:error"
}

The custom dimension ID is site-specific. Existing equality-only URLs remain valid. URLs, segments, dashboards and exports keep the same encoded rules.

Overview pageviews, visitors and charts use matching pageviews in the selected period. Visits, duration, bounce rate and entry/exit lists use their associated visit cohort, including visits that began before the period. Duration and bounce describe the whole stored visit, not time spent only on the matching path. Goal counts require conversions in the selected period from matching visits. Event-name filters select visits containing a matching event; they are not a claim that every page caused that event. Live visitors use matching pageviews in the last five minutes, independent of the historical date selector.

Weekly insights are whole-site human-traffic summaries and are hidden for filtered views. Search Console aggregates support only page, landing-page, country and device filters; the widget is hidden for other filters because search-provider aggregates do not contain site_area, custom properties or individual visitors.

Website areas and historical coverage#

Create site_area as an active Event / String custom dimension. Supported values are marketing, documentation, auth, app, status and error. An indexed explicit value takes precedence over the path fallback. A custom-dimension equality filter alone does not classify historical rows that lack that value.

The Website area filter uses these exact fallback routes, including their /en and /de equivalents:

Area	Historical fallback
marketing	/ exactly; /blog, /features, /product, /products, /pricing, /about, /contact, /compare, /solutions and descendants
documentation	/docs, /documentation and descendants
auth	/login, /register, /auth, /forgot-password, /reset-password and descendants
app	/app and descendants, excluding /app/admin and descendants
status	/status and descendants
error	/404, /error, /errors and descendants

Unknown paths and API routes are not inferred as marketing. The coverage notice separates explicitly labeled pageviews from path-fallback pageviews. This does not rewrite historical data or recover missing hits. For success-only marketing and product reports, add Diagnostic type / Does not equal / 404. A diagnosis view instead uses Diagnostic type / Equals / 404.

Saved segments#

If you reuse a filter combination, save it as a segment. Segments can be personal, site-level or used as dashboard defaults depending on your permissions.

Performance notes#

Very broad custom combinations may take longer on high-traffic sites, especially across large date ranges.

Find a website, report or settings section#

Use Search in the app header or press Ctrl+K / Cmd+K. Search websites by name or domain, saved report schedules, analytics views and website settings. Results only include your current website memberships; report management and settings require the appropriate role. With no active website, choose a website before opening a site-specific view. Switching websites keeps the date range and clears website-specific filters and saved-view selections.

Website settings also include Find a settings section for their sixteen sections. Choose a result to open its direct URL fragment. Existing pinned analytics tabs remain available.