Three ways to stop it. Pick by whether the thing you want to exclude is a place on your site, a connection, or a browser.
The quickest: this browser
Open the console on your own site and run:
localStorage.truestat_ignore = "true";Nothing is sent from that browser on that origin from then on. To undo:
delete localStorage.truestat_ignore;Three catches:
Per origin and per browser.
example.comandstaging.example.comare separate. So are Chrome and Firefox, and so is every profile. Set it in each.Clearing site data clears it, silently re-enabling yourself.
Private windows do not keep it. Every private session is a fresh visitor.
This is the best option for a laptop you control, and it is checked before anything is sent, so it works even when everything else is misconfigured.
Your connection
Site settings → Excluded IPs. Add your address; find it by searching "what is my IP" in the browser you want to exclude.
Your IP is hashed before it is stored — the raw address is never written. The hash is scoped to your site and survives our daily key rotation, so an exclusion set today still works next month.
The limitation: most home connections have a dynamic IP. If yours changes, the exclusion quietly stops working and nothing tells you. For a fixed office connection it is reliable; for a home connection the browser flag is better.
A section of your site
Site settings → Excluded paths. One glob pattern per line:
/admin
/admin/*
/wp-admin/*/admin/* does not match /admin itself. That catches people constantly —
if you want both the section and its index, list both, as above.
* is the only wildcard. Everything else is literal.
Which to use
| Situation | Use |
| Your own laptop | The browser flag |
| A fixed office connection | IP exclusion |
| A home connection with a dynamic IP | The browser flag |
| An admin area nobody should count | Path exclusion |
| A staging path on the same site | Path exclusion |
| Local development | data-allow-localhost off — the default |
All of them are free
Path and IP exclusions are applied before the event is stored, so excluded views never enter your monthly event count. The browser flag is applied earlier still — nothing is sent at all.
If a large share of your traffic is your own admin area, excluding it directly reduces your bill. See What counts as an event.
The opposite problem: my visits are not being counted
If you are testing an install and your own page loads produce nothing, one of the same three is switched on.
localStorage.truestat_ignore // undefined means the flag is not setThen check the site's excluded IPs for your current address, and its excluded paths against the URL you loaded.
A path exclusion is the sneaky one: the request returns 202 and no row is
written. In DevTools it looks exactly like success.
Why not "exclude logged-in users"
There is no such setting, because TrueStat has no idea who is logged in to your site — it does not see your cookies, your session or your user model.
The way to do it is to render the tag conditionally: do not emit it when the visitor is signed in as an admin. The tag not being on the page is the most complete exclusion available, and it costs no quota.