Ad account restricted? A pre-launch checklist that reduces avoidable risk

Last verified against Meta's Business Help Center: . Platform policies change; the dates on this page tell you how fresh each claim is.

A single rejected ad is one thing — an account-level restriction is another. If you've lost the ability to spend, been locked out of some ad features, or had your whole business portfolio blocked, the cause may extend beyond the last ad you ran. This page covers what Meta's own Business Help Center says actually gets restricted, why, and what a pre-launch routine grounded in those stated causes looks like.

This page covers advertising restrictions on business portfolios, ad accounts, Pages, and user accounts. It does not cover a single ad being rejected during review — see why was my Meta ad rejected for that. It also does not cover account hacking recovery or payment-processor-specific holds, which have their own separate help flows.

What actually gets restricted

Meta's advertising restrictions can land on four different assets, and each behaves differently (Meta Business Help Center, About Advertising Restrictions, retrieved 2026-08-07):

Why restrictions happen

Meta separates two categories, and they carry different consequences.

Policy-violation restrictions. Meta states these apply when an advertiser doesn't follow Community Standards, Advertising Standards, Commerce Policies, or other terms; when Meta suspects a business portfolio or its assets have been compromised; or when an advertiser doesn't meet two-factor authentication requirements for account security (Meta Business Help Center, About Advertising Restrictions, retrieved 2026-08-07).

Unusual-activity restrictions. Meta states it may temporarily restrict spend limits, payment features, or the ability to add admins or create new ad accounts when it notices unusual account or payment activity, high rates of failed payments, or disputed payments — while it investigates (same source). These are framed as temporary and investigation-driven, not necessarily a finding of a policy violation.

Separately, Meta's page on common policy-violation examples names two specific behavior patterns that trigger restrictions beyond ordinary ad rejections: evading enforcement — creating new ad accounts or business assets with the intent to repeat violations after existing accounts were disabled, or coordinating a network of accounts running the same or similar policy-violating ads — and violating networks or associations, where a business asset is found closely connected to accounts or entities that violate or evade policy (Meta Business Help Center, Common examples of Meta advertising policy violations, retrieved 2026-08-07).

The pre-launch checklist

Grounded in the causes Meta states above — not a guarantee, since Meta doesn't publish a complete list of every restriction trigger:

  1. Turn on two-factor authentication before you scale spend. Meta names unmet 2FA requirements as a stated restriction cause on its own.
  2. Never open a new ad account to repeat violations after an existing one was disabled. Meta names creating replacement business assets with intent to repeat violations as an evading-enforcement example that may trigger restrictions on the new asset too.
  3. Don't coordinate a network of accounts running the same or similar ads that persistently or severely violate policy. Meta names that pattern specifically as a restriction trigger — not an isolated duplicate ad, separate from any single ad's own rejection status.
  4. Treat a rejected ad as a pattern signal, not a one-off. Meta's restriction criteria are explicitly about severe or repeated violations at the account level — fixing the recurring issue (a claim style, a targeting mistake) matters more than resubmitting the same ad with one word changed.
  5. Keep billing current and predictable. Meta names high rates of failed or disputed payments as an unusual-activity trigger, separate from any ad content issue.
  6. Know who's attached to each ad account. Meta states that if a user account is restricted, any ad account where that person is the only attached user may also be disabled — attaching more than one admin reduces that single point of failure.

If you're already restricted

Meta's stated process (Meta Business Help Center, Request a review if you are restricted from advertising, retrieved 2026-08-07): you must be an administrator on the account to request a review. Go to Meta Business Support Home, select Account status overview, select the restricted account, and choose Request review under "What you can do." Meta states its typical review takes about 48 hours, though it may take longer. If Meta determines the restriction should stand, it remains in place; if not, the account is reinstated — though ads that were running before the restriction don't restart automatically. Meta also states there's a limited number of times you can request a review, and once a review is completed, that decision is final.

What nobody can promise you — including us

Account restrictions are enforced on signals a creative-review tool structurally cannot see: two-factor authentication status, payment and billing history, whether the same person or network runs other restricted accounts, and Meta's own investigation of unusual activity. Cutsheet's Check reviews one uploaded image or video — visible text and, for video, spoken audio and on-screen text — and returns a hook/clarity/CTA/production assessment plus a verdict. It is not a dedicated Meta-policy rules engine and doesn't check your creative against Meta's Advertising Standards or evaluate any account-level signal at all.

What it can do: since it reads the same on-screen and spoken text a Meta reviewer would see, running your creative through it is one more general pass at your ad's messaging — not a policy check, not an account-safety check, and not a substitute for reviewing your own account status directly. It has no access to your account history, payment status, 2FA setting, or any other account you or your business run, and it cannot promise a restriction won't happen.

Run your ad through a Check →

Sources