Meta's Five Ban Levels: Ad, Ad Account, Page, BM, Profile — Decoded

what's the difference between a rejected ad and a disabled ad account?

A rejected ad stops one piece of creative; a disabled ad account stops every campaign the account could ever run, past, present and future. Meta's ad review system checks each ad's images, video, text, targeting and destination page against policy, and it runs primarily on automated tools rather than a single human reviewer. Most reviews finish inside 24 hours, though Meta says some take longer, and an ad can be pulled back for a second look even after it goes live.

When review finds a violation, Meta's own language draws the line for you: 'the ad will be rejected, and the Business Account or its assets may be restricted.' That second clause is the whole difference. A rejection is a creative-level event you fix and resubmit inside Ads Manager. A restriction is an account-level event, and Meta routes the appeal through Account Quality rather than through the ad itself.

Some violations are built to escalate straight past the ad stage. The conduct Meta used to police under a standalone 'Circumventing Systems' policy now lives inside Account Integrity, which covers accounts repurposed to dodge a prior ban or otherwise built to evade review — the mechanics of that specific ban are covered in why Meta disabled your account for circumventing systems. Account Integrity findings rarely leave a trail of rejected ads on the way to a disabled account; they usually skip straight to it.

why is my business manager disabled but my ad account still works?

Because Meta enforces against the specific asset it flagged, not automatically against every asset connected to it. Meta's Advertising Standards restrict 'that account or asset' — singular, not the whole portfolio — so an ad account can keep spending after its business manager gets disabled if it sits under different effective ownership or was only shared into the flagged BM through partner access rather than owned by it. Three patterns explain most of these split states:

None of this means the ad account is safe long-term. If the BM disable was an evasion finding, Meta's Account Integrity standard explicitly extends to assets with 'common ownership' to a previously removed account, and diagnosing which layer actually failed before filing anything is the first move; see diagnose before appealing for the checklist.

• The ad account is owned by a separate Business Account and only shared into the disabled BM, so it keeps its own standing.
• The violation attached to a Page or a user account inside the BM, not to the ad account itself, and Meta's asset-level enforcement stopped there.
• The disable is mid-propagation: Account Integrity cases can restrict 'accounts, entities or business assets' in a widening set, and the ad account simply hasn't been reached yet.

can a restricted personal profile take down a healthy business manager?

Not automatically — Meta's own Advertising Standards say that when a user account is restricted, 'other members of the associated Business Account or Page may still be able to advertise.' A business manager with more than one admin does not go dark because one profile gets flagged.

The exposure concentrates on whoever is the sole attached user. If your restricted profile is the only admin on a given ad account, that ad account is the one at risk, not the BM as a whole. Community reports describe a worse state above simple restriction: advertisers say Meta has banned their 'entire account and any account with my name,' with freshly made profiles picking up new bans within days of creation. That is identity-level enforcement, not asset-level, and no published Meta document names it as a distinct category.

A restricted profile and a hacked profile are not the same problem and don't share a fix. A takeover changes account credentials and admin lists without any policy violation on your part, and Meta's restoration process for that scenario looks different from an appeal — see how business manager takeovers happen and what Meta restores before assuming a restriction is what you're dealing with.

what happens to my pixel and page when an ad account is disabled?

The pixel and its custom audiences typically stay intact even when the ad account that fired them goes dark. Delivery drops to zero the moment the account is disabled, but practitioners consistently report that the pixel itself, its event history and saved audiences remain visible and reusable once a working ad account is reattached — Meta doesn't confirm this in writing, but it's the consistent operator experience.

The Page is a separate asset with its own enforcement track, and a disabled ad account doesn't delete it or reset its history. Where the Page can suffer independently is its Customer Feedback Score: operators widely report a penalty band starting under 2.0 and a hard advertising block under 1.0, drawn from roughly the last 60 days of post-purchase surveys, and this is one of the rare cases where community observation and Meta's own published behavior line up, since Meta's original feedback announcement states it will 'reduce the amount of ads that particular business can run' when feedback stays poor.

Catalogs, product sets and other Business Manager-level assets follow the same logic as the pixel: they belong to the business asset, not the ad account, so they survive an ad-account-level disable. What they can't survive is a Business Account-level restriction, since that's the layer that actually owns them.

do bans cascade from one asset to the others?

Yes, along ownership and identity lines, though Meta has never published the exact rules for how far a cascade travels. Its Account Integrity standard states outright that accounts, entities or business assets with 'common ownership' to a previously removed account 'may be restricted or disabled,' which is about as close as Meta gets to confirming cross-asset spread in writing.

Operators describe the trigger as asset association: shared admins, reused payment methods, shared pixels, shared domains or one prior banned profile pulling down accounts that never spent a dollar — one widely shared account was flagged despite never running an ad, on a Page dormant for seven years, with no payment method even attached. The device-and-browser-fingerprint version of this theory gets repeated constantly in advertiser communities, but its loudest advocates are antidetect-browser vendors with an obvious commercial interest in advertisers believing it, and Meta has never confirmed fingerprint-level linking. That particular explanation deserves less weight than the ownership and payment-method signals Meta does describe in its own policy.

Meta is also working the supply side of this problem directly. In February 2026 it sent cease-and-desist letters to eight former Meta Business Partners accused of running phony ad-account restoration services and renting out trusted accounts so clients could evade enforcement, alongside separate lawsuits against scam-advertiser networks — who gets sued versus who gets a warning letter is mapped in the ban-evasion economy.

how do I find out which asset is actually restricted?

Open Account Quality first — it's the one panel that reports status per asset rather than for whichever account you happen to be logged into. It will separately show the state of ad accounts, Pages and the Business Account itself, and that separation tells you whether you're dealing with a Page problem, an ad-account problem or a business-manager problem before you write a single word of appeal. Work down this ladder if Account Quality doesn't resolve it:

• Business Help Center live chat, for a human read on what Account Quality won't explain.
• A Meta partner agency or an assigned rep, if the account has one — operators consistently describe a real relationship as the biggest single factor in whether a case gets human attention at all.
• The in-platform Request Review button is reported as greyed out or non-functional on a subset of accounts in 2026, which pushes those cases straight to Business Help Center.

which level of ban does each appeal form actually target?

Each restriction layer has its own appeal path, and using the wrong one wastes the turnaround window instead of speeding it up. Ad-level rejections go through the 'Request review' option attached to the specific ad; account and business-manager-level restrictions go through Account Quality's broader appeal flow; a Page's feedback-score penalty has no appeal form at all and only clears through operational fixes over time.

None of these paths carries a Meta-published turnaround guarantee. Operators report 24 to 72 hours for straightforward ad-account cases, up to roughly 30 days for complex ones, and three failed appeals over 30-plus days as the practical point where rebuilding becomes more realistic than continuing to appeal — a sequence detailed step by step in how to appeal a disabled Meta ad account.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Meta Ad Library, Meta advertising standards, and Google helpful content guidance. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Daily Intel for offer owners and producers, Building the Chargeback Function in a Five-Person Offer Business, Peptide and GLP-1 Disputes: Higher Tickets, Shorter Runways, Split Liability, The Chargeback Cascade: What Breaks First, and in What Order, Your Support Desk Is a Chargeback Prevention System, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.