Bot filtering
Four independent signals score every click — ASN reputation, TLS fingerprint, headless indicators and request cadence. A verdict lands in 7.2 ms at p95.
Roughly one click in six that reaches a funnel is a scraper fleet, a compliance sweep or a rented residential proxy. CloakShield Pro scores each one at the edge in 7.2 ms and passes only the real ones through to Cloaking House, Keitaro, Voluum or whatever you route with today.
CloakShield scores the request, resolves the real geography and checks the landing page is still the page you published — then hands the visitor to your existing flow untouched.
Four independent signals score every click — ASN reputation, TLS fingerprint, headless indicators and request cadence. A verdict lands in 7.2 ms at p95.
Country, region and carrier resolved from GeoIP2 and an ASN lookup, then cross-checked against language and timezone. A mismatch is marked proxied, not trusted.
Every landing page is fetched from 30 vantage points each minute and diffed against what you published. Injected scripts and dead offer links raise an alert with the diff.
Response-level masking rotates class names and DOM structure per session, so competitive-intelligence crawlers and spy tools cannot fingerprint your templates.
Click parameters — sub1–sub10, clickid, cost — are forwarded verbatim and postbacks replayed in the format your platform already accepts.
One CNAME and an API key, or a single script tag if you would rather not touch DNS. Rolling back is deleting the record — we hold no campaign state of our own.
Add one CNAME for your campaign domain. Your router keeps its address and its rules — nothing is migrated.
Every click is scored at the nearest edge PoP. A verdict lands in 7.2 ms at p95, and a timeout passes the visitor through.
Clean traffic reaches your platform with parameters untouched and the verdict attached, so existing flows decide as they do now.
Landing pages are diffed every minute against the version you published, and tampering raises an alert with the diff attached.
Every scored click with the signal that decided it, the integrity state of each landing page, and the latency you are paying for it.
Sample workspace, populated with representative traffic. Open the full walkthrough.
Cloaking House, Keitaro, Voluum and the rest keep every campaign, flow, stream and offer where it is today. There is no migration step to plan.
Point the campaign domain at a CloakShield edge PoP and leave Cloaking House as the decision layer behind it. The verdict travels as request headers — x-cs-score, x-cs-asn, x-cs-geo — alongside the untouched query string, so your white-page and offer rules read an enriched request instead of a bare IP.
Campaigns, streams and offer IDs import over /admin_api/v1/campaigns, so identifiers map one-to-one instead of being retyped into a second console. Conversions are replayed to the postback URL you already have on file, in the format Keitaro accepts. Self-hosted and cloud instances behave identically.
CloakShield answers on your tracking domain and hands the visitor to Voluum's redirect endpoint with cid intact, so click IDs, cost data and the conversion chain still reconcile at the end of the day. Traffic source templates, path weights and offer caps stay configured in Voluum.
Binom runs on your own server, so the filter sits in front of that server rather than in front of a vendor. Campaign and landing IDs import over the public API on your instance, and the click is handed on with clickid and every &s1..s20 token untouched, which is what keeps Binom's own reports whole.
An API key is enough to pull offers, sources and campaigns across. Filtered clicks are reported back through RedTrack's conversion API with a cost of zero and a status that marks them as rejected, so the traffic never inflates a payout report while still leaving an audit trail against the source that sent it.
Traffic routing platforms
Traffic sources, infrastructure and alerting
CloakShield holds no campaign state of its own. Nothing is exported into it, so removing it is deleting one DNS record — your platform is still the system of record the next morning.
Every plan includes bot filtering, geo resolution and landing page monitoring. What changes is volume, how many domains you run, and how fast someone answers you.
Billed monthly · cancel anytime
For one buyer running a handful of campaigns on a single domain.
Billed monthly · cancel anytime
For media buyers running several offers across more than one traffic source.
Billed monthly · cancel anytime
For teams buying at volume who need custom rules and a named engineer.
Plans are activated from inside the workspace. Create an account, confirm your email address, and the plan you picked here is waiting on the billing screen — payment is in BTC, ETH, SOL or USDT.
Two or three months takes 10% off the list price. Six months takes 15%. Twelve months is our annual rate at 20% off — $1,440, $3,360 or $4,800 depending on plan.
Effective $350.00 per month
About a fifth of what one push source billed us had no browser behind it at all. The ASN pattern was obvious inside a week, and we cut the source before the next invoice cleared.
Our host pushed an analytics script into four landers without telling anyone. We heard about it from a DOM diff at 03:40, not from a conversion dip three days later.
I was ready for the latency argument with our buying team. We measured 6.9 ms at p95 on the redirect path, which was quiet enough that nobody brought it up again.
navigator.webdriver and canvas hash collisions, and request cadence per /24. Thresholds are yours to tune, and every verdict is logged with the signal that decided it, so you can audit a call you disagree with.Traffic questions rarely fit a ticket form. Reach us however suits — most replies land well inside 24 hours.
A single CNAME, one live campaign, and a week of scored clicks tells you more than any deck. Your router keeps running exactly as it does today.