Traffic Filtering

Overview

Traffic filtering allows you to exclude certain visitors from your analytics data. This is essential for:

• Excluding your own visits while developing or testing
• Filtering out known bot traffic
• Blocking traffic from specific countries
• Removing spam referrers
• Excluding office or team IP addresses

IP Blocking

Block specific IP addresses or ranges from being tracked.

Supported Formats

Adding Blocked IPs

1. Go to your site's Settings page
2. Find the "IP Blocking" section
3. Enter an IP address or range
4. Click "Add IP"
5. Save your settings

# Block your home IP
98.234.56.78

# Block your office network
10.0.0.0/8

# Block a range of IPs
203.0.113.0/24

# Block with wildcards
192.168.1.*

Finding Your IP Address

To find your current IP address:

1. Search "what is my IP" in any search engine
2. Or use a service like ifconfig.me
3. Note: Your IP may change if you don't have a static IP

Country Blocking

Block all traffic from specific countries using ISO country codes.

How It Works

When country blocking is enabled:

1. We determine the visitor's country using IP geolocation
2. If the country matches a blocked code, the pageview is not recorded
3. The visitor still sees your website normally

Adding Blocked Countries

1. Go to your site's Settings page
2. Find the "Country Blocking" section
3. Select countries to block from the list
4. Or enter ISO country codes (e.g., RU, CN)
5. Save your settings

Common Country Codes

Important Considerations

Filtering is Immediate

Once you add an IP or country to your block list:

• New pageviews from blocked sources are not recorded
• Historical data is not affected
• Changes take effect immediately

Filtering Does Not Block Access

Traffic filtering only affects analytics collection:

• Blocked visitors can still access your website
• They just won't appear in your analytics
• For actual access blocking, use your web server or CDN

VPN and Proxy Considerations

Be aware that:

• Users with VPNs may bypass country blocks
• IP blocking works on the visible IP, not the actual origin
• Proxy servers may cause different IP addresses

Best Practices

• Block development traffic: Add your office and home IPs to exclude internal visits
• Use CIDR for networks: Block entire office networks with CIDR notation
• Document your blocks: Keep notes on why each IP/country is blocked
• Review periodically: Remove outdated blocks when no longer needed
• Don't over-block: Only block what's necessary to keep data clean

API Access

Manage traffic filters via API by updating site settings:

PUT /sites/{site_id}

{
  "blocked_ips": [
    "192.168.1.100",
    "10.0.0.0/8"
  ],
  "blocked_countries": [
    "CN",
    "RU"
  ]
}