← All guides
Proxy & VPN detection

Binom fraud filter: proxy and VPN detection for every click

Binom rules can route on a proxy flag or a GET value, but cannot call a scoring API. Put a FraudNova gate in front of your lander and route by the result.

Published

Binom is a tracker many affiliates run on their own server (Binom v2), with Binom Cloud as the hosted option. Its campaign rules route clicks, but they cannot ask an outside service about each visitor. This guide shows how to put a FraudNova check in front of your lander, so proxy, VPN, Tor and bot traffic lands on a safe page and everyone else carries on with their Binom click id intact.

If you run more than one tracker, our overview of fraud filtering for affiliate trackers compares all four and explains the shared setup in more depth.

What Binom gives you, and where it stops

Binom's campaign Rules can route a click on a long list of criteria. Three of them matter here:

  • Proxy-traffic. A rule that matches clicks Binom considers proxy traffic. The documentation does not say what that judgement is based on.
  • Bot. Binom describes this as a "Bot checker with MagicChecker or Adspect", and offers Binom Protect as its own in-house option.
  • GET. A rule that matches on a value in the URL's GET parameters. Rules can also match on tokens, the IP, the ISP, the language and more.

There is no rule that sends the click to an external API and branches on the answer. So Binom can act on a verdict, but it cannot fetch one for you. A FraudNova check on the visitor's IP returns a fraud_score from 0 to 100 plus flags such as proxy, vpn, tor and bot_status; the proxy and VPN detection API page lists every field. The job is to get that check into the click path.

The gate, in short

The gate is a small redirect script you host yourself. You will find it in the tracker gate folder of our examples repo, in two versions: PHP (gate.php, which needs PHP 8.2 and Composer) and Node.js.

The gate scores the IP of the visitor's own connection (with the User-Agent and Accept-Language headers), never an IP from the query string, so a ?ip= in the link is ignored. It blocks at a fraud_score of 75 or above, or when proxy, vpn, tor or bot_status is true; the number, the flags, an opt-in active_vpn and an allowed_countries list are all set in its config. Either way it answers with a 302, to your money URL or your safe URL, carrying the incoming parameters along so Binom's clickid survives the hop. Verdicts are cached per IP for 24 hours, a check gets 2 seconds, and if a check fails (no credits, a rate limit, a 503, a timeout) the click is allowed by default.

Set up the gate in Binom

Upload the gate to your server and fill in its config: your FraudNova API key (it starts with fn_ and is created under Dashboard, API keys) and a default route with your real lander as the money URL and a harmless page as the safe URL.

Then, in Binom:

  1. Open your campaign and go to its landers. Enter the gate as the lander URL:

    https://gate.example.com/gate.php?route=default
    
  2. In the campaign settings, find Append to lander's URL. Binom says it "adds the given list of parameters to all of the campaign's landings", and that "All tokens are available". Add:

    clickid={clickid}
    

Binom replaces {clickid} with the click's id before the visitor arrives, so the gate receives something like https://gate.example.com/gate.php?route=default&clickid=.... You could append {ip}, {user_agent} or {language} the same way, but the gate does not need them: it reads those from the visitor's own request, which is the safer source.

Your lander does not change, as long as its buttons already point at Binom's Click URL. Its link to the offer is still Binom's regular Click URL, which still redirects the visitor through Binom on the way to the offer, exactly as it did before the gate. Binom requires that Click URL to use the same domain as the campaign, so keep the domain you already use.

A Click API lander, if you prefer

Binom's Click API is a PHP snippet, copied from Settings → Click API, that sits at the top of a .php lander and must call sendBaseClick(). A lander built this way could score the visitor before that call and, for a risky visitor, link to a safe page instead of the address getOfferUrl() returns. It keeps everything on one server, but you maintain the code yourself, and Binom notes the Click API is not compatible with MagicChecker. For most campaigns the gate is less work.

Report blocked clicks back to Binom

A blocked visitor never reaches the lander, so Binom never hears of them. Point the gate's report_url at a Binom postback:

https://TRACKER/click.php?cnv_id={clickid}&event10=1

Binom takes events 1 to 10 as GET parameters here. Event 10 is free of conflicts: the e-commerce status scheme reserves 1 to 5, the subscription scheme 5 to 8. Binom then counts blocked clicks per source.

Want a status as well, like &cnv_status=blocked? Status names belong to your account (Settings → Stats → Status scheme), so add a blocked status there before using it.

Binom's proxy rule, the gate, and the threshold

In Binom a rule sends its matches to its own path, and a path holds its own landers. So if the Proxy-traffic rule's path uses a different lander, those clicks never reach the gate and spend nothing. That gives you two setups, and a starting threshold for each (the bands are 0–39 clean, 40–74 suspicious, 75–100 high risk):

  • Proxy-traffic rule in front of the gate. Binom's own rule takes the clicks it recognises, and the gate scores the rest. Start the gate at 75 and watch the event 10 column: a count near zero suggests the rule already catches most of what the gate would block.
  • Gate alone. Every click goes through the gate, so its verdict is the only one. Start at 75 for geo-restricted offers, where allowed_countries does part of the work, and at 85 for high-volume, cheap traffic where you only want the worst gone.

The fraud score thresholds guide explains how to move the number once you have a few days of data.

What it costs on a Binom campaign

Take a campaign that gets 2,000 clicks a day from about 1,400 different IPs. The gate checks each IP once, so that day costs about 1,400 credits at 1 credit per check; the other 600 clicks are repeat visits from IPs it has already scored and cost nothing. Clicks your Proxy-traffic rule sends to its own path are not counted at all when that path uses a different lander. New accounts start with 25 free credits after email verification, and the per-key rate limit and concurrent-check cap (raisable on request) are in the API docs.

Next step

Before you start, paste an IP from a recent Binom click into the free IP checker to see the kind of verdict the gate will act on. Then:

  1. Create an account for an API key, deploy the gate, and add it as the campaign's lander with clickid={clickid} in "Append to lander's URL".
  2. Send one campaign's traffic through it and leave the others as they are.
  3. After a day, open that campaign's Binom report and read the event 10 count to see how many clicks the gate turned away.

Try it free

Run one IP proxy check right now — no account, no card.

Try the free IP proxy checker — no signup See the Proxy & VPN detection API

Also read