Excluding internal traffic and /admin

Internal team traffic on /admin, /dashboard, /preview and similar paths skews every analytics metric. We strip it three ways: by IP, by URL path, and by GA4's internal-traffic flag.

Path-based exclusion (default-on)

These paths are stripped from analytics reports by default for every workspace:

text
/admin
/dashboard
/preview
/wp-admin
/login
/signup
/api

Customize in Settings → Analytics → Excluded paths. Use comma-separated substrings or regex.

IP-based exclusion

Add your office IPs and your home IP. Settings → Analytics → Excluded IPs. Supports single IPs and CIDR blocks:

text
203.0.113.42
203.0.113.0/24
2001:db8::/32

IPv4 and IPv6 both supported. We strip these from analytics, conversions and the user-flow funnel.

GA4 internal-traffic flag

If you've configured an "internal traffic" filter in GA4 itself, we respect the GA4-side flag too. This catches users hitting your site from VPNs or shifting IPs.

How they combine

A session is excluded if ANY of the three rules match: path is excluded, IP is excluded, or GA4 flagged it. There is no per-rule weighting.

Verifying exclusions

Settings → Analytics → Excluded sessions log shows the last 100 sessions excluded, with the rule that matched. Useful for confirming your office IP is correctly blocked and not accidentally taking out real users.

Excluding only conversions vs all data

By default, exclusions strip the session from all reports. Toggle "Strict mode" off in Settings → Analytics if you want sessions visible in pageview counts but excluded from conversions only. Useful for showing client traffic in agency reports while keeping conversion data clean.