Why is cloaking needed for Facebook?

To pass moderation: moderators and bots see legal white, while the offer shows only to live targeted traffic. Without cloaking a gambling campaign is short-lived.

What does a Facebook moderator see?

The white page — neutral safe content consistent with the creative. The offer (black) is not shown to them.

How do I avoid cutting real users?

Tune filters carefully: cut bots, datacenters and the wrong geo, but let live users on mobile and Wi-Fi through. Too-crude filters lose conversions.

Does cloaking guarantee no ban?

No. Cloaking is part of a system; you also need fresh domains, clean tracking and sane account behavior.

Where should cloaking run?

Ideally at the edge, before the page loads, so the white/black decision is instant and never exposes the offer.

Cloaking for Facebook in PWA

Cloaking shows moderators and bots a safe white page and the offer to live targeted traffic. For gambling and betting on FB it is a survival condition. Here is what and how to filter to pass moderation without cutting real users.

How cloaking works

The cloak analyzes each request — user-agent, IP, geo, device, fingerprint — and decides what to show. A bot or moderator gets neutral white; a live targeted user gets the showcase or offer (black). The best cloaking runs at the edge, before the page loads.

White and black pages

White is legal neutral content (blog, review, news) that moderation sees. Black is the real offer for targeted traffic. A mismatch between the ad and white speeds up a ban, so they must look consistent.

What to filter

Bots and crawlers by user-agent, datacenters and proxies/VPNs by IP intelligence, the wrong geo and suspicious devices by fingerprint. The main rule is not to cut real users on mobile and Wi-Fi, or you lose conversions with the bots.

Geo and datacenter filters

FB moderation often comes from datacenters and outside the target geo — those go to white. Precise geo and datacenter filters let live targeted traffic through and cut checks. Too-crude filters cut real users, too-soft ones expose the offer.

Cloaking is part of a system

Cloaking alone will not save you: you need fresh HTTPS domains, clean tracking and sane account behavior. Cloaking handles passing moderation, but campaign survival is the sum of all factors. See the guide on running PWA without bans.

FAQ

Why is cloaking needed for Facebook?: To pass moderation: moderators and bots see legal white, while the offer shows only to live targeted traffic. Without cloaking a gambling campaign is short-lived.
What does a Facebook moderator see?: The white page — neutral safe content consistent with the creative. The offer (black) is not shown to them.
How do I avoid cutting real users?: Tune filters carefully: cut bots, datacenters and the wrong geo, but let live users on mobile and Wi-Fi through. Too-crude filters lose conversions.
Does cloaking guarantee no ban?: No. Cloaking is part of a system; you also need fresh domains, clean tracking and sane account behavior.
Where should cloaking run?: Ideally at the edge, before the page loads, so the white/black decision is instant and never exposes the offer.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free