Why do PWA campaigns get banned?

Most often because of burned domains, weak cloaking, inconsistent creatives and dirty tracking. Less often account behavior. There is no magic: a ban is almost always explainable.

What to do right after a domain ban?

Switch the app to a spare domain in one click. Users with the installed PWA keep using it, and new traffic goes to the fresh domain.

Is cloaking alone enough to avoid bans?

No. Cloaking is part of a system. Without fresh domains, clean tracking and sane account behavior, even good cloaking will not last long.

How many spare domains should I keep?

Enough that rotation never stops the flow. A pool of fresh auto-HTTPS domains and one-domain-one-app reduce the risk of a cascading ban.

Can I run PWA with zero bans?

You cannot fully rule out a ban, but the right funnel multiplies a campaign's life and makes a ban a manageable routine rather than a total loss.

How to Run PWA Without Bans

A ban is almost always about domains, cloaking and behavior, not magic. Fresh domains with HTTPS, honest cloaking, clean tracking and ready rotation let a campaign live far longer. Below is a practical checklist of what to set up before you run and how to react when a domain does get banned.

Domains: fresh and on HTTPS

An old or burned domain exposes the funnel before the cloak even runs. You need fresh domains with automatic HTTPS and no history. Keep a spare pool so a ban means switching, not scrambling for a domain. One domain, one app — so a ban does not drag down the whole network.

Cloaking and anti-bot

Cloaking shows a clean white page to moderators and bots and the offer to real targeted traffic. Filter crawlers by user-agent, datacenters and VPNs by IP intelligence, and drop the wrong geo. The main rule is not to cut real users on mobile and Wi-Fi, or you lose conversions along with the bots.

Warm-up and account behavior

A sharp start with big budgets on a fresh account is a red flag. Warm-up, careful budget ramp and stable behavior lower ban risk at the account level. Domains and creatives must look consistent: mismatches between the ad, white and offer speed up moderation.

Clean tracking

A messy redirect, revealing URL parameters and offer leaking into the source help a moderator ban you. Keep the chain clean: click id in parameters, not the offer; server-side postbacks; no extra traces on white. Clean tracking also means correct attribution, not just survival.

Rotation: a plan for the ban

A ban is a matter of when, not if. Keep spare domains ready and switch the app to a new one in one click: users who already installed the PWA keep opening it with no loss. Ready rotation turns a ban from a disaster into a routine consumable swap.

FAQ

Why do PWA campaigns get banned?: Most often because of burned domains, weak cloaking, inconsistent creatives and dirty tracking. Less often account behavior. There is no magic: a ban is almost always explainable.
What to do right after a domain ban?: Switch the app to a spare domain in one click. Users with the installed PWA keep using it, and new traffic goes to the fresh domain.
Is cloaking alone enough to avoid bans?: No. Cloaking is part of a system. Without fresh domains, clean tracking and sane account behavior, even good cloaking will not last long.
How many spare domains should I keep?: Enough that rotation never stops the flow. A pool of fresh auto-HTTPS domains and one-domain-one-app reduce the risk of a cascading ban.
Can I run PWA with zero bans?: You cannot fully rule out a ban, but the right funnel multiplies a campaign's life and makes a ban a manageable routine rather than a total loss.

Build your PWA in APEX in minutes

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

Get started free