EngageTrack

Exclude Visits

Filter out internal traffic, bots, and test environments from your analytics.

Exclude Visits

Keep your analytics clean by excluding internal team visits, development traffic, and bots from your data.

Self-Exclusion (Browser)

The simplest way to exclude yourself is from the browser console on your tracked site.

Using the SDK Method

// Disable tracking for this browser
window.engagetrack.ignore();
 
// Re-enable tracking
window.engagetrack.unignore();

Both methods require a page reload to take effect.

Using localStorage Directly

// Disable tracking
localStorage.setItem("engagetrack_ignore", "true");
 
// Re-enable tracking
localStorage.removeItem("engagetrack_ignore");

The exclusion flag is stored in localStorage, so it persists across sessions but is specific to that browser. You need to set it on each browser and device you use.

Bookmark Shortcut

Create a browser bookmark with this URL to toggle exclusion with one click:

javascript:void(localStorage.getItem('engagetrack_ignore')==='true'?(localStorage.removeItem('engagetrack_ignore'),alert('EngageTrack: Tracking enabled. Reload the page.')):(localStorage.setItem('engagetrack_ignore','true'),alert('EngageTrack: Tracking disabled. Reload the page.')))

IP Exclusion

Exclude traffic from specific IP addresses or ranges in the dashboard:

  1. Go to Site Settings -> Tracking
  2. Under Excluded IPs, add IP addresses or CIDR ranges
  3. Traffic from those IPs will be silently dropped

Common use cases:

  • Office IP addresses
  • VPN exit nodes used by your team
  • CI/CD server IPs

IP exclusion is applied server-side, so excluded traffic never appears in your analytics data at all.

Path Exclusion

Exclude specific pages or URL patterns from being tracked:

  1. Go to Site Settings -> Tracking
  2. Under Excluded Paths, add URL patterns

Patterns support wildcards:

PatternMatches
/admin/*All pages under /admin/
/internalExact match for /internal
/staging/*All staging pages

Hostname Exclusion

If you have the script installed on staging or development environments and want to exclude that traffic:

  1. Go to Site Settings -> Tracking
  2. Under Allowed Hostnames, list only the production hostnames

Any traffic from hostnames not in the list will be ignored.

If you leave the allowed hostnames list empty, traffic from all hostnames is accepted. Add at least your production domain to enable hostname filtering.

Verify Exclusion

To confirm your visits are being excluded:

  1. Add data-debug="true" to the script tag (or use a development environment)
  2. Open the browser console
  3. If you have engagetrack_ignore set, you will see: [EngageTrack] Tracking disabled via engagetrack_ignore flag
  4. Check the Real-time dashboard view — your visits should not appear