Account Restrictions

Facebook Ad Account Restricted? What to Do Next

A calm, operational checklist — not a guarantee of restoration.

Common restriction types

Meta may limit advertising ability at several layers: the ad account, Page, Business Manager, user profile with advertising permissions, payment method, or combinations of those. Symptoms often overlap — ads disabled, spend blocked, inability to create campaigns, assets greyed out, or policy flags on creatives and landing pages — so the first job is to identify which layer is actually limited.

An ad-account-level issue may leave your Business Manager and Pages usable while blocking spend on one node. A Page issue can interrupt advertising even when the ad account looks healthy. A Business Manager issue can cascade across multiple accounts and partner relationships. Payment problems can look like policy restrictions until you inspect billing. Treat “restricted” as a category that needs diagnosis, not a single event with one fix.

Notices inside Ads Manager, Business Settings, and email may not use identical wording. Capture all of them. Note dates, affected asset IDs, and whether delivery stopped suddenly, after a creative reject streak, after a payment failure, or after a Business Manager change. Sequence matters when you later decide whether to appeal, restructure, or pause.

Immediate steps

Start with evidence and containment. Do not improvise a full rebuild in the first hour unless you already know ownership of every critical asset. The goal is to preserve information and stop actions that typically make the situation harder to unwind.

  • Screenshot the restriction notice, related email, and any policy or payment alerts — include timestamps and asset names
  • Note which assets are affected: ad account, Page, Business Manager, domain, Pixel/Dataset, payment method, or user access
  • Pause aggressive relaunches of the same rejected creatives or landing pages without changing the underlying issue
  • Confirm who still has admin access in Business Settings and whether partner access is intact
  • Preserve Pixel/Dataset ownership details, domain verification status, and CAPI destinations before changing structure
  • Export or record active campaign structure, audiences, and recent reject reasons while you still have visibility
  • Stabilize billing: confirm cards, balances, and failed charges so a payment issue is not mistaken for a policy dead end

What NOT to do

Do not share personal Facebook passwords with vendors. Legitimate help uses Business Manager roles and partner access. Password sharing creates security risk and can complicate ownership if accounts later need recovery.

Do not create chaotic duplicate Business Managers, Pages, and Pixels without documenting ownership. Sprawl makes diagnosis harder and can leave tracking fragmented across assets nobody fully controls. If you must create new structure, do it deliberately with a written map.

Do not assume cloaking, claim-hiding, or a mismatched “safe” landing page will solve a policy problem. Those approaches typically increase long-term risk under current Meta policies and can turn a creative reject into a broader trust problem. Fix the offer, claims, and consistency — or pause advertising for that product — rather than trying to outmaneuver review.

Do not spam appeals with identical text while continuing the same rejected activity. If you appeal, make it factual and tied to a real change or a clear error. Restoration is never guaranteed; repeated low-quality appeals usually do not help.

Review workflow

A useful review separates symptoms from root causes. Work through layers in order: what Meta says is limited, what you can still access, whether payment is healthy, whether Pages and domains are verified and consistent, whether creatives and landing pages match, and whether permissions or shared assets are broken.

Account quality signals visible to you — reject rates, disabled ads, payment failures, Business verification status where relevant, and unresolved Page issues — help prioritize. So do dependencies: an ad account may look fine while a connected Page or domain problem blocks delivery. Landing-page and creative consistency matters especially for health and wellness categories, where personal-attribute language and outcome claims are often scrutinized under current Meta policies.

An appeal may be appropriate when the notice suggests a review path and you believe there is a factual error or you have already remediated the flagged issue. An appeal is less useful when the product category itself is not eligible to advertise, when claims cannot be made truthfully, or when the Business Manager layer is the real problem. Decide appeal vs restructure vs pause based on diagnosis — not panic.

  • Capture restriction scope and asset IDs
  • Check payment health and billing ownership
  • Inspect Page, domain, and Business Manager dependencies
  • Review recent creatives, reject reasons, and landing-page alignment
  • Confirm admin/partner permissions have not been silently lost
  • Choose a path: remediate and appeal, restructure cleanly, or pause the offer

When professional assessment helps

If spend is material, assets are tangled across people and Business Managers, or you are unsure whether to appeal versus rebuild, a Meta ad account health audit can prioritize next steps. A professional review typically maps permissions, restriction layer, tracking ownership, and offer risk so you do not spend weeks on the wrong lever.

Professional help is also useful when multiple teams have added partners over time, when Pixel ownership is unclear, or when you need a continuity plan that protects measurement while a spend node is limited. It is not a guarantee of restoration, unban, or future approvals. Anyone who promises a fixed outcome Meta alone controls is overselling.

Use outside help for clarity and process. Keep ownership of passwords and final decisions. Ask for a written diagnosis: what is restricted, what is salvageable, what should not be relaunched yet, and what architecture changes reduce repeat risk under current Meta policies.