How TrafficFilter decides what each visitor sees

A short walkthrough of the PHP connector, the decision API, the filters it checks, and what happens to each visitor.

When someone clicks your ad, TrafficFilter decides what that visitor sees: your offer or a safe page. Here is how that decision is made.

The connector asks, the API decides

You put a PHP connector (index.php) on your site. On each visit, the connector asks the TrafficFilter decision API what this visitor gets, and then serves the answer.

What the filters check

  • Bots, and visitors coming from datacenter, hosting or VPN networks.
  • IPs on the fraud blacklist.
  • Your allow and block lists for country, language, device, OS, browser and ISP.
  • Your advanced AND/OR rules on user agent, Accept-Language, query string, referrer and ISP.

IPs on your whitelist are always let through.

Two possible outcomes

A visitor caught by a filter sees the safe page: an HTML page you uploaded, one generated with AI or from a template in the dashboard, or your own page. Every other visitor is redirected to your offer, or the offer is shown in an iframe.

Check your rules before you spend

The dashboard has a rule tester, so you can check how a visit would be handled before sending traffic. Per-link stats show clicks and blocked visits for the last 7 and 30 days.