Why ignore paths
Not every page is relevant to performance measurement. Admin areas, login pages or internal tools distort the statistics because they have different loading characteristics from the pages real visitors see.
Configuration
Under Live data > [website] > Ignore paths you can enter paths that are excluded from measurement. One path per line.
Exact paths
/wp-admin/
/wp-login.php
/cart
Wildcards
You can use * at the end of a path:
/wp-admin/*
/api/*
/intern/*
That excludes all pages below this path.
Typical entries
| Path | Why ignore it |
|---|---|
/wp-admin/* |
WordPress back end — no visitor traffic |
/wp-login.php |
Login page — not representative |
/cart |
Shopping cart — often dynamic and not cacheable |
/checkout/* |
Checkout process — different performance characteristics |
/preview/* |
Preview pages — not public |
When paths are excluded
Events from ignored paths are filtered as soon as they arrive — they are not stored and appear neither in the dashboard nor in alerts.
Filtering in detail
Paths are filtered on two levels:
- On receipt (ingestion): the RumFlush command checks the ignore patterns before events are stored. Events from ignored paths are discarded and do not count towards the page view quota.
- At evaluation time (query time): dashboard queries apply the ignore filter additionally, so that events already stored are also excluded from charts and metrics by patterns added later.
This means: a new ignore pattern takes effect on the dashboard immediately. Events that were already stored (before the pattern was added) stay in the database. But they no longer appear in any dashboard view.
No regular expressions
Only exact paths and wildcard paths (/pfad/*) are supported. Regular expressions or partial matches are not possible. The * placeholder only works at the end of a path.