Excluding traffic

Bots are filtered automatically. These rules run on top, for traffic you don’t want counted.

Your own visits

Settings, General has a “Do not count” list with a tick box for every role on the site. Visits from logged-in people with a ticked role are left out of every report. Administrator is ticked by default, so your own browsing doesn’t pollute the stats. To count administrators, for example while testing, untick it.

Tick editors, authors, shop managers or any other role to keep the rest of the team out too. Roles left unticked, such as customers, are counted. To leave out your own visits when you browse logged out, exclude your IP address.

Excluded IPs

Settings, Tracking, Exclusions, “Excluded IPs / CIDR”: one entry per line. IPv4, IPv6 and CIDR ranges work.

203.0.113.7
198.51.100.0/24
2001:db8::/32

Excluded addresses are dropped for pageviews, events and speed measurements.

Excluded paths

“Excluded paths” takes one path pattern per line. * matches anything except /, and ** matches anything.

/wp-admin/*
/wp-login.php
/checkout/*
/members/**

/wp-admin/* and /wp-login.php are there by default.

Countries

“Excluded countries” under Geo-location discards traffic from whole countries. See Countries and devices.

Click Save settings

Rules apply from the moment you save. Nothing already counted is removed.

Behind a proxy or load balancer

If your site sits behind a reverse proxy, Vireo may see the proxy’s address instead of the visitor’s, and IP exclusions won’t match. Switch on proxy headers with the vireo_trust_proxy_headers filter. Vireo then believes them only from Cloudflare, loopback and private network addresses. A proxy on any other address needs adding with vireo_trusted_proxies.

Keep the tracker off certain pages

To stop the tracker loading on some pages entirely, a developer can return false from the vireo_load_tracking_script filter.