Using usage.io

Exclude traffic

Excluded traffic is filtered per site in Settings. Matching page views are discarded during processing and never appear in your dashboard or usage totals for reporting purposes.

You do not need to remove the tracking snippet to exclude admin areas or your office network—configure filters instead.


Excluded Paths

Path filters use PHP-compatible regular expressions applied to the URL path only (the part after the hostname, starting with /). Query strings are not matched by the pattern itself.

In Settings → Excluded Paths, enter a pattern and click Add filter. Examples:

PatternTypical use
^/adminAdmin area and subpaths
^/previewDraft or preview routes
/wp-adminWordPress dashboard
\.(php|asp)$Legacy script endpoints you do not want in top paths

The settings UI suggests placeholders such as ^/admin, /wp-.*, and \.(php|asp)$.

Test after each pattern

A pattern that is too broad (for example matching all paths) will hide real traffic. Add one filter at a time and check Page views and Top paths for the date range you care about.

To remove a filter, use Remove next to the pattern in the list.


Excluded IPs

In Settings → Excluded IPs, add:

  • A single IPv4 address (for example your office egress IP)
  • A CIDR range (for example 203.0.113.0/24)

Visits from matching addresses are discarded for that site. IPv6 addresses are not supported in the exclusion UI at this time.


When to use exclusions

ScenarioSuggested approach
You visit your own site dailyExclude your office or home IP
/admin or /wp-admin trafficPath regex for that prefix
Staging environment on a different hostPrefer a separate site entry or do not install the snippet on staging
Bots from a fixed IP you controlIP or CIDR exclusion

Billing and usage

Excluded visits should not appear in your analytics. For environments you never want measured, omit the tracking snippet entirely rather than relying on exclusions alone.


Previous
Site settings