Meta Business Manager and Ads Manager errors: the FAQ

Ad accounts are usually disabled by automated integrity systems responding to a signal cluster: a rejected-ad pattern, a new or mismatched payment method, a login from an unusual location, or a linked asset (page, domain, personal profile) that was itself flagged. First step: do not create a new account or portfolio, which converts a suspension into a circumvention violation. Instead, open Account Quality in Business Settings, read the stated reason, complete identity confirmation if asked, and submit the request-review form once, with a factual explanation. Most first-time flags on otherwise clean accounts are reviewed within days.

Check the rejection reason on the ad itself and the status banner in Account Quality. A single rejected ad with a specific policy citation (before-and-after imagery, personal attributes, prohibited content) is an ad-level problem: fix the creative or copy and resubmit. Repeated rejections across different ads, or a rejection immediately followed by an account restriction, means the system has flagged the entity, not the creative - stop resubmitting, because every rejected resubmission deepens the account's policy history, and review the landing page and domain as well as the ads.

Meta's billing system declines for three common reasons: the card's bank blocks cross-border or online recurring charges (call the bank and whitelist Meta), the billing name or country does not match the ad account's currency and business country, or the card was previously attached to an account with unpaid or disputed charges. A payment method with a bad history contaminates any new account it touches, so replace rather than retry a disputed card. Settle any outstanding balance in Billing before attempting anything else.

Rapid change is the trigger: a new account immediately spending at scale, many ads published in the first days, an admin logging in from a new country or device, or bulk edits to payment and permissions. The fix is patience plus verification: confirm the admin's identity when prompted, complete business verification, keep spend increases gradual (roughly twenty percent every few days on a young account), and avoid simultaneous changes to admins, payment methods and domains.

Portfolio-level restrictions aggregate the history of everything inside: pages with quality violations, ad accounts with policy strikes, payment disputes, and admins whose personal profiles are restricted. One compromised or careless admin can restrict the whole business. Audit Account Quality for the portfolio and each asset, remove people who no longer need access, resolve page-level violations first, then request review at the portfolio level. If an admin's personal profile is the flagged element, that person must resolve their own restriction - the business cannot do it for them.

Almost all verification rejections are document mismatches: the legal name on the registration certificate differs from the portfolio name (trading names are the classic failure), the address differs across documents, the document is expired or cropped, or the website domain does not match the business email domain. Align the portfolio's legal details to the certificate exactly, verify the domain first, use a document set in one consistent name, and submit once with everything correct rather than repeatedly with variations.

Delivery stops for mechanical reasons more often than policy ones: the account spending limit was reached, the payment method failed, the campaign end date passed, or the ad set budget dropped below the minimum for the objective. Learning restarts on any significant edit - budget change over roughly twenty percent, audience change, creative change, or a pause of seven days or more. Check the Delivery column status first; it names the specific blocker in most cases.

No events: the base code is not loading on the page (check with Meta Pixel Helper), a consent banner is blocking it, or a site update removed the tag manager container. Doubled events: the same event fires from two paths - typically a hard-coded pixel plus a tag manager installation, or browser pixel plus Conversions API without matching event IDs for deduplication. Keep one browser installation path, and generate a shared event ID per event instance so browser and server sends deduplicate. Verify in Events Manager's Test Events view.

Access in Meta is two-layered: portfolio-level membership and per-asset permission. Being inside the portfolio grants nothing by itself - you need explicit task access on each asset. Ask a portfolio admin to grant you the specific asset permission (for example, Manage campaigns on the ad account). If the asset belongs to a different portfolio entirely, it must be shared to yours via a partner link; you cannot request ownership of assets another business owns, only access.

If any current employee still has portfolio admin, they can remove the departed person and add a replacement - do this the day someone leaves, always. If the departed person was the sole admin, recovery goes through Meta support with proof of business ownership: registration documents, domain control, and a letter on company letterhead. This takes weeks, which is why the standing rule is two permanent-employee admins with two-factor authentication at all times.

WhatsApp enforcement runs on its own logic, separate from ad account standing: users blocking or reporting your messages, sending template messages to people who did not opt in, or sudden volume spikes on a new number. Recovery means fixing the behaviour, not appealing the rating: pause outbound templates, confirm opt-in records, warm volume up gradually, and keep message quality high - the rating recovers over days of clean sending. A restricted number can still receive messages; only outbound is limited.

No. Restrictions attach to the people, payment methods, domains and pages involved, and Meta's systems are built to detect linked entities. A duplicate portfolio or ad account created to evade enforcement is itself a circumvention violation and typically results in both entities being disabled, permanently this time. The only legitimate path is resolving the original restriction through Account Quality and review requests, however slow that feels.