Why exclude IP addresses
Internal team activity can distort analytics. Excluding IP addresses helps keep reports focused on real visitors instead of staff, developers, agencies, or QA testers.
Use IP exclusions for:
- office networks
- developer testing locations
- agency teams
- client review teams
- automated monitoring where applicable
Find the IP address to exclude
Use a trusted "what is my IP" service from the network you want to exclude. If the office has multiple networks or VPNs, collect each public IP address.
Be careful with home networks and dynamic IP addresses. Some internet providers change IPs regularly, so exclusions may need updates.
Add IP exclusions
Open the website settings and add the IP addresses that should be excluded from recording.
Use one IP address per entry. If your account supports ranges, only add ranges you understand and control.
After saving, create a test visit from that network and confirm it no longer appears in new sessions.
What IP exclusions affect
IP exclusions should apply to new tracking activity after the setting is saved.
They do not usually remove historical sessions that were already recorded before the exclusion was added.
Use with other controls
IP exclusions work best with:
- privacy masking
- consent-aware loading
- excluding sensitive pages
- avoiding tracker installation on staging sites
Do not rely only on IP exclusion for privacy. Visitors can use shared networks, VPNs, mobile networks, or changing IP addresses.
Troubleshooting
If excluded traffic still appears:
- confirm the visitor is using the excluded network
- check whether a VPN changes the public IP
- confirm the exclusion was saved on the correct site
- wait for new sessions rather than checking old sessions
- check whether the browser is using a proxy or mobile network