Three tools, applied at different points. The difference between them matters, because two of them are free and one is not.
The site settings exclusions panel showing both fields — excluded paths with a couple of glob patterns entered, and excluded IPs with one address added and shown as stored. Light theme, desktop.
Path exclusions
Stop counting whole sections of your site.
Site settings → Excluded paths. One pattern per line:
/admin
/admin/*
/wp-admin/*
/preview/*The wildcard rule, exactly
* is the only wildcard, and it means "any characters".
| Pattern | Matches | Does not match |
/admin | /admin and nothing else | /admin/users |
/admin/* | /admin/users, /admin/settings/general | /admin |
/admin/* does not match /admin itself. If you want both, list both — as
in the example above.
A pattern with no * is an exact match. Everything else in the pattern is
literal, including dots, so /v1.0/docs matches only that path.
Full regular expressions are not supported. That is deliberate: this runs on every incoming event, and a pattern that backtracks badly would be a self-inflicted outage on your own collector.
IP exclusions
Stop counting a particular connection — your office, your home.
Site settings → Excluded IPs. Add the address.
The address is hashed before it is stored. The raw IP is never written. The hash is scoped to your site, so it is meaningless anywhere else, and it is computed in a way that survives our daily key rotation — an exclusion you set today still works next month.
To find your current address, search "what is my IP" in the browser you want to exclude.
The obvious limitation: most home connections have a dynamic IP. If yours changes, the exclusion stops working and you will not be told. The browser flag below is more reliable for a machine you control.
The browser flag
Stop counting this browser on this origin, with no account setting at all. Open the console on your own site and run:
localStorage.truestat_ignore = "true";To undo it:
delete localStorage.truestat_ignore;Three things about it:
Per origin and per browser.
example.comandstaging.example.comare separate. So are Chrome and Firefox, and so is each browser profile. You have to set it in each one.Clearing site data clears it, silently re-enabling yourself.
It is checked in the browser before anything is sent, so it costs nothing and works even when the collector is unreachable.
Which one to use
| Situation | Use |
| An admin area nobody should count | Path exclusion |
| A staging path on the same site | Path exclusion |
| Your office, fixed connection | IP exclusion |
| Your own laptop | The browser flag |
| Your home, dynamic IP | The browser flag |
Excluded traffic does not cost you anything
Path and IP exclusions are applied before the event is stored, so excluded views are never written and never count against your monthly event limit.
This is a real lever, not a footnote. If a large share of your traffic is your own admin area, excluding it directly reduces your usage and can keep you on a cheaper traffic step. See What counts as an event.
The browser flag is applied even earlier — in the browser, so nothing is ever sent.
What is not excluded
Bot and crawler traffic is never excluded at collection. It is always stored and filtered when you read it. That is what makes AI visibility possible at all: a crawler hit discarded on arrival can never be reported.
So crawler traffic does count against your monthly event limit. If that is a problem for you, What counts as an event explains the trade-off.
What is not available yet
Excluding by country and excluding by hostname are not built. If you are getting a large volume of traffic from somewhere you do not care about, the current answer is a path exclusion if the traffic hits identifiable paths, and otherwise a bigger traffic step.