Filtering Rules
Rules determine what to do with traffic that matches specified conditions. You define the criteria — the system automatically applies the action to every matching visit.
How It Works
Each rule consists of two parts:
- Conditions — what visit characteristics trigger the rule
- Action — what to do with such a visit
Format: IF [conditions] THEN [action].
Example:
IF country = CN AND traffic_signal_name = proxy_like THEN Show ChallengeConditions
Conditions are built from visit fields. Dozens of fields are available: country, city, browser, device, proxy type, traffic signals, sub parameters, flags (webview, iframe, adblock), and more. For string fields you can use operators: equals, not equals, contains, in list, regular expression.
Conditions can be combined into groups with AND / OR logic:
- Within a group: all conditions must match (AND) or at least one (OR)
- Between groups: the same applies
This allows you to build complex rules:
(country = RU AND traffic_signal_name = proxy_like) OR (is_crawler_ua = true)Actions
| Action | When to use |
|---|---|
| Flag as GIVT | Traffic is clearly invalid — flag it and see it in statistics |
| Flag as SIVT | Suspicious invalid traffic, such as probable device spoofing |
| Send to Traffic Back | Send fraud back — redirect to the URL specified in the integration |
| Show Challenge | Verify the visitor with an interactive test before granting access |
Challenge
Partial verification
When selecting "Show Challenge", you set the percentage of visits that will receive the verification (challenge rate). You do not have to check 100% — you can show the challenge to, say, 30% of suspicious visits to avoid degrading the experience for everyone.
Linking to Integrations
A rule is not automatically applied to all traffic. You link rules to specific integrations in the integration settings. There you also set the order of application — rules are evaluated sequentially.
This allows you to have different rule sets for different traffic sources.
Access
Rule management is available only to the account owner (Owner).
What's next
- Handle Fraudulent Traffic — practical rule examples
- Set Up a Challenge — soft verification instead of blocking
- Integrations — linking rules to traffic sources