When (not if) you get banned: the recovery playbook
Almost every paid-traffic affiliate gets their ad account disabled at some point. Health niches especially. It's the cost of doing business in this category. The difference between "small setback" and "I'm done" is whether you prepared.
The three things that get disabled
| Disabled object | What you lose | Recovery path |
|---|---|---|
| An ad / adset / campaign | That specific ad. Account still works. | Edit and resubmit, or request review. Often a creative/copy fix. |
| An ad account | All ads in that account. Other ad accounts under the same BM still work. | Request review (1× per account, usually). If denied, spin up new ad account in same BM or move to agency account. |
| A personal profile / BM | Everything. Profile login locked, BM frozen, all ad accounts inaccessible. | This is why you set up a backup admin in Module 02. Backup admin keeps the BM alive. |
Prepare before you launch (do this now)
- Backup admin profile on the Business Manager with full control (Module 02).
- Second personal Facebook profile (yours, real identity, separate email, used normally for a few months) ready to be added as a backup-backup if profile #1 falls.
- 2–3 Pages tied to the BM, not just one. If a Page gets restricted, you can switch ad attribution to another.
- Pixel and audiences live in BM, not in a single ad account. They survive when the ad account doesn't.
- Campaign assets backed up off-platform (creative files, ad copy, audience IDs in a spreadsheet). When an account dies, you don't want to be rebuilding from memory.
"Farming" backup profiles (the legitimate version)
"Farmed profile" in this space just means: a Facebook profile that has been used like a normal person uses Facebook for an extended period, so it has trust signals when you eventually attach it to a Business Manager.
To prepare a profile (over weeks, not days):
- Real identity, real phone number, ideally a real selfie verification done early.
- Log in from the same device + Wi-Fi for the first 30+ days. Don't VPN-shop.
- Add real friends (10+ minimum). Post 1–2 times a month. Like, comment, react.
- Join a few Groups. Don't post in them — just join.
- After 60+ days of normal activity, the profile can be added as a BM admin without immediate flag.
Agency ad accounts
When your personal ad accounts get fragile, the next level is renting an agency ad account. Facebook has a partner program where established marketing agencies can request ad accounts on behalf of clients. Those accounts have a much higher trust score because the agency is on the hook for compliance.
How it works in practice:
- You sign up with an agency (search "Facebook agency account affiliate" — there are dozens; reputable ones include established media-buying agencies, not anonymous Telegram sellers).
- They onboard you (KYC, your offer, your landing page reviewed once).
- They share an ad account with your BM as the advertiser. You run ads from your BM, billing goes through them.
- You pay a setup fee ($50–$300) and either a flat monthly or a small % of spend.
- If FB disables an agency-supplied account, the agency replaces it. That's the value.
Use agency accounts once you're spending $100+/day reliably. Below that, the fees aren't justified.
Virtual cards
When a card gets associated with a banned account, FB sometimes flags future accounts that use the same card. Virtual cards (single-use or unique-number-per-account) solve this.
Three legitimate sources:
- Privacy.com (US) — free, generates a unique 16-digit number per merchant, backed by your real bank account.
- Revolut, Wise, N26 — multi-card virtual issuance from standard fintech accounts.
- Your own credit card's "virtual card number" feature — Capital One, Citi, and others offer this natively. Free.
Rotate one virtual card per ad account. When an ad account dies, the card is "burned" — don't reuse it on the next account.
What to actually do the day you get banned
- Don't panic-click "Request Review" five times. One request per banned object. Multiple submissions get auto-rejected.
- Read the disable email. It usually says "violation of Advertising Policies" generically but sometimes specifies which policy.
- Fix the obvious cause if there is one. If your ad clearly violated personal attributes, edit and resubmit when you get account access back.
- Request review via Business Support → Help → Account quality. Be polite and brief: "I believe this disable was in error. My ads promote a digital wellness product and follow the personal attributes guidance. Please re-review."
- If the personal profile is locked, use the backup admin profile to access BM → spin up campaigns from a sibling ad account, keep revenue flowing during the review wait (usually 24–72 hours).
- If permanently disabled, move active campaigns to agency account; spin up fresh BM on backup profile; carry your pixel + audiences over (they live at BM level, you can reassociate them).
Reducing ban frequency
You can't eliminate bans in this category, but you can reduce them:
- Warmup (Module 02) — by far the biggest single factor for new accounts.
- Clean landers — no shock claims, no before/after, accurate to the offer.
- Niches with lower policy heat — non-health niches have fewer bans. Health/finance/weight-loss are highest-risk.
- Don't scale a borderline ad — if an ad is barely passing review, scaling it 10× draws scrutiny. Replace marginal creatives early.
- Don't run identical campaigns across multiple ad accounts — FB detects duplicates and rolls bans across them.
- Pace creative refresh — completely new creative every 2–3 weeks signals "active legitimate business," not "evergreen scam."
How the operator helps
runners/ban_recovery.py orchestrates the unattended path:
- Detects an ad account disable via API.
- Pauses active campaigns gracefully.
- Switches the BM to the backup admin profile.
- Spins up a sibling ad account if quota allows; otherwise pings you to onboard the agency account.
- Rotates the payment card to a fresh virtual.
- Re-launches the previously-running campaigns on the new account, with new ad IDs (no duplicate detection).
This is the only runner that the operator will page you for (Slack webhook if configured) — you want to know the second this happens.