Home › Cloaking
A cloaker is a traffic-filtering layer in your funnel. From one campaign link, reviewers, crawlers and competitor spy tools are served a compliant safe page, while real buyers reach the real landing page. It decides who is who from request signals, then routes each side accordingly.
That is the textbook definition. What actually determines your results are three questions that rarely get answered honestly: how to choose one, what it should cost, and what it will not fix.
How does a cloaker work?
When a visitor hits the campaign link, the system reads public signals from that request — IP ownership and type, User-Agent, GEO, device and browser fingerprint, referrer — and judges whether this is a real user or a reviewer, crawler or automation tool. It then routes the two groups to the safe page and the real page respectively.
Everything hinges on accuracy, and accuracy comes from two things: how fresh the intelligence is (datacenter ranges, proxies, VPNs and bot fingerprints change daily) and how disciplined the decision logic is (better to let a suspicious visitor through than to block a real buyer).
For security reasons we do not publish our own detection signals or the composition of our intelligence sources — publishing them would be writing a bypass guide for the other side. This is standard practice across the industry.
Which five criteria actually matter?
In order of importance: false-positive rate (does it block real buyers), intelligence refresh rate, funnel structure (does it require a redirect), billing model (flat monthly vs per-visit), and whether landing is integrated (do you have to wire two vendors together).
1. False positives
The most underrated metric. Blocking reviewers is easy; not blocking real buyers along with them is hard. False positives quietly delete conversions and are very hard to notice.
2. Intelligence refresh
Datacenter ranges, proxy pools and bot fingerprints shift daily. A cloaker on a static list visibly degrades within a couple of months.
3. Funnel structure
Whether a redirect is required decides whether you get flagged as a misleading link. Most commonly overlooked criterion.
4. Billing model
Flat monthly vs per-visit. At scale the latter gets expensive fast, especially when bot traffic is heavy.
5. Landing integration
Are cloaker and PWA on one platform and one domain? When you wire two vendors, the redirect is usually born at the joint.
What does a cloaker cost?
The mainstream band is $100–$200 per month. The full spread runs from $25/month at entry level to €1,199/month at the high end, with at least one vendor offering a ~$330 lifetime licence. Price differences come mostly from intelligence quality, supported traffic sources and concurrency — not from feature count.
| Tier | Price range | Typical positioning |
|---|---|---|
| Entry | $25 – $50 / mo | Limited campaigns and domains; fine for testing |
| Mainstream | $100 – $200 / mo | Market median; where most teams land |
| High end | $250 – €1,199 / mo | Many traffic sources, high concurrency, deeper checks |
| Lifetime | ~$330 one-off | Rare; includes ongoing updates |
Figures from a public 2026 third-party review of 12 vendors, collected September 2026; pricing changes often. Worth noting: none of the 12 vendors in that review offered a PWA — landing has to be sourced separately.
What a cloaker cannot fix (the part nobody covers)
A cloaker only governs who sees which page. It cannot compensate for a weak account, a low-trust Page, creative that violates policy on its own, a domain with history, or landing content that crosses a hard line. The widely held view in this industry is that account stability weighs at least as heavily on approval as the cloaker does.
Saying this plainly serves both sides. We see the same pattern constantly: someone upgrades to a more expensive cloaker and nothing changes — because the disease was in the account and the creative, not in the filtering layer.
A cloaker solves
What reviewers and crawlers see, whether competitors can scrape your real landing page, and filtering out bots and junk traffic.
A cloaker does not solve
Account and Page history, policy-violating creative, domain reputation, or operational issues like payments and support.
So treat any “100% approval” claim as a red flag — including from us; we will not make it. What we do commit to is doing the filtering and the funnel-structure layers properly, and not creating new problems in either.
What is different about the HZWADS cloaker?
Three things: flat monthly billing (not per visit — bot traffic costs you nothing extra), swap campaign links without touching live ads (one click, no relearning), and same platform and same domain as the PWA (nothing to wire together, so no redirect appears).
Flat monthly billing
Not charged per visit. Bots and junk traffic are supposed to be filtered out — you should not be paying by the head for them.
Swap links, keep ads
Rotate the campaign link without editing live ad sets, so you avoid resetting the learning phase.
Same-domain mode
PWA landing and cloaked site share one domain. No cross-domain hop to detect, and nothing broken in the payment stack.
PWA included free
No monthly fee, no per-install billing, no revenue share, no offer lock-in, no cap.
FAQ
Will using a cloaker hurt my Google organic rankings?
It depends who you are filtering. Google defines cloaking as “presenting different content to users and search engines with the intent to manipulate search rankings” — aimed at sites that fool Googlebot to rank. Filtering for ad review is a separate track from Google organic. That said, if your own corporate site serves Googlebot something different, that is textbook cloaking and the site can vanish from the index.
What do false positives cost me, and how do I detect them?
They quietly reduce conversions and are nearly impossible to attribute — you will blame the creative or the audience. Detect them with a controlled comparison: same traffic, measure arrival and conversion rates with the cloaker in the path versus without. The unexplained gap is your false-positive rate. This is why it belongs at the top of the criteria list.
My ad was rejected mid-flight — did the cloaker fail?
Not necessarily. The more common cause is a redirect in the funnel being detected. Meta re-reviews landing pages during delivery, and redirects are the behaviour it names in policy. Upgrading to a pricier cloaker usually will not help — the funnel structure is what has to change.
Can I buy just the cloaker and build my own landing page?
Yes. But if your landing page is on a different domain from the cloaker, you will most likely need a redirect between them — which brings you back to the previous question. At minimum, check whether a cross-domain hop exists in your path.
Is a cloaker the same as an anti-detect browser?
No. An anti-detect browser handles your side — isolating environments and fingerprints across many accounts so they do not link to each other. A cloaker handles the visitor side — who arrived and which page they get. Different problems; most operations run both.
Get the filtering and the funnel right together
Flat monthly cloaking, free PWA, one platform.
Talk to us on Telegram