cloakingx@guard:~

Cloaking for X Ads

X (formerly Twitter) doesn't publish a documented user-agent or IP range for a dedicated ad-review crawler the way Google or Meta do — so there's no single named signature to attribute review traffic to. What X Ads streams need instead is the general layer: bot, datacenter, and VPN filtering; spy-tool blocking; and correctly recognizing X's own in-app browser as a real visitor rather than a bot.

Why X Ads Review Detection Is Different From Google or Meta

Google (AdsBot-Google), Meta (facebookexternalhit / AS32934), TikTok (Bytespider / ByteDance's own ASNs), Microsoft (AdIdxBot), and Yandex (YaDirectFetcher) all self-document a crawler identity — a user-agent token, an IP range, or both — that Cloaking X can match against directly. X has not published an equivalent for its own ad review process, so no platform-specific crawler signature exists to attribute here.

That doesn't mean X Ads traffic goes unfiltered. Whatever automated review or scraping activity does hit your landing page still has to originate from somewhere — a datacenter, a VPN exit node, a bot-hosting network, or a scripted HTTP client — and that's exactly the general layer described below, running on every stream regardless of which platform sent the click.

How Cloaking X Filters X Ads Traffic

Every X Ads stream runs full IP intelligence (datacenter/VPN/Tor/proxy detection), browser and JS-fingerprint integrity checks, and spy-tool/scraper blocking — the same general-purpose layer every stream on this product uses, independent of any single named crawler.

X's own iOS in-app browser (the WKWebView opened when a real user taps an ad from inside the X app) is recognized as a genuine consumer browser, not flagged as automated — so a real viewer browsing from inside the X app isn't misjudged for carrying a stripped, non-standard user-agent string. The same stream captures twclid (X's click identifier) automatically.

SIG.01

Bot, VPN & Datacenter Filtering

IP intelligence flags datacenter, VPN, Tor, and proxy traffic in real time — the primary defense for a platform with no self-published crawler signature to match against.

SIG.02

In-App Browser Recognition

Recognizes X's own iOS in-app browser as a real visitor, not a bot — it strips the standard Version/Safari tokens a normal fingerprint check would expect, and is allowlisted specifically so it isn't misjudged.

SIG.03

8 Delivery Modes

Proxy, 302 redirect, meta refresh, iframe, cross-origin iframe, JS redirect, click-reveal, or mirror — pick whichever fits your X Ads tracking setup.

SIG.04

twclid Capture

Automatic click-ID capture for X's twclid, alongside RedTrack/Voluum/Keitaro/Binom/Utmify if you're running a tracker in front of the stream.

Setting Up X Ads in 3 Steps

  1. 1

    Create a stream

    Set your fallback page (or use the built-in generator) and your money page(s) for this campaign.

  2. 2

    Choose a delivery mode

    Pick the mode that matches your setup — most X Ads streams run proxy or 302 redirect delivery.

  3. 3

    Point your X Ads website URL at the stream

    Use the stream link (or your own domain, if you're on a plan with custom domains) as the ad's website URL.

Related Documentation

Filter X's Reviewers, Not Your Real Traffic

Start on the Free plan — one stream, 300 clicks/day, no time limit — and see how X review traffic gets routed differently from real visitors.

Start Free View All Plans

See Also