IP Exclusions
IP exclusions let you filter out internal traffic from specific IP addresses or CIDR ranges. Events from excluded IPs are dropped before ingest -- they are never stored in the database and never forwarded to ad platforms.
Excluded traffic cannot be recovered. Events from excluded IPs are permanently dropped at the edge and are not available in the dashboard, exports, or any reporting.
Supported formats
| Format | Example | Description |
|---|---|---|
| Single IPv4 | 203.0.113.42 | Excludes one specific IP address |
| IPv4 CIDR range | 10.0.0.0/24 | Excludes all 256 addresses in the 10.0.0.0 - 10.0.0.255 range |
| Single IPv6 | 2001:db8::1 | Excludes one specific IPv6 address |
IPv4 CIDR ranges are fully supported. For IPv6, only single addresses are supported at this time -- IPv6 CIDR ranges are not yet available.
Configuration
Open IP exclusions settings
Navigate to Settings -> IP Exclusions tab in your project settings.
Add an IP or CIDR range
Click Add Exclusion and enter:
- IP address or CIDR range -- the address or range to exclude
- Label (optional) -- a human-readable name, for example
"CEO Office","Dev Network", or"QA Lab"
Use the "Add my IP" shortcut
Click the Add my IP button to automatically detect and add your current public IP address. This is useful for quickly excluding your own traffic during development or testing.
Save
Click Save to apply the exclusion. It takes effect immediately for all new incoming events.
How it works
Incoming Event
│
▼
IP Check ──→ IP in exclusion list? ──→ Yes ──→ Event dropped (permanently)
│
└──→ No ──→ Event processed normallyIP exclusion happens at the earliest stage of the ingest pipeline, before any processing, storage, or forwarding occurs. This means:
- Excluded events do not count toward your event volume
- Excluded events are not visible in the dashboard
- Excluded events are not forwarded to ad platforms
- Excluded events are not included in exports or reports
Use cases
- Development traffic -- Exclude your office or development network to prevent internal pageviews and test conversions from polluting production data.
- QA testing -- Exclude QA team IPs so automated test conversions are not tracked.
- Executive traffic -- Exclude specific IPs to prevent internal stakeholder browsing from appearing in analytics.
- Partner traffic -- Exclude agency or partner IPs if their visits should not be counted.
Example exclusion list
| IP / CIDR | Label |
|---|---|
203.0.113.42 | CEO Office |
10.0.0.0/24 | Dev Network |
198.51.100.0/28 | QA Lab |
2001:db8::1 | Remote Developer |
Permissions
Adding, editing, or removing IP exclusions requires the project owner or admin role.
Important notes
- IP exclusions are a per-project setting. Each project has its own exclusion list.
- Changes take effect immediately for all new events. Events that were already ingested before the exclusion was added are not affected.
- There is no "undo" for dropped events. If you need to temporarily include internal traffic (for example, during a test), remove the exclusion first and re-add it afterward.