Domain Rotation After a Ban
A domain gets burned far more often than a whole ad account, and without a warmed backup ready, your campaign just sits idle while you scramble to buy and configure a new one. In APEX, rotation means pointing the same PWA at a domain from a ready pool in one click — no rebuild, no editing every ad link.
Why the domain gets banned, not the account
Ad platforms and anti-fraud systems usually blocklist the specific link or domain first, before touching the whole ad account: the domain lands on a blocklist, browsers show an unsafe-site warning, or part of your audience just sees a white page or a load error. From the outside it looks like a sudden drop in impressions or clicks on a campaign that was live a moment ago. The upside is that a domain ban is usually cheaper to fix than an account ban — you don't need a new ad account, just a new entry point.
Treat domains as a running cost, not a one-time purchase
Budget for domains the way you budget for ad spend — as a recurring cost of the campaign, not a single purchase meant to last forever. Keep a pool of several warmed backup domains ready per active campaign so a ban doesn't catch you flat-footed. Buying a replacement only after the old one is already dead means downtime and lost momentum, not savings.
How rotation actually works under the hood
In APEX, the same PWA project can be attached to several of your own domains with automatic free HTTPS — the witrina content, cloaking rules and settings stay exactly as configured, only the entry point changes. If your ads point through a tracking or redirect link (a Keitaro domain, for example) instead of straight at the witrina, the ad link itself never has to change — only its destination does.
Step-by-step rotation when a ban hits
Confirm the ban first: open the link in incognito mode, from an IP in the target geo, on a clean device — if the white page or a load error shows up consistently, it's a real ban, not a fluke. In APEX, attach the next domain from your backup pool to the same PWA, and check that HTTPS issued cleanly and the witrina loads correctly. Update the destination in your tracker once (not every single ad, if you're routing through a redirect link), then resume spend while watching the first clicks closely.
What survives the switch, and what needs care
Stats and postbacks don't disappear — click IDs and conversion data live in the tracker, not on the witrina's domain. The one thing worth planning around is push subscribers: a push subscription is tied to the origin where it was created, so your existing base is still reachable only through the old domain. Common practice is to keep the old domain alive a little longer just to finish sending to existing subscribers, while the new domain builds its own base.
Cutting down how often you need to rotate at all
Rotation is a backup plan, not a default strategy — solid cloaking and antibot filtering (bots, datacenters, wrong geo) lower the odds of getting flagged in the first place. Keep unrelated offers and verticals on separate domains, don't reuse a domain that was just banned for a new attempt right away, and watch for early warning signs like a sudden CPM spike or CTR collapse — that's often visible before the hard ban lands.
FAQ
- How many backup domains should I keep per campaign?
- Three or more is a reasonable baseline — the higher the daily budget and the riskier the vertical, the more you want in reserve so you're never rotating mid-shift under pressure.
- Does traffic stop while you rotate domains?
- If ads point through a tracking or redirect link rather than straight at the witrina domain, switching takes minutes and doesn't require touching the ads themselves.
- What happens to push subscribers when the domain changes?
- A subscription stays tied to the domain it was created on, so your existing base is only reachable while that old domain stays alive — worth keeping it running a bit longer instead of killing it immediately.
- Do I need to change the creative along with the domain?
- Not necessarily if only the link or domain was flagged — but if the ad itself showed ban signals too, refresh it as well, or you'll likely hit the same wall on the new domain.
- How do I tell a real ban apart from a temporary stats dip?
- Test the link in incognito from an IP in the target geo on a clean device — a white page, browser warning or load error that reproduces consistently means a ban, not normal fluctuation.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free