Skip to main content

Path exclusions

Path exclusions prevent PureStats from recording pageviews or events for matching paths even when the tracker is installed there.

Configure exclusions in Site Settings. The tracker loads these rules automatically, so the default script tag still only needs data-domain.

Common exclusions​

Examples:

/admin
/admin/*
/account/*
/preview/*
/internal/*

Use exclusions when the tracker is included through a shared layout but some areas should not appear in analytics.

Matching behavior​

Rules should be simple and predictable:

  • Exact paths match only that path.
  • Prefix or wildcard-style rules match child paths.
  • Query strings are ignored for path matching.

Keep rules narrow. Excluding /app/* may remove important product analytics if your app lives there.

Private and staff traffic​

Path exclusions are different from internal traffic filtering. Exclusions remove specific URLs for everyone. Internal traffic filters remove visits from known staff or environments.

Debugging exclusions​

If a page does not show up:

  1. Check Site Settings for exclusion rules.
  2. Confirm the browser path matches the rule.
  3. Switch dashboard traffic mode to all traffic.
  4. Inspect the Network response from /api/event.

Privacy benefit​

Excluding private areas reduces the chance that account URLs, billing paths or internal workflows appear in analytics reports.