Text version of this lessonExpand
When a Meta account is restricted, speed is not the first goal. The first goal is to find the restricted layer, gather evidence that can be checked, fix the risk source, and restart without creating a second incident.
Lesson output: Meta recovery evidence pack
This lesson produces one operating asset: a Meta recovery evidence pack. It helps the team stop guessing whether the problem is the profile, Business Portfolio, ad account, Page, Catalog, Commerce status, billing, or security access.
The pack must answer seven questions
- Restricted layer: Which layer is affected: profile, Business, ad account, Page / Catalog, billing, or security.
- Asset IDs: Business ID, ad account ID, Page, Catalog, domain, product ID, payment record, or case ID.
- System message: The exact Account Quality, Business Support Home, Ads Manager, Commerce Manager, or billing message.
- Last 14 days changes: Payment, access, login device, creative, landing page, domain, Catalog, Pixel, or CAPI changes.
- Fixed risks: What was removed, corrected, paused, or aligned before review.
- Support path: Account Quality, Business Support Home, Commerce Manager, billing support, or security recovery.
- Week-one restart rule: How the account will restart with low-risk creative, stable payment, limited access, and a review log.
Plain terms before recovery
A restriction is easy to misread because several Meta surfaces are connected. A personal profile may manage a Business Portfolio. The Business may own ad accounts, Pages, domains, Pixels, datasets, and Catalogs. The ad account may be blocked by payment or policy. A Catalog may have product issues that look like ad issues. Write the layer before you write the appeal.
| Term | Plain meaning | What breaks when it is wrong |
|---|---|---|
| Profile | The personal Meta account that logs in and manages assets. | If identity, 2FA, or advertising access is restricted, the person may not be able to request review or manage business assets. |
| Business Portfolio | The business container that holds ad accounts, Pages, Pixels, Catalogs, domains, and people access. | If business records, domains, or admin access are messy, recovery cannot be solved only inside the ad account. |
| Ad account | The account that spends ad budget and holds payment settings. | Failed payments, rejected ads, abnormal spend, or policy issues can stop delivery. |
| Page / Catalog | The public Page and product catalog used by ads and shops. | Page content, product claims, Catalog status, or landing pages can create policy or Commerce issues. |
| Account Quality | One official place to inspect ad and asset restrictions and review options. | If the team relies only on email screenshots, it may miss the actual restricted object and review path. |
Use layer diagnosis before choosing an action
Do not describe the incident as "the account is banned" until you know which layer is actually blocked. Different layers require different evidence and different first actions.
| Layer | Check first | First action | Do not do first |
|---|---|---|---|
| Profile | Identity verification, 2FA, login devices, advertising access. | Secure login and identity before touching managed assets. | Create a new personal profile to bypass review. |
| Business | Business verification, admins, partner access, domains, risky assets. | Align business records and clean access. | Submit conflicting documents repeatedly. |
| Ad account | Payment, rejected ads, abnormal spend, account status. | Save ad account ID, billing records, rejected ads, and case status. | Move the same risky creative into a new ad account. |
| Page / Catalog | Page content, products, landing pages, Commerce status, permissions. | Fix product and page issues before ad recovery. | Inspect Ads Manager only. |
| Billing | Payment method, billing address, failed charges, payer details. | Fix payment stability and record consistency. | Rotate cards and accounts under pressure. |
Restriction scenario router
The same red warning can come from different systems. Use the symptom to pick the first recovery lane, then gather evidence for that lane before opening more actions.
| Scenario | Priority layer | Evidence to gather | Blocked move |
|---|---|---|---|
| Payment failed after budget scaling. | Billing / ad account | Billing screenshot, failure time, payer details, budget-change log, ad account ID. | Do not rotate cards, currencies, or payer identity. |
| Ad account appears restricted but the review button is missing. | Profile / security | Profile status, 2FA, login devices, admin list, Business Support Home message. | Do not borrow another person's profile to create a new Business for the same site. |
| Ad rejection appears with Catalog or Commerce warnings. | Page / Catalog / Commerce | Product ID, Catalog status, landing URL, before/after screenshots, Commerce notice. | Do not move the same product and page into a new ad account. |
| Restriction appears after agency handoff. | Business / access security | People access table, partner list, 2FA status, recent access changes, Business ID. | Do not keep every former operator as admin just in case. |
Replay the last 14 days
Many restrictions feel sudden only because nobody kept a change log. Before submitting review, replay the last 14 days and write the likely trigger next to each change.
| Window | Possible change | Risk hypothesis | Evidence |
|---|---|---|---|
| D-14 to D-10 | Card, billing address, payer, failed charge. | Billing risk or inconsistent records. | Payment record, billing screenshot, failure message. |
| D-9 to D-6 | Admin, partner, access, 2FA, login-device change. | Security or access anomaly. | Access table, device record, 2FA status. |
| D-5 to D-3 | New creative, claim, landing hero, offer, or product promise. | Policy or page-support issue. | Creative screenshot, URL, preflight notes. |
| D-2 to incident day | Domain, Catalog, Pixel, CAPI, checkout, or theme change. | Asset connection, Commerce issue, or signal anomaly. | Change log, event QA, Catalog status. |
Recovery anti-patterns that raise risk
Bad recovery usually looks busy. The team submits appeals, opens assets, changes cards, edits ads, and asks more people to log in. That creates more signals and fewer facts.
Replace these moves
- Repeated vague appeals: replace with one evidence pack that names layer, IDs, system message, fixed risk, and support path.
- New Business or ad account under pressure: replace with root-cause repair before deciding whether a new structure is needed.
- Frequent card or operator switching: replace with stable payer, stable device, 2FA, and narrow admin access.
- Appeal while risky creative or page remains live: replace with removal or correction plus before/after evidence.
Choose the support path by issue type
Not every issue belongs in the same appeal text. Account Quality is useful for ad and asset restrictions. Business Support Home can support Business and ad account cases when available. Commerce Manager belongs to product, Catalog, and shop issues. Billing support belongs to payment failures. Security recovery comes before policy debate when a profile or admin path is compromised.
Support path checklist
- Ad or asset rejection: bring ad ID, system reason, and before/after evidence.
- Business or ad account support: bring Business ID, ad account ID, case ID, and record consistency.
- Product or Catalog issue: bring product ID, Catalog status, page evidence, and fix screenshots.
- Billing issue: bring payment records, failure messages, and payer identity consistency.
- Security issue: bring login records, 2FA state, admin list, and affected assets.
Week-one restart rules
Recovery is not finished when the account is re-enabled. The first week after recovery should prove stability, not chase aggressive growth.
| Rule | Why it matters |
|---|---|
| Run approved creative only. | Do not reintroduce the expression that may have created the incident. |
| Restart budget slowly. | A sudden spend jump can create billing, learning, or review noise. |
| Freeze payment and access changes for seven days. | A stable payer and admin environment makes the next review easier to explain. |
| Keep a recovery log. | If another warning appears, the team can explain what changed and what did not. |
Stop / Go decision
Stop if the restricted layer is still unclear, risky creative or pages are still live, business records and payment identity conflict, or the same risk is being moved into a new asset.
Go when the fault layer is clear, the last 14 days are documented, the risk source is removed or fixed, and the first-week restart rule is written.
Copyable recovery packet
Current scenario: __; symptom: __; priority layer: __; evidence to gather: __; first move: __; blocked move: __; support path: __; week-one restart rule: __.