What is a cloaking service?

A cloaking service decides, for each visit, which version of your landing page to serve. Ad platform review systems and scrapers get a page that stands on its own; people who arrived through your ad get the offer page. CloakerHQ makes that decision in two layers: network attribution before anything renders, then browser evidence once the page has loaded.

Do I have to redirect visitors?

No. CloakerHQ keeps one URL. The offer is swapped in on the page itself, so the address bar never changes and there is no redirect chain to inspect.

What does ad review actually see?

The compliant page, and only that, unless it executes JavaScript and stays long enough for the second layer to run. On live campaigns almost none of it does: TikTok's scanner rarely runs page scripts at all, and Meta's automated crawler is gone in a fraction of a second.

How much does it cost?

$49, $99 or $199 a month depending on how many sites you run and how much traffic passes through the filter. Campaigns are unlimited at every tier. Waitlist signups keep their price for the first year.

Is this against ad platform policy?

Yes. Google and Meta both prohibit showing their review systems different content from what users see, and Meta has sued cloaking software vendors directly rather than only the advertisers using them. Nobody can promise your account survives, and any vendor who does is selling a decision that is not theirs to make.

One URL, two audiences

CloakerHQ is one script on your landing page. Ad review and scrapers get a page that stands on its own; the people who clicked your ad get the offer. No redirect, no second domain, $49 a month.

Two browser windows showing the same URL: one serving a plain company catalogue page, the other serving a discounted product offer — The same URL in both windows. Nothing redirects, and nothing about the address tells the two apart.

The part of this problem nobody else covers

Every filter in this category decides from the request: the address, the network it belongs to, the headers it carried. That works for review traffic which announces itself, and it is blind to the case that actually costs accounts.

We see review sessions arrive from ordinary cloud providers with complete headers, ordinary Android and Windows user agents, and nothing irregular anywhere in the request. Server-side there is nothing to see, which means every filter deciding before the page renders serves those sessions the offer.

The only thing that separates that visitor from a buyer is the environment their browser is running in. And environment evidence does not exist until the page is running, which is why we decide on the page rather than before it.

What we bring to that layer

A browser-environment engine built for the opposite problem: working out when a browser is lying about what it is. A review environment is a machine presenting itself as somebody's phone, and that is the same question asked from the other side.

What we will not do is print the signals and their hit rates on a public page. The one thing every rule in this layer has in common is that it stops working the moment the platform reconfigures around it, and it stops working silently. Publishing the recipe is writing the other side's fix list.

One thing worth saying anyway, because it is about the category rather than about us: the automation flag most of these tools treat as their bot signal does not fire on ad review at all. It fires on unrelated automation farms. More checks is not the same as the right ones.

One verdict, spent properly

A browser verdict is expensive: the visitor has to stay several seconds for the probes to finish, so it is precise and rare at the same time. Treating it as a verdict about one visit wastes almost all of its value.

A browser verdict is expensive to obtain and therefore rare. It does not stop at the visit that produced it: it becomes an address-level label applied backwards and forwards, which is the only path from a precise but rare signal to coverage of your whole traffic.

So a confirmed review environment becomes a label on the address, and the address covers every request from it afterwards, including the ones that arrive in a tenth of a second and never run a script at all. This is the only route from a rare high-precision signal to coverage of your whole traffic, and it is the piece we think is genuinely ours.

A filter log listing visits with their origin, the reason each was filtered, which layer decided, and which page was served — Every filtered visit, with the reason and the layer that decided it. The banner at the top is the alarm that fires when a rule stops matching anything, because a rule that quietly stopped working looks exactly like a quiet week.

What we will not claim

A human reviewer we cannot place

Real browser, real machine, an address we cannot attribute, behaving normally. Nothing in this category catches that, ours included, and the honest version of this page says so rather than quoting you a number.

That the rules last forever

Every rule in the browser layer stops working the moment the platform reconfigures around it, and it stops working silently: zero matches looks exactly like a quiet week. So every account gets an alarm on hit counts rather than a dashboard nobody reads.

That your account is safe

That decision belongs to the platform. Anyone selling you a survival rate is selling something they do not control.

That the filter is the hard part

Your compliant page is. We have watched a human reviewer go through an entire checkout on one, filling the forms and submitting payment. No filter rescues a page that cannot survive that.

Pricing

Priced on sites and traffic, not on campaigns. Join the waitlist and your tier stays at this price for the first year.

Starter

$49 / mo

1 site
50,000 filtered visits a month

One offer, one landing page, one traffic source.

Growth

$99 / mo

5 sites
250,000 filtered visits a month

Several offers running at once, across more than one platform.

Scale

$199 / mo

Unlimited sites
1,000,000 filtered visits a month

Agencies and media buyers running for more than one advertiser.

In every tier

Both filtering layers, network and browser
Unlimited campaigns, no per-campaign charge
Google, Meta, TikTok, Bing and X, all included
One URL, no redirect
A log of every filtered visit and why it was filtered
An alarm when a rule stops matching anything

What each tier includes.

Questions people ask first

What is a cloaking service?: A cloaking service decides, for each visit, which version of your landing page to serve. Ad platform review systems and scrapers get a page that stands on its own; people who arrived through your ad get the offer page. CloakerHQ makes that decision in two layers: network attribution before anything renders, then browser evidence once the page has loaded.
Do I have to redirect visitors?: No. CloakerHQ keeps one URL. The offer is swapped in on the page itself, so the address bar never changes and there is no redirect chain to inspect.
What does ad review actually see?: The compliant page, and only that, unless it executes JavaScript and stays long enough for the second layer to run. On live campaigns almost none of it does: TikTok's scanner rarely runs page scripts at all, and Meta's automated crawler is gone in a fraction of a second.
How much does it cost?: $49, $99 or $199 a month depending on how many sites you run and how much traffic passes through the filter. Campaigns are unlimited at every tier. Waitlist signups keep their price for the first year.
Is this against ad platform policy?: Yes. Google and Meta both prohibit showing their review systems different content from what users see, and Meta has sued cloaking software vendors directly rather than only the advertisers using them. Nobody can promise your account survives, and any vendor who does is selling a decision that is not theirs to make.

Join the waitlist

There is nothing to sign into yet. Leave an email and we will write once the private beta opens, with setup notes for the traffic source you run.