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.

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.

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 hostname or path 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.

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

Something unclear? Contact support.