Spare fan pages keep your ads running when the page they run from gets restricted or disabled: you connect a ready backup and relaunch instead of stopping campaigns. Without spares, you're stuck waiting for recovery or buying new pages mid-campaign.
Facebook ads are published on behalf of a page, so when your primary fan pages get restricted, disabled, or hit limits, every ad running from them stops. A ready spare is the difference between staying live and sitting idle.
Why Fan Pages Go Down
Fan pages get restricted for policy violations in creatives, sudden traffic spikes, or platform algorithm changes. Sometimes it's your fault, sometimes it's the algorithm — either way, you need to keep running.
Young pages and pages running aggressive offers (finance, crypto, nutra) draw more checks. You can't fully control this, so a reserve is prepared in advance, not on the day a page goes down.
How Many Spares to Keep
Keep at least one ready spare for every working page, and grow the reserve as your campaign volume and risk grow. There is no universal number: it depends on your scale and risk tolerance.
Starting out
One working page plus a ready spare is the minimum. If the working page gets flagged, you switch and troubleshoot without pausing ads. For calm offers and a small number of campaigns, this is enough.
Running several campaigns at once
At this stage a single restricted page can take down a big part of your daily results, so keep more spares. They let you pivot without pausing everything. Rotate them regularly so they don't look abandoned when you need them.
Large operations
Instead of a fixed number per account, maintain a shared pool and distribute pages as needed. Bigger operations absorb restrictions better because they're spread across accounts and geos, but they also spend more, so downtime costs more. Don't stock more than you can actually check: a dead spare is not a spare.
What Makes a Good Spare
A good spare is an aged page with a clean record that isn't connected to live campaigns. Not every fan page works as a backup. Look for:
- Age. A freshly created page is more likely to get checked at your first launch, which is why aging matters. Aim for pages aged 90+ days, ideally a year or older, and check a page's age before buying.
- Clean history. No active policy strikes and no abandoned ad accounts attached. A page flagged once is more likely to be flagged again.
- A finished look. A description, a logo and a few posts. An empty page looks suspicious.
- 2FA. Preferably included; it makes the page safer to hold.
- No active campaigns. Keep spares dormant until you need them, so they don't inherit restrictions from other pages' problems.
For maximum cover, consider a reinstated page (PZRD FP): a page whose ad restriction was lifted after review. That doesn't contradict the clean-history rule, since the restriction is already gone. Such pages are considered more resilient, though nothing guarantees they won't be restricted again.
How to Store and Rotate Spares
Label every spare, keep it away from live campaigns, spread spares across ad accounts, and check them regularly.
Label them clearly. Note each spare's creation date, the account it's attached to, and its status (active, backup, cooling down). A simple spreadsheet saves a lot of confusion when you need a replacement fast.
Keep them lightly active. Don't let a spare sit untouched for long stretches. Log in from time to time, add a post, interact with your own content. A page that looks abandoned is more suspicious to the algorithm.
Don't attach multiple spares to one ad account. If that account gets flagged, all connected pages can go down together. Spread spares across different ad accounts so a single restriction doesn't wipe out your reserve.
Keep spares separate from your main campaigns. Don't run hot campaigns through an account that holds a spare. Once you activate a spare for a campaign, it's no longer a spare — it's a working page, and the reserve needs topping up.
When to Buy More Spares
Restock when your reserve is being used faster than you replace it — before it runs out, not after. Typical signals:
- You're switching to spares more often than before, and the reserve keeps shrinking.
- Your primary pages show early warning signs: policy warnings, account reviews, slower ad approvals.
- You're scaling to new geos or verticals where restrictions are more common.
- You're testing aggressive creatives or untested audiences.
Waiting until you're completely out is how campaigns stall.
Pairing Spares With the Right Ad Accounts
Pair spare pages with accounts that already have history — PZRD, farm or aged accounts — rather than brand-new autoregs. A spare page is only as useful as the account it ends up running on:
- PZRD accounts have already had an ad restriction lifted and come back. They're considered more resilient.
- Farm accounts with 14+ days of activity are solid: they have history and implicit trust.
- Aged accounts (2022 and older) are better than fresh autoregs. The older the account, the more buffer you have.
Avoid pairing spares with brand-new autoreg accounts unless you have no choice. A new account plus a new page means double risk.
What Running Out Costs
Without a spare, ads from a restricted page stay off until you find and prepare a replacement: no ads, no creative tests, no scaling, and the budget sits idle.
A spare page costs money upfront, but it's cheaper than stopped campaigns. Stock up on aged spares in the fan page catalog or bundled with farm accounts, keep them labeled and lightly active, and when a restriction hits, switch and keep running.
FAQ
How many spare fan pages do I need per ad account?
At least one ready spare for every working page. If you run many campaigns at once, work with aggressive offers or scale into new geos, keep more — but only as many as you can check regularly.
Should spare fan pages be connected to live campaigns?
No. Keep spares dormant and spread across different ad accounts. If a campaign or an account gets flagged, the pages connected to it can go down together.
How old should a spare fan page be?
Aim for 90+ days, ideally a year or older. Fresh pages are more likely to get checked at the first launch.