Filter your visits and exclusions

Open Settings → Exclusions to keep testing and internal activity out of new collection.

Ignore your browser

On the tracked website, run this in that site’s browser console, then reload:

localStorage.setItem('seean_ignore', 'true');

To resume, remove the preference and reload:

localStorage.removeItem('seean_ignore');

This affects that browser and website origin. Running it on app.seean.io does not set the preference on your own site. Do Not Track and Global Privacy Control also stop collection.

Use the Match dropdown to choose Path, Hostname, IP address or Country before entering a rule. It follows your theme and supports keyboard selection. Changing the match type clears the unsaved value; the control is disabled while saving.

Exclude a path

Add an exact path such as /admin, or a child-path prefix such as /admin/*. The latter matches children but not /admin itself. Paths are case-sensitive; omit query strings and fragments.

Exclude a hostname

A hostname rule matches that hostname and its www alias, not every other subdomain. For example, excluding staging.example.com does not exclude example.com.

On save, a pasted URL becomes a lowercase hostname without its trailing dot or first www. prefix. The saved name shown in the list is what the rule matches, together with one added www. prefix. For example, a saved www.example.com matches www.example.com and www.www.example.com; it does not match example.com, other.www.example.com or www.www.www.example.com.

Exclude an IP address or range

Enter a single IPv4 or IPv6 address, or a CIDR range such as 203.0.113.0/24 (IPv4 /8 to /32, IPv6 /32 to /128). On save, the address is canonicalized: lowercase, zone identifiers removed, host bits of a range cleared, and an IPv4-mapped IPv6 address such as ::ffff:203.0.113.7 stored as 203.0.113.7. Visitors arriving over IPv4-mapped IPv6 match IPv4 rules.

Exclude my current IP asks the collector for the address it sees for your browser and saves it as a rule. Your address changes when your network or VPN does; add a new rule when that happens. Nothing is stored by that lookup.

Addresses are compared at the moment a request arrives, using the visitor address reported by the network edge. Seean never stores visitor IP addresses, so an IP rule cannot filter earlier history.

Exclude a country

Enter a two-letter country code such as DE; the list shows its flag and name. The visitor’s country, region and city come from the network edge on each request, not from the browser. If the edge reports no country, the browser timezone or language estimate is used for reports, and the country rule compares against that value. A visitor using a VPN matches the exit country.

Scope and limits

Each website supports up to 50 rules. Matching new pageviews, custom events and Web Vitals are discarded before usage counting. Existing data stays in history. Remove a rule to allow future matching traffic again.

Use Remove beside the saved rule. This removes only that entry and leaves other rules in place. Removing the same entry again has no further effect. If a request fails, retry after the error; your existing rules remain unchanged. A rate-limited request says how many seconds to wait.

Revenue attribution only

The second card, Revenue attribution only: ignore checkout and thank-you visits, takes up to 20 path rules with the same /thanks or /checkout/* syntax. Unlike the rules above, they discard nothing: traffic on those paths is still collected and appears in every report. They only stop visits that enter on a matching path from taking attribution credit in the Revenue report and in the Overview’s revenue-by-source and entry-page credit. See ignore checkout and thank-you visits for how credit is recalculated.

Basic bot filtering is always active; it is not proof of complete bot detection. See bot handling.

Something unclear? Contact support.