Skip to content

Anti-fraud

Keep bots out of your numbers.

Capve flags suspicious clicks before they reach an offer. Route them like everyone else, or send them to a safe page, and judge your sources on human traffic.

Account blocklist

Block IP addresses, CIDR ranges, ASNs and user-agent substrings once, for every campaign.

Datacenter ASN flag

Optionally treat clicks from hosting and cloud networks as bots.

Safe page

Per campaign, send flagged clicks to a safe page instead of your lander and offer.

Bot column in reports

Bots are counted, not hidden. See which zones send them, then blacklist those zones.

How a click gets flagged

Each click is checked against your blocklist and, if enabled, the datacenter-ASN list. A match sets is_bot on the click. The campaign's bot action then decides what happens: keep routing, or redirect to the safe page.

Rules can use the bot flag too

Bot is one of the routing conditions, so you can build a separate path for flagged traffic and still measure it.

Close the loop with zone blacklists

Automation rules blacklist zones that send clicks but no conversions. Export the list as TXT or CSV and paste it into the traffic source.

FAQ

Bot filtering: questions

Does Capve use a third-party bot database?
No. Capve uses your own blocklist, an optional datacenter-ASN check and the signals in each request. There's no external lookup, so no added latency or per-check fee.
Do bot clicks count against my plan?
Yes. Every recorded click counts, bots included, because Capve still has to process and store it.

Bring your casino affiliate tracking together.

14-day free trial with every feature. No card, no server, no sales call.