Excluding traffic

Excluded traffic is dropped by /collect before anything is stored. It never appears in any report, and it never counts toward your monthly Quota. Exclusions apply from the moment you save them; they do not remove what was already stored.

Ignored IP addresses

In the Site's Settings → Filtering, under Ignore internal traffic, add the IP addresses your team browses from. Add my current IP fills in the address you are using right now.

Each rule is either:

• one address, IPv4 or IPv6, such as 203.0.113.7 or 2001:db8::1
• a CIDR range, such as 203.0.113.0/24 or 2001:db8::/32

Every hit from a matching address is dropped: Pageviews, Events, Outbound links and identify() calls.

Excluded paths

Under Excluded paths, add the pages that should never count, such as an admin area or a preview page. A rule starts with /, and * matches any characters, slashes included:

Rules match the path only, without the query string. Pageviews and Events on an excluded path are dropped. Outbound links have no path of their own, so they are kept.

A Site takes up to 100 IP rules and 100 path rules.

Bots

Hits from bots are dropped on every Site, with nothing to configure. We recognise search engine crawlers, link previews, uptime monitors, headless browsers and automation tools (Puppeteer, Playwright, Selenium), and HTTP clients such as curl, Wget, Python, Go, Java, OkHttp, axios, node-fetch and undici, as well as requests with no User-Agent at all.

Excluding yourself without a fixed IP

If your IP changes often, exclude yourself on the website's side instead: only add the snippet when you are not signed in as an admin, or leave it out of your staging and preview builds.