← All guides
Proxy & VPN detection

Voluum fraud filter: proxy and VPN detection with a redirect gate

Voluum's Anti-Fraud Kit reports suspicious visits but cannot score a click against an API. Add a FraudNova gate to your path and block before the offer.

Published

Voluum runs in the cloud ("All plans have cloud-based tracking"), so there is no server of its own for you to extend. Its Anti-Fraud Kit reports which visits look suspicious. What it does not do is ask an outside service about each visitor and act on the answer before the offer loads. This guide adds that step with a self-hosted redirect gate used as the campaign's lander.

For the longer explanation of the gate, and how Voluum compares with Keitaro, Binom and RedTrack, read the overview of fraud filtering for affiliate trackers. This page covers only what is specific to Voluum.

Voluum reports suspicious traffic; blocking is a separate job

The Anti-Fraud Kit looks for patterns such as "abnormally fast or frequent clicks, poor referrer reputation, unrecognized user agent", and it adds a honeypot to catch bots. Traffic it flags "is considered to be suspicious" and is marked that way in Voluum's reports; flagging on its own does not stop a visit.

To act on traffic, Voluum gives you two tools:

  • IP/UA filtering. Voluum can filter traffic by IP address and user agent.
  • Rule-based paths. Voluum's FAQ says you can "re-route it in Voluum with Rule-based paths". A path rule can match on country, language, day of week, time of day, connection type, device type, city, region, mobile carrier, ISP, device brand and model, OS, browser, referrer, custom variables, visit uniqueness, an IP rule, and a Proxy rule, described as "Filter out traffic that uses various types of proxy solutions".

The documentation does not explain how the Anti-Fraud Kit's flags turn into path conditions, and none of the conditions above calls an external URL or reads a fraud score. So the per-visitor score has to come from somewhere else. A FraudNova check on the visitor's IP returns a fraud_score from 0 to 100 and flags such as proxy, vpn, tor and bot_status; the proxy and VPN detection API page lists every field.

The one native hook: Redirect Webhook

Voluum does have a feature built for this kind of decision. With the Redirect Webhook, "Voluum's backend will make an HTTP request to your server when a campaign URL is activated", and "Your server should send a correct response with a landing page or offer page address". You set the URL under Settings, on the Redirect Webhook tab (the URL may carry tracking parameters), and switch it on per campaign in the DESTINATION tab under Routing callbacks, either for the whole campaign or for selected paths. Two limits matter: "The time windows for the response is 1 second", and if your server misses it, the visitor goes to the campaign's fallback destination. Voluum describes the feature as an "enterprise-grade expansion".

We cannot give you a ready-made setup here, because Voluum's documentation does not publish the request or response format. FraudNova does not offer a Redirect Webhook integration today. If you have access to the feature, ask Voluum support for the exact format: the gate's decision function, decide(), is a separate unit in both versions of the gate, so it can answer that request once Voluum gives you the format. Voluum's 1-second window is shorter than the gate's default 2-second timeout, though, so a webhook responder built on decide() would need timeout_ms well under 1,000 and a cached verdict path. Everyone else can use the lander route below.

The gate in four sentences

The gate is an open-source redirect script in the tracker gate folder of our examples repo, in PHP (gate.php, PHP 8.2 with Composer) or Node.js. It checks the IP the visitor really connects from, along with their User-Agent and Accept-Language, and ignores any IP passed in the URL. It blocks at a score of 75 or more, or when proxy, vpn, tor or bot_status is true (you can change all of that, opt in to active_vpn, and set allowed_countries), then sends a 302 to your money URL or safe URL with the query string attached. Verdicts are cached per IP for 24 hours, a check gets 2 seconds, and if the API errors or times out the click goes through.

Put the gate in a Voluum path

Deploy the gate and fill in its config: your FraudNova API key (fn_..., from 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 Voluum:

  1. Under Landers, create a new lander with the gate as its URL:

    https://gate.example.com/gate.php?clickid={clickid}&route=default
    
  2. In the campaign, set the path to Lander → Offer, with the gate lander in the lander slot and your offer where it was.

  3. Do not touch the call-to-action on your real lander. It keeps pointing at Voluum's click URL, https://TRACKING-DOMAIN/click (or /click/1, /click/2, /click/3 for a lander with several offers), so the visitor still passes through Voluum on the way to the offer.

Voluum says of its tokens: "Once the HTTP link is activated, these tokens are replaced with concrete values." Its docs do not show a lander URL with {clickid} in it, so check before you send real traffic: open the campaign URL once and confirm the gate logged a real click id, not the literal {clickid}. You do not need {ip}, {useragent} or {language} in the URL; the gate reads those from the visitor's request.

Count blocked clicks as a custom conversion

A blocked visitor stops at the gate, so you should see the visit in Voluum but no click through to the offer. To count those visitors, record them as a custom conversion:

  1. In Settings, open the Custom conversions tab and create one called blocked. Voluum says "the value paired with the et parameter has to match the value created inside Voluum", so use exactly that name.

  2. Set the gate's report_url to your postback, where cid carries Voluum's click id:

    https://TRACKING-DOMAIN/postback?cid={clickid}&et=blocked
    

The gate calls it once per blocked click, with {clickid} filled in, and never for an allowed one.

Let the Anti-Fraud Kit tell you where to set the threshold

In Voluum, if your plan includes the Anti-Fraud Kit, you get a second opinion: the kit keeps reporting suspicious visits while the gate does the blocking. Use one to tune the other. The bands are 0–39 clean, 40–74 suspicious and 75–100 high risk, and the default of 75 is where the high-risk band starts.

  • The kit still flags much of the traffic the gate lets through. The gate is too lenient for this source. 65, then 60, are starting points to test.
  • The blocked count is high but the kit's suspicious share barely moved. You may be blocking visitors the kit considers fine. Go back up toward 75, or check which flag does most of the blocking.
  • Both agree. Leave it alone.

Give each change a few days. The fraud score thresholds guide explains the bands in more detail.

Voluum events and FraudNova credits

Your Voluum plan is sized by events; FraudNova charges 1 credit per check. They are separate budgets, and the gate's cache keeps the FraudNova one below your visit count. Say a campaign sends 10,000 visits a day from 6,000 distinct IPs. The gate checks each new IP once a day, so that is about 6,000 credits, and the 4,000 repeat visits reuse a cached verdict at no charge. If you route Proxy rule matches to a path with a different lander, those visits never reach the gate and cost no credits.

On the Voluum side, ask Voluum how your plan counts events for the extra lander step and for the blocked postbacks before you roll the gate out widely. New FraudNova accounts get 25 free credits after email verification, credits come in prepaid packs with no subscription, and the rate limits are in the API docs.

Rollout, step by step

  1. Paste an IP from a recent Voluum visit into the free IP checker to see the verdict the gate would act on.
  2. Create an account, copy an API key, and deploy the gate.
  3. Add the gate as a lander and the blocked custom conversion, on one campaign only.
  4. After a few days, put the blocked count next to the Anti-Fraud Kit's suspicious visits for that campaign and adjust the threshold.
  5. Copy the gate lander into your other campaigns once the numbers look right.

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