IP exclusions

IP exclusions filter out traffic from specific IP addresses or CIDR ranges. Events from excluded IPs are dropped before ingest: they are never stored, never shown in the dashboard and never forwarded to ad platforms.

Excluded traffic cannot be recovered. Events from excluded IPs are permanently dropped at the edge and do not appear in the dashboard, exports or any report.

Supported formats

IPv4 CIDR ranges are fully supported. For IPv6, only single addresses are supported at this time.

Adding an exclusion

1. Go to Settings → Tracking → Excluded IPs.
2. Type the IP address or CIDR range into the field at the bottom of the list, add an optional label such as “Head office”, “Dev network” or “QA lab”, and click Add.
3. Or click Add my IP to detect and add your current public address in one step. Useful when you are testing from your own machine. The row is labeled This device.

There is no Save button. Each addition or removal is saved as soon as you make it and applies immediately to new events. To remove an entry, click the × at the end of its row.

How it works

Incoming event
      |
      v
  IP check --> IP in exclusion list? --> Yes --> Event dropped (permanently)
      |
      +--> No --> Event processed normally

The check runs at the earliest stage of the ingest pipeline, before any processing, storage or forwarding. So excluded events:

• do not count toward your plan’s conversion limit
• are not visible in the dashboard
• are not forwarded to ad platforms
• are not included in exports or reports

Use cases

• Development traffic. Keep internal pageviews and test conversions out of production data.
• QA testing. Stop automated test conversions being tracked.
• Stakeholder browsing. Keep internal visits out of analytics.
• Partner traffic. Exclude agency or partner IPs if their visits should not count.

Example list

Permissions

Any project member can add or remove exclusions. Viewers cannot.

Good to know

• Exclusions are per project. Each project has its own list.
• Changes apply to new events only. Events already ingested are unaffected.
• There is no undo for dropped events. To include internal traffic temporarily, remove the exclusion first and add it back afterward.
• Testing from an excluded IP is a common reason a test conversion never appears. See Troubleshooting.