Traffic Filters

Traffic filters control which visitors' data gets processed and sent to your ad platforms. Filter out bots, irrelevant geographies, and specific IP addresses to keep your conversion data clean.

Accessing Traffic Filters

1. Go to Configuration in the sidebar
2. Select your domain
3. Click the Traffic Filters tab

Plan Availability

Features not available on your plan show an upgrade prompt.

Bot Filtering

Bot filtering is enabled by default on all plans. It blocks known bots, crawlers, and automated traffic from being counted as conversions.

Basic Bot Filtering (All Plans)

• Known bot blocking: Automatically filters traffic from recognized bots (Googlebot, Bingbot, etc.) using a database of 45+ known bot patterns
• This runs silently, no configuration needed

Advanced Bot Filtering (Signal+)

• Bot score threshold: Set a value between 1 and 99. Each visitor gets a bot score where a lower score is more bot-like, so CleanClicks blocks visitors whose score falls below your threshold -- a higher threshold blocks more aggressively. There is no default; leave it unset to skip score-based filtering.
• Custom blocked UA patterns: Add your own user-agent patterns to block. Useful for filtering proprietary crawlers or monitoring tools that your analytics shouldn't count.

Adding Custom UA Patterns

1. In the Bot Filtering section, find Custom Blocked User Agents
2. Enter a pattern (e.g., SemrushBot or AhrefsBot)
3. Click Add
4. Save your configuration

Patterns are matched against the visitor's user-agent string. Partial matches work: Semrush will match SemrushBot/7.0.

Geographic Filtering

By default, CleanClicks filters to US visitors only. A US-only geo allowlist is applied on every plan whenever you haven't configured geo yourself. To accept traffic from other countries (or turn geo filtering off), edit the country list below -- country-level geo customization is available on every plan. Filter traffic based on the visitor's country:

How It Works

You choose a mode and a list of countries:

• Allowlist mode: Only visitors from the listed countries are processed. Everyone else is filtered out.
• Blocklist mode: Visitors from the listed countries are filtered out. Everyone else is processed.

Setting Up Geo Filtering

1. Enable Geo Filtering toggle
2. Choose Allowlist or Blocklist mode
3. Add countries using their two-letter country codes (e.g., US, CA, GB, AU)
4. Save

Common Configurations

• US-only business: Allowlist with US
• North America: Allowlist with US, CA
• Block known bot-farm countries: Blocklist mode with specific countries

Geographic filtering happens before conversion processing, so filtered traffic doesn't count toward your session limit or get sent to ad platforms.

IP Filtering

Available on Signal plans and above. Filter specific IP addresses or ranges.

Modes

• Blocklist: Block specific IPs (e.g., your office IP to exclude internal traffic)
• Allowlist: Only allow specific IPs (rare, but useful for testing)

Adding IPs

1. Enable IP Filtering toggle
2. Choose Blocklist or Allowlist mode
3. Enter IP addresses (one per line)
4. Save

Supports individual IPs (e.g., 203.0.113.50). Useful for filtering your own office traffic, known spam sources, or competitor IPs.

Origin Filtering

Control which referrer origins are allowed to send data. This prevents unauthorized domains from sending events through your CleanClicks subdomain.

Add allowed origins as full domain names. If you don't configure any, CleanClicks accepts events only from your own domain (https://yourdomain.com and https://www.yourdomain.com). Add an origin here to also accept events from a subdomain (e.g. app.yourdomain.com) or another trusted source.

How Filters Stack

Filters are applied in order. A request must pass all active filters to be processed:

1. Bot filter — known-bot and non-browser user agents are blocked first.
2. IP filter — if you've set an IP allowlist/blocklist, it's checked next.
3. Geo filter — the visitor's country is checked against your allowlist/blocklist (US-only by default).
4. Origin filter — the request origin is checked at the endpoint.

Traffic that's filtered out is not counted toward your session limit, not sent to ad platforms, and doesn't appear in your conversion data. Filtered requests are still logged in traffic analytics (on Signal+ plans) so you can see what's being blocked.

---

Next: Ecommerce