Purpose of Filters
Filters help distinguish wanted traffic from unwanted traffic. The decision can take into account country, IP, device, browser, source, language, User-Agent, repeat clicks, suspicious signals, and additional query parameters.
Popular Rule Groups
| Group | Example Use |
|---|---|
| Geography | Allow only selected countries or exclude specific regions. |
| Devices | Separate mobile and desktop traffic. |
| Sources | Check utm_source, referrer, or campaign parameters. |
| IP & Networks | Restrict suspicious addresses, data centers, or frequent repeat clicks. |
| Behavior | Account for click frequency and repeat visits. |
How to Configure Safely
- 1
Enable rules gradually.
- 2
After each change, review the last 10–20 clicks.
- 3
Check not only the final decision but also the reason.
- 4
Compare statistics before and after the change.
- 5
Save successful rule sets as presets if that feature is available.
Decision Reasons
The click log shows the reason explaining why a visitor was passed or filtered. If the reason is unexpected, check the corresponding filter, the click's input parameters, and the selected time period.
A filter should solve a specific problem. Don’t enable a rule just because it exists in the interface.