Meta ad account disabled: what to do in the first 48 hours

When a Meta ad account is disabled, four things belong in the first 48 hours: read the stated reason and the restriction type correctly, build an evidence file that can win on the first attempt, separate your business assets and team access so nothing else falls with it, and quantify the revenue impact so budget can move to surviving channels. Order matters. An appeal fired off against a misread reason spends one of the few review attempts you get.

Meta ad account disabled: what order should you work in?

The order is this. Read the notification and the Account Quality screen to establish whether the restriction sits at ad-account level or business-portfolio level. Then collect evidence that answers the stated reason directly. Third, submit a single clear request for review. Fourth, move the stalled spend to surviving channels and track the daily revenue gap. All four fit comfortably inside 48 hours.

How do you read a disabling notice correctly?

An ad account disabling is Meta suspending an account's ability to deliver and spend, temporarily or permanently. Two details in the notice decide everything: which asset was restricted, and which policy heading was cited. A third detail matters just as much, namely whether a request-review link appears on the same screen. If it does not, the restriction usually sits in a heavier class and the path is different.

• Pending review: delivery stops but no decision has been made. Many cases resolve on their own; appealing at this stage is unnecessary.
• Payment-driven shutdown: a failed charge or an outstanding balance. The fix is not an appeal but clearing the balance and updating the payment method; accounts typically re-enable on their own within 24 hours.
• Policy-driven shutdown: the creative, the copy, the landing page or a vertical-specific rule is cited. This is where a request for review actually earns its keep.
• Linkage-driven shutdown: a previously restricted Page, card or personal profile ties the new account to the old problem, and the new account goes down too.
• Severe violation: for headings like fake identity or deceptive billing, reinstatement rates are low and a review option may not be offered at all.

What evidence belongs in the appeal?

A good request for review is not a defence letter, it is an evidence file. The reviewer decides in a short window, so the file must be short, verifiable and matched one-to-one against the cited reason. The sequence below is the one that moves with the least friction in practice.

1. Collect the screenshot, the date and the affected asset IDs (ad account, Page, business portfolio) in one document.
2. Attach documents that answer the reason head-on: business registration, proof that the payment method is yours, domain ownership, real order and refund records, a working customer-service channel.
3. If a policy breach is alleged, take the ad down or fix it. The disputed content should not still be visible while the review runs.
4. Keep the text short. Explain what you sell, how you meet the cited policy and what you changed, in three paragraphs. Emotional language, threats and copy-pasted templates change nothing.
5. Submit from an account with admin rights on the business portfolio. Only admins can open a review request; someone on employee access will not even see the link.
6. Send one request and wait. Filing repeatedly on the same grounds does not jump the queue and usually consumes your remaining attempts.

How do you protect business assets and team access?

In a properly built structure, a disabled ad account does not erase your data layer. Pixels, conversion events, custom audiences, catalogs and Pages belong to the business portfolio; the ad account is only the delivery and spend layer. The real risk is a single-admin portfolio where that one person is locked out too. Handle the access side inside the same 48 hours.

• A second admin: keep at least two full admins on the business portfolio. If your only admin is locked out, nobody is left who can file the appeal.
• Two-factor authentication: mandatory for everyone who can spend. Suspicious access quietly accounts for a share of disablings.
• Partner access, not ownership: agencies should reach client assets through partner relationships rather than taking ownership. A restriction on one side then does not travel to the other.
• System users: separate automation and reporting access from personal profiles, so staff turnover never walks away with your infrastructure.
• Export while you can: back up the reports and audience source lists you can still export. If the source data lives in your own systems, rebuilding audiences takes hours instead of days.

How do you limit the revenue impact of downtime?

What you lose during downtime is not the unspent budget, it is the revenue that budget would have produced. So the day-one task is to put a number on the stalled account's daily contribution and see how much of it other channels can realistically absorb. Budget shifts made without measurement usually break ROAS.

• Measure first: lock in the stalled account's 14-day average daily revenue and spend. That is your cost of downtime.
• Then shift: move budget to channels that reach the same audience and are far from saturation, not at random. Prioritise branded search and remarketing on Google Ads.
• Lean on owned channels: email, organic social and existing-customer campaigns recover the fastest during an outage.
• Watch the site side: if landing-page errors or slowdowns go unnoticed during downtime, you lose the first day again once the account returns.
• Ramp back slowly: when delivery resumes, do not jump straight to the old daily budget. A staged increase protects both the learning phase and your risk of a fresh restriction.

The most common mistake during downtime is reading the loss only from the disabled account's own screen. Once Meta, Google Ads, TikTok and GA4 data sit in one place, you can separate revenue that actually vanished from revenue that simply moved to another channel. Ads Sensor's round-the-clock anomaly and site-health monitoring acts as a second pair of eyes on those days; it does not run your appeal, but it does show where the damage is accumulating. Join the beta to watch all accounts in one dashboard.

How do you build a setup that prevents a repeat?

An account that went down once will go down again if the structure stays the same. A durable setup rests on three legs: assets separated from each other, permissions tight and reviewable, and risky ad content checked before it goes live. With those three in place the residual risk does not hit zero, but it becomes manageable.

1. Asset separation: every brand or client sits in its own business portfolio, with its own Page and its own payment method. Reusing one card across portfolios is the most common way a restriction spreads.
2. Access hygiene: review the access list quarterly. No departed employees, no expired agency contracts, no unused system users.
3. Risky content review: have a second person read copy touching health, finance, weight, income claims or personal attributes before launch. One reworded sentence can change the policy class entirely.
4. Landing-page consistency: the promise in the ad should appear verbatim on the page, with contact details, refund terms and pricing in the open.
5. Regular audits: once you get the account back, review the structure from scratch; a dedicated checklist is the fastest route.

Do you have extra appeal rights in the EU?

For advertisers operating in the European Union, the Digital Services Act opens a second path. Platforms must issue a reasoned statement for decisions such as account suspension and keep the internal complaint mechanism open for six months from the decision. If that route fails, Article 21 of the DSA defines out-of-court dispute settlement, where a certified body reviews the case again.

Two practical consequences follow. First, a rejected in-platform appeal is not the end of the process. Second, building the evidence file properly from the start pays off in the second stage too, so keep the text of the reasoned statement. Outside the EU this extra path may not exist, which makes the quality of that first in-platform request even more decisive.