What Cloaking X does
Cloaking X sits in front of your ad landing pages and decides, in real time, whether the visitor arriving from your ad is a real prospective buyer or invalid traffic — bots, scrapers, VPN/datacenter IPs, and the ad platform's own review crawlers.
Money page vs. safe page
Every stream (one per landing page / campaign you protect) is built around two kinds of destination:
Your real offer — where visitors who pass the check are sent. A stream can hold multiple destination pages (called moneyPages in the API), rotated randomly, sequentially, or on a timer, plus optional per-OS overrides for iOS/macOS, Windows, and Android.
A compliant, policy-safe page shown to visitors who get blocked — bots, reviewers, low-quality traffic. It's always delivered as a direct render rather than a redirect (never a 301/302 to it), by design. If no fallback page is configured, a blocked visitor simply isn't redirected anywhere.
The visitor flow
Visitor clicks your ad and lands on your page
The integration snippet (see Integration Guides) is already installed there — client-side JS, a WordPress plugin, a server-side PHP snippet, or a native Keitaro filter.
The snippet calls the Cloaking X check
It sends the visitor's IP, User-Agent, and (for browser-based integrations) a fingerprint payload to /api/check along with your stream ID and any click-tracking parameters (gclid, fbclid, UTMs) present on the URL.
Cloaking X evaluates the visitor
IP intelligence (datacenter/VPN/Tor/bot status), your blacklist/whitelist, allowed countries/OS/devices, and browser/fingerprint integrity checks are combined into a single risk score and compared against your stream's threshold. See the Block Reason Reference for the full list of what can trigger a block.
The visitor is delivered to the right page
A visitor who passes is sent to a destination page, delivered using the stream's configured Money Page Delivery method. A blocked visitor is sent to the fallback page, if one is set.
Every check is logged
Passed and blocked decisions both appear in Reports, with a block reason attached whenever the decision was "blocked". A few gates (covered in the FAQ) skip logging entirely by design — worth knowing before you assume a missing row means something broke.
The four stream modes
Each stream runs in one of four modes:
Full enforcement. Blocked visitors are sent to the fallback page (or left where they are, if none is configured) — they never reach your destination page.
Observe mode. Every visitor is scored and a block reason is still recorded in Reports for anyone who would have been blocked — but everyone is still delivered to the destination page. Useful for tuning your threshold before you flip a stream to full enforcement. High-confidence bot reasons (datacenter, vpn, ua_bot, headless) are also auto-added to your blacklist while in this mode.
Filtering is fully disabled. Every visitor goes straight to the destination page — no risk evaluation runs at all, and nothing is written to Reports for these clicks.
Masks the stream for the window while an ad platform is reviewing a campaign. Every visitor — including your own whitelisted IPs — is sent to the fallback page instead of the destination page, with no exceptions, for as long as the mode stays set. Scoring and logging still run normally, so Reports keeps showing who arrived. There's no auto-expiry — switch the stream back to filter yourself once the campaign is approved. See Mode for full detail.
Setting up your first stream
- From your dashboard, go to Streams and create a new stream — give it a name and a traffic source (Google, Facebook, TikTok, Bing, or Other).
- Add one or more destination page URLs. If you have more than one, choose a rotation mode (random, sequential, or timer-based).
- Optionally set a fallback page for blocked traffic — recommended for any campaign under active ad-platform review.
- Pick a mode (
filterto enforce immediately, ormoderationto observe first) and a threshold. - Go to Integration, select your new stream, and follow the guide for your platform — see Integration Guides.
- Send a few test clicks and confirm they appear in Reports with the decision and block reason you expect.