Cloaking for Native Ads (Taboola & Outbrain)
Native ad networks like Taboola and Outbrain review the destination behind a widget click before approving a campaign, and third-party ad-intelligence scrapers separately crawl live native placements to reverse-engineer whichever creative and funnel is running. Cloaking X's job on a native stream is to tell those apart from a real reader and route each one to the right page.
How Native Ad Networks Review a Landing Page
Taboola self-documents its own review crawler — Taboolabot — in its Realize help center, giving both a fixed user-agent token and its own dedicated network (Taboola operates its crawling infrastructure on two registered autonomous systems). That's two independent, verifiable signals for the same crawler, which is unusually strong for an ad-review bot — most platforms publish only one or the other, if either.
Outbrain does not currently publish an equivalent documented user-agent or IP range for its own review crawler, so Cloaking X has no verified platform-specific signature to match against for Outbrain review traffic specifically. Outbrain (and any other native network) traffic still runs through this product's general bot, datacenter, VPN, and spy-tool defenses below — it just isn't attributed to "Outbrain's reviewer" by name the way Taboola's is.
How Cloaking X Filters Native Ad Review Traffic
Cloaking X attributes Taboolabot by both its user-agent and its two registered network ranges (AS200478 / AS206614) in real time, at the edge, before the request reaches your money page — either signal alone is enough to route it to your fallback page.
Every native stream also runs full IP intelligence (datacenter/VPN/Tor/proxy detection), spy-tool and scraper blocking, and browser/fingerprint integrity checks — the same layer that covers platforms with no published crawler signature of their own, so a network like Outbrain is still filtered on general signal even without a named-crawler match. The same stream captures tblci (Taboola's click identifier) automatically.
Taboolabot UA & Network Attribution
Recognizes Taboola's own review crawler by both its documented user-agent and its two registered autonomous systems — two independent signals for one crawler.
Spy Tool & Scraper Blocking
Blocks the ad-intelligence scrapers competitors use to pull your creative and funnel off a live native placement.
8 Delivery Modes
Proxy, 302 redirect, meta refresh, iframe, cross-origin iframe, JS redirect, click-reveal, or mirror — pick whichever fits how your native tracking URL is set up.
tblci Capture
Automatic click-ID capture for Taboola's tblci, alongside RedTrack/Voluum/Keitaro/Binom/Utmify if you're running a tracker in front of the stream.
Setting Up Native Ads in 3 Steps
- 1
Create a stream
Set your fallback page (or use the built-in generator) and your money page(s) for this campaign.
- 2
Choose a delivery mode
Pick the mode that matches your setup — most native streams run proxy or 302 redirect delivery.
- 3
Point your native widget's destination URL at the stream
Use the stream link (or your own domain, if you're on a plan with custom domains) as the destination URL on your Taboola or Outbrain campaign.
Filter Native's Reviewers, Not Your Real Traffic
Start on the Free plan — one stream, 300 clicks/day, no time limit — and see how Native review traffic gets routed differently from real visitors.