Skip to content

Handle Fraudulent Traffic

You have identified a fraud source and want to automatically handle that traffic. Adsafee does not block visits directly — it classifies them, and you decide what to do: flag, redirect to traffic back, or show a challenge.

Example: Proxy Traffic from a Specific Country

You have determined that fraud is coming from China through proxy servers.

1. Create a Rule

Go to Rules > Add Rule.

2. Set Up Conditions

Create a condition group with AND logic:

FieldOperatorValue
geo_countryequalsCN
is_proxyequalstrue

This means: the rule will trigger when a visit is both from China AND through a proxy.

3. Choose an Action

ActionWhat happens
Flag as GIVT / SIVTThe visit will be flagged — you will see this in statistics, but the visitor stays on the site
Send to Traffic BackThe visitor will be redirected to the URL specified in the integration settings
Show ChallengeThe visitor will see a verification check. If they pass — they stay; if they fail — they won't reach the site

4. Attach to an Integration

A rule does not work on its own. Go to the settings of the relevant integration, add the rule to the list, and save.

Other Common Scenarios

Flag crawlers

Condition: is_crawler_ua equals trueAction: Flag as GIVT Crawlers will appear in statistics as GIVT.

Send webview traffic to traffic back

Condition: is_webview equals trueAction: Send to Traffic Back Visitors from in-app embedded browsers will be redirected.

Show a challenge to proxy traffic

Condition: is_proxy equals trueAction: Show Challenge Real users behind a VPN will pass the check; bots will not.

Flag a trusted source as clean

Condition: sub1 equals trusted_partner_idAction: Flag as Good

Caution

The "Flag as Good" rule overrides automatic classification. Use it carefully and only for sources you are confident about.

What's Next

Adsafee — Ad Traffic Fraud Protection