Your Meta ad account gets restricted, campaign delivery stops, and the clock starts ticking. Most advertisers either panic and create a new account (triggering a permanent ban) or wait passively for Meta's review to resolve itself (losing days of campaign momentum in the process). Neither approach is acceptable for performance marketers who depend on continuous delivery.
Meta's Account Quality hub now provides a structured appeal pathway, and understanding how to use it correctly is non-negotiable. But the process has hard limits: review attempts are finite, accounts inactive for more than 180 days cannot be reinstated, and response times are measured in days rather than hours.
This guide covers everything you need to navigate a restriction without compounding it. You will learn the seven reasons accounts get flagged, what to audit before submitting an appeal, how to work through the formal review process step by step, and why activating a parallel infrastructure solution during that review window is the only strategy that genuinely protects your campaigns. By the end, you will have a clear, actionable framework for handling account restrictions without surrendering delivery momentum to Meta's timeline.
Meta's Account Quality hub is the centralised dashboard inside Meta Business Support Home for managing restrictions, disapprovals, and policy flags across your meta ad account and every linked asset under your Business Manager.
Notifications inside it fall into three distinct categories:
Account-level restrictions, which halt all delivery immediately
Ad-level rejections, which require a per-ad fix or appeal
Portfolio-level restrictions, which sit at Business Manager level and require remediation there, not at individual account level
The distinction between the first two matters more than most advertisers realise. Account-level restrictions are compliance signals. They stop delivery entirely and require a formal review. Ad-level diagnostics are performance signals. They flag efficiency losses but do not necessarily stop spend. Submitting a formal account review for an ad-level rejection wastes one of your limited appeal attempts and solves nothing.
Meta formalised this review pathway as a structured alternative to general support tickets. Formalised does not mean fast. Meta's documentation states reviews typically complete within 48 hours, though longer timelines apply in many cases, and advertiser experience bears that out.
There are also hard limits on the process itself. Decisions are final once a review completes. The number of review requests per account is capped. These constraints are not theoretical. Understanding them before you submit determines whether you use the process effectively or exhaust it without resolution.
Knowing your restriction category before you appeal is not optional. It determines what evidence you need, what you write, and whether reinstatement is realistic.
The seven categories, with approximate 2026 prevalence:
Circumventing Systems (35%). The largest single cause of a disabled Facebook ad account. Triggers include accelerated spend patterns, rapid payment method changes, and activity Meta's automated classifiers read as policy-evasion, even when the intent is entirely legitimate.
Unacceptable Business Practices (20%). Landing pages, ad claims, or offers that conflict with Meta's commerce policies. The advertiser often believes the content is compliant. Meta's classifier disagrees, and that is what counts.
Payment and Billing Issues (15%). Typically the fastest to resolve. Most payment-related restrictions clear within 1 to 3 days once the underlying billing problem is fixed.
Compromised Account or Unusual Activity (10%). Requires identity verification steps before Meta will review the account. Act on these immediately.
Repeated Ad-Level Disapprovals (10%). Preventable. Running ad-level compliance checks before launching new creatives stops this from accumulating into an account-level flag.
Restricted Content Categories (5%). Certain product and service types face additional scrutiny by default. Check Meta's restricted categories list before launching in new verticals.
Identity Verification Failure (5%). Requirements escalate with account age, spend velocity, and geographic expansion. Completing verification proactively, before it is demanded, removes this risk entirely.
The category label in your Account Quality dashboard is the starting point for everything that follows.
Once you know which restriction category applies, the next step is diagnosis before action. Rushing straight to the appeal form without this check is one of the most common reasons appeals fail or resolve the wrong problem.
Go to Meta Business Support Home and select Account status overview. Confirm whether the restriction is at ad level, account level, or Business Manager level. Each requires a different fix. An ad-level rejection needs per-ad remediation, not a full account appeal. A Business Manager-level restriction disables every ad account underneath it simultaneously, so appealing a single account first will not restore delivery.
Read the restriction reason carefully. Meta's notices are often brief, but the category label tells you which policy area triggered the flag and what evidence or changes are likely to matter in your response.
Do not create a new personal ad account while your appeal is in progress. Meta treats this as evasion. The typical outcome is a permanent ban on both the original and the new account, converting a recoverable situation into an unrecoverable one. This single mistake ends more accounts than the original restriction does.
Finally, check the account's age. Accounts disabled for more than 180 days cannot be reinstated. If you are inside that window, submit immediately. If you are outside it, the account is gone and continuity becomes the only priority.
Once you have confirmed the restriction type and verified your account is within the 180-day window, submit the appeal using these steps.
Go to business.facebook.com/support. Under Account status overview, find the restricted ad account and click See details.
Identify the restriction category from the policy notice. If it references Circumventing Systems, the largest single disablement cause at around 35% of cases, prepare evidence that your spend patterns and payment changes had clear operational reasons. A budget spike tied to a product launch, or a payment method change linked to card expiry, reads differently with documentation behind it.
Click Request review. Write a factual explanation: what your business does, what activity likely triggered the flag, and why it does not breach the stated policy. Keep the language plain. Reviewers handle high volumes, and a concise, specific explanation is easier to process than a long one.
Complete identity verification immediately if it is required. Every day of delay is a day lost inside your 180-day reinstatement window.
Check the Account Quality dashboard daily after submitting. Meta may request additional documentation. Missing a follow-up request can cause the review to close without a resolution, with no further appeal available.
If the decision comes back as valid, accept it and move on. Continuing to contest a finalised ruling on the same account produces no result. The focus shifts to how quickly you can restore campaign delivery through other means, which the next section addresses directly.
Meta's own guidance states reviews typically complete within 48 hours, though many cases, particularly Circumventing Systems flags, take longer.
Once you have submitted the review, the waiting begins. Meta's stated window is 48 hours, but that figure applies to straightforward cases. Circumventing Systems flags, which account for roughly 35% of all disablements, routinely take longer. For a DTC brand with active campaigns, two to five days of dark accounts means lost revenue, cooling audiences, and competitors absorbing the inventory you vacated.
The standard advice is to submit and wait. That is incomplete.
Passive waiting while an automated review runs means your campaigns stop, your pixel data goes cold, and your retargeting pools shrink. Every day of downtime compounds the recovery cost when delivery eventually resumes.
The critical constraint is this: creating a new personal ad account while an appeal is in progress signals evasion to Meta's systems and typically results in a permanent ban on both accounts. That option is off the table.
Using a managed agency account is a different matter entirely. An agency ad account operates under a separate Business Manager, provisioned and owned by an infrastructure provider. It already exists. You are not creating anything new in your own name. This is the same structure that agencies have used to manage multiple client accounts safely for years. It is standard advertising infrastructure, not a workaround.
Submitting the appeal and activating an agency account in parallel protects campaign continuity without creating additional risk to your primary account. These are two separate actions with no conflict between them.
Circumventing Systems accounts for roughly 35% of all Meta ad account disablements, and it is the category most likely to contain false positives. Meta's automated classifiers are built to detect evasion behaviour, but the patterns they flag overlap directly with normal performance marketing operations.
Rapid budget scaling, frequent payment method changes, logging in from multiple devices or IP addresses, and launching many ad sets in quick succession are all routine for a high-velocity DTC advertiser. They are also flagged by the same system that catches genuine violations.
If your account carries a Circumventing Systems label and you believe it is a false positive, your appeal must be specific. Generic appeals fail. For each activity the notice references, provide the business context.
A budget increase tied to a confirmed product launch reads differently from an unexplained spike. A new payment method added the week a card expired reads differently from repeated payment cycling with no clear reason.
Useful records to keep before and during a restriction:
Payment method changes, with dates and reason (card expiry, billing account migration)
Spend increases linked to campaign events such as seasonal peaks or product launches
New login locations tied to team hires or agency access grants
These details are what separate a false positive from a genuine violation in a reviewer's eyes.
A well-documented appeal improves your position. It does not guarantee reinstatement. Treat the appeal as a necessary step, not a reliable recovery mechanism, and keep your backup account infrastructure running alongside it.
So the appeal is submitted. Now the question is what happens to your campaigns while you wait.
An agency ad account is an account provisioned and owned by a specialist infrastructure provider, operating under a Business Manager that has no connection to the one affected by your restriction. It may be dedicated to your brand or shared across clients, depending on the provider's model.
The compliance distinction matters. When you activate an agency account during an appeal, you are not creating a new account in your own name. You are using existing, compliant infrastructure that already operates independently. Meta's evasion detection targets advertisers who open new personal accounts to replace restricted ones. That is not what this is.
The practical case comes down to timing. AdBear typically delivers a working Meta ad account within two hours. The appeal window is 48 hours at minimum, often longer for complex cases. Running both in parallel is the straightforward response to that gap.
Your campaigns stay in your own Ads Manager throughout. You continue managing creatives, targeting, and budgets exactly as you normally would. The infrastructure provider handles the account layer, including compliance flags, account health, and billing stability.
Balance top-up speed also matters here. A campaign already behind after downtime cannot afford a second delay caused by slow payment processing. Near-instant top-ups keep delivery moving once the account is active.
Finally, month-to-month terms mean no long-term commitment during an uncertain period. You use the infrastructure for as long as it serves the situation, then reassess.
Once the decision arrives, act on it immediately.
If the restriction is lifted, do not switch campaigns back on straight away. First, open the Account Quality dashboard and confirm no secondary flags remain. Check every active ad individually for policy compliance. Verify that your payment method is valid and verified. Only then reactivate.
When you do start spending again, ramp slowly. Increase daily budgets over several days rather than returning to peak spend in one move. A reinstated account that immediately resumes high-velocity spend can trigger the same automated classifiers that flagged it the first time.
If the decision is permanent, close the account as an operational asset. The agency account infrastructure you activated during the review period is now your primary delivery environment. There is nothing productive in continuing to contest a final decision, and attempting to do so risks consuming time and focus that belongs on recovery.
Either way, use the disruption to audit your broader setup. Single-account dependency is the root cause of most campaign continuity failures. Brands that have backup accounts in place before a restriction occurs recover far faster than those who start looking for alternatives after the flag appears.
Finally, document everything. Record what triggered the restriction, what the appeal process revealed, and what you would do differently. That record makes your compliance practices sharper and any future appeal more specific and better supported.
The steps above cover the full process. This is where it compresses into a single operating principle.
Submit the appeal the moment a restriction appears. Use Meta Business Support Home, identify the correct restriction category, and write a factual, specific explanation. Do not submit a vague appeal and wait.
Then act on continuity immediately, without waiting for the outcome. Meta's review window is typically 48 hours, and complex cases run longer. That is days of dark campaigns, cold audiences, and lost revenue. Passive waiting is not a strategy.
The compliant way to keep delivery running during a review is through an existing agency account infrastructure. Not a new personal account, which Meta treats as evasion. Not a workaround. A properly provisioned agency ad account, operating under a separate Business Manager, is legitimate infrastructure. It is how agencies have managed multiple clients safely for years.
If you are running significant paid social budgets without backup account infrastructure in place, that is the gap to fix now, before a restriction appears. The advertisers who recover fastest are the ones who already have a second account ready when the first one goes down.
AdBear provisions Meta ad accounts, typically within two hours, with near-instant balance top-ups and WhatsApp support from a real operations team. If you want to close that gap, visit adbear.co to start a conversation.
A restricted Meta ad account does not have to mean a dead campaign. The advertisers who come out ahead treat every stage of this process as an active decision: submitting a precise, well-documented appeal immediately, maintaining delivery through legitimate agency account infrastructure, and never simply waiting for Meta to respond.
Three things determine how fast you recover: the speed of your appeal, the specificity of your documentation, and whether backup infrastructure exists before you need it. All three are within your control.
The time to build that infrastructure is now, not mid-restriction when revenue is already bleeding. Prepare your appeal process, understand your account's risk profile, and close the gap on backup delivery capacity.
If you want a provisioned agency account ready before the next restriction appears, visit adbear.co and start that conversation today.
.svg)