moneat.io

Excluding Traffic

Your own visits inflate the numbers you use to make decisions. Moneat has two ways to leave them out, and they answer different questions: the ignore flag covers this browser, an excluded address covers everything behind that address.

Both are applied before anything is written. Excluded events are never stored, never appear in any breakdown, and never count toward your pageview allowance.

Exclude an address or range

Address exclusions are set per organization and apply to every tracked site.

  1. Go to Settings → Web analytics.
  2. The address this browser reaches Moneat from is shown at the top. Choose Exclude to add it.
  3. To cover a whole network, enter a CIDR range under Address or range — 203.0.113.0/24 covers every address in that block.

Only an organization owner or admin can change the list. Every member can read it, so the numbers and what they omit stay visible to the same people.

Ingest reads the client address from X-Forwarded-For, falling back to X-Real-IP. If Moneat sits behind a proxy that rewrites those headers, exclude the address your proxy forwards, not the one your laptop reports.

Notes

  • A range is stored as its network address: entering 203.0.113.77/24 saves 203.0.113.0/24.
  • IPv4 and IPv6 are both accepted. An IPv4 range never matches an IPv6 client, so a dual-stack network needs an exclusion for each.
  • Enter a literal address or range, not a host name. An exclusion that resolved a name would change meaning without anyone editing it, so names are rejected.
  • An organization may hold up to 200 exclusions.

Exclude one browser

A home connection whose address changes, or a laptop that moves between networks, is easier to cover per browser.

Open any tracked page with ?moneat_ignore=true appended:

https://yoursite.com/?moneat_ignore=true

That browser stores the flag and stops sending events for that site. To undo it, open the same page with ?moneat_ignore=false.

For the Moneat dashboard itself, the switch under Settings → Web analytics → This browser does the same thing.

The flag lives in localStorage, so it covers one browser on one site: clearing site data removes it, and a second device needs its own. That is the reason to prefer an address exclusion when you can use one.

Separate the app from the site

If you run Moneat's dashboard on its own hostname, its pageviews land in the same project as your marketing site's. Use the Sites breakdown on the Analytics page to see the split, and click a row to filter everything below it to that site. In the API the same dimension is the site filter:

GET /v1/analytics/{projectId}/overview?period=30d&filters[]=site:is:moneat.io

What the tracker skips on its own

Without any configuration, no event is sent when:

  • The browser has Do Not Track enabled.
  • The page identifies itself as automated.

Automation that hides those signals is still counted, so check the Sites and Sources breakdowns before concluding that unfamiliar traffic is yours.