Exclude your own visits, IPs, countries, hostnames, or paths

To improve the accuracy of your analytics and filter out your own activity or irrelevant traffic, Flowsery Analytics provides several exclusion options.

Tip: Exclusions also help lower your Flowsery Analytics usage. Excluded visits are not counted against your monthly event quota, letting you reserve your allowance for traffic that actually matters.

1. Exclude specific URL paths

You can block events from particular URL paths (e.g. /settings, /test) from being recorded. Both exact paths and wildcard patterns are supported.

  • /admin - Excludes only the exact /admin page
  • /admin/* - Excludes everything under /admin (such as /admin/users, /admin/settings, /admin/settings/general, etc.) but not the /admin page itself.

All events on these paths will be excluded from tracking, including revenue attribution.

  1. Open your Website Settings in Flowsery Analytics.
  2. Go to the Exclusions tab.
  3. Enter the URL paths you want to filter out. Flowsery Analytics will stop tracking visitors on these paths, and they will not appear in your reports.

2. Exclude IP addresses

You can block visits from specific IP addresses (e.g. 127.0.0.1) so they are not included in your analytics.

  1. Open your Website Settings in Flowsery Analytics.
  2. Go to the Exclusions tab.
  3. Enter the IP addresses you want to filter out. Flowsery Analytics will stop tracking visitors from these IPs, and they will not appear in your reports.

3. Exclude specific countries

You can block events originating from certain countries. This is helpful for filtering out bot-heavy regions or meeting data privacy requirements.

  1. Open your Website Settings in Flowsery Analytics.
  2. Go to the Exclusions tab.
  3. Pick countries from the dropdown to exclude. Flowsery Analytics will stop tracking visitors from those countries, and they will not appear in your reports.

All events from excluded countries will be filtered out, including revenue attribution.

Common use cases:

  • Remove bot-heavy regions that distort your analytics
  • Meet regional data privacy regulations
  • Narrow your analytics to target markets only

4. Exclude specific hostnames

You can block events from particular hostnames. Only the exact hostname will be filtered out.

  • subdomain.example.com - Excludes only that specific hostname
  • example.com - Excludes only the root domain (subdomains are not affected)

All events from excluded hostnames will be filtered out, including revenue attribution.

  1. Open your Website Settings in Flowsery Analytics.
  2. Go to the Exclusions tab.
  3. Enter the hostnames you want to filter out. Flowsery Analytics will stop tracking visitors from those hostnames, and they will not appear in your reports.

Common use cases:

  • Remove white-labeled subdomains (e.g., user1.example.com, user2.example.com)
  • Filter out staging or test environments
  • Exclude internal tools or admin panels

5. Exclude your own visits (browser-based)

To stop your visits from being counted in a specific browser, you can set a localStorage flag. This approach works well for development and testing.

To exclude your visits:

  1. Navigate to the website where you want your visits excluded.
  2. Open your browser's developer tools. (Right-click the page and choose Inspect, or press F12 on Firefox/Chrome, or Option+Command+i on Safari).
  3. Switch to the "Console" tab.
  4. Paste the following command and press Enter:
localStorage.flowsery_ignore=true

You will need to repeat this for each domain/subdomain and every browser you use for testing.

To re-enable counting of your visits:

  1. Go to the website and open the developer console as described above.
  2. Paste the following command and press Enter:
delete localStorage.flowsery_ignore

Tip: For additional strategies to lower your event usage and avoid plan limits, see the reduce your usage guide.