A Meta advertising restriction is not one generic “Facebook Ads ban.” Meta can restrict a person’s advertising access, a Page, an ad account or an entire Business Portfolio. A rejected ad, failed payment, compromised administrator and Events Manager data restriction can also stop delivery without being the same enforcement event. If the team diagnoses the wrong object, it can fix the wrong thing and spend a limited review opportunity on an irrelevant explanation.
The first move is to preserve the notice and identify the exact restricted asset in Meta Business Support Home. Then separate policy, security, identity, payment, destination, category and data-use evidence before changing campaigns. Meta’s own guidance places account status, outstanding issues and available actions in Business Support Home (Meta: About Meta Business Support Home).
This guide is for legitimate founders, heads of growth, paid-social operators, app teams and compliance owners. It is not legal advice, a workaround manual or a promise that Meta will restore access.
The short answer: what should you do when a Meta ad account is restricted?
When a Meta ad account is restricted, capture the exact notice, account and portfolio IDs, affected asset, policy label and available action before editing anything. Check whether the restriction belongs to the ad account, a person, Page or Business Portfolio; rule out a rejected ad, failed payment, security incident and data-source restriction; correct the controlling issue; then have an authorized administrator use the review path displayed in Business Support Home.
Do not open a replacement portfolio or account, borrow another person’s profile, rotate domains or submit altered documents to keep advertising. Meta’s Advertising Standards and training material identify evading enforcement, inauthentic accounts and problematic connected networks among the behaviours that can lead to business-asset restrictions (Meta Blueprint: Understanding Meta Advertising Standards).
The working question is not “How do we get Facebook Ads back?” It is: which asset is restricted, which rule or risk signal controls the decision, and which evidence proves that the underlying problem was corrected?
Start with the restricted asset, not the campaign
Meta’s advertising-restriction guidance distinguishes four scopes. Each changes who can act and what else may stop.
Restricted object Practical effect Evidence to preserve first Responsible owner --- --- --- --- Personal profile The person may lose the ability to advertise or create ads across assets they manage Profile notice, identity/security prompts, affected portfolios and account roles The affected person and a trusted portfolio administrator Page The Page cannot advertise Page ID, notice, Page access, recent content and connected accounts Page owner and compliance/brand owner Ad account The account, its ads and some connected advertising assets are disabled Ad account ID, account-status notice, rejected ads, billing and destination state Ad account administrator and paid-media owner Business Portfolio The portfolio cannot advertise, potentially affecting owned accounts and assets Portfolio ID, all outstanding issues, people/partner access, verification and owned assets Business owner with full access
Meta says restrictions may be applied when an advertiser does not follow its standards or terms, when it suspects compromise, when account-security requirements are not met, or when payment and other account activity create risk (Meta: About advertising restrictions). That does not establish the cause of a specific account. The controlling evidence is the notice shown for that asset.
A restriction on one person is not interchangeable with a restriction on the business. A clean ad account view does not prove that every administrator can advertise. Conversely, a rejected ad does not automatically mean the whole account is restricted. Record each object separately before asking anyone to “fix the account.”
Rule out five lookalike delivery stops
Several operational failures are commonly described as a disabled account even though they require different evidence and actions.
1. One ad was rejected
An ad rejection is an ad-level decision. Meta says the rejection notice and reason appear in Business Support Home, where an advertiser can edit the ad or request another review when eligible (Meta: How to troubleshoot a rejected ad). Preserve the rejected version, policy reason, creative, copy, targeting and final destination before editing.
2. A payment failed
A failed payment can pause ads and disable the ad account until the amount due is resolved. Treat that as a billing incident first: preserve the billing notice, invoice, payer, payment-method status and bank response, then use Meta’s supported billing path (Meta: Fix a failed payment issue). Do not move charges to unrelated cards or entities to make the notice disappear.
3. A person or asset may be compromised
Unexpected administrators, unfamiliar sessions, changed payment details or unauthorized ads point to security containment before a policy argument. Preserve alerts and access history, remove unauthorized access through supported controls, restore trusted administrators and follow the security steps shown in the account. A compromised profile can contaminate the diagnosis if the team immediately deletes the evidence or gives another unknown “recovery specialist” full control.
4. Business or identity verification is incomplete
The account may require the business to reconcile its legal name, address, contact method, domain and supporting records. Meta’s verification flow is managed through the business’s Security Center and must be completed by someone with the relevant access (Meta: How to verify your business). Verification is not a universal cure; it only resolves the facts the verification step controls.
5. Event data is restricted
An Events Manager data-sharing restriction can limit which website or app events Meta receives or uses. It is not necessarily an advertising-account restriction. Meta says these notices are communicated by email and in Events Manager, and the advertiser remains responsible for its Business Tools integration and the data it sends (Meta: Understand data sharing restrictions). Diagnose the data source, event fields and category separately from the account’s advertising status.
Build a Meta restriction incident record
Before making corrective changes, create one record that another administrator could reproduce. Include:
The exact notice text, date and status shown in Business Support Home.
The restricted object type and its ID: profile, Page, ad account or Business Portfolio.
The policy, security, identity, payment, verification or data label shown by Meta.
Every action listed under “What you can do,” including steps that must precede a review.
The administrator who can see and act on the notice.
Affected ads, Pages, accounts, catalogs, datasets, apps, domains and payment profiles.
The original creative, copy, targeting and final destination for relevant ads.
Business identity, domain, app publisher, licence and category evidence when material.
Billing notices, invoices and payment ownership when material.
People and partner access, recent changes, security alerts and unusual activity.
Prior review requests, case IDs, decisions and correspondence.
A dated change log for the seven days before the restriction and every correction after it.
Do not delete rejected ads, disconnect assets or rewrite business details merely to produce a cleaner screenshot. Preserve the before-state first. The review should be able to distinguish what Meta saw, what the team corrected and how the correction was verified.
Use an enforcement-layer map before requesting review
Map the notice to a layer rather than sending one generic appeal.
Layer Diagnostic question Typical evidence Correction before review --- --- --- --- Asset scope Which profile, Page, account or portfolio carries the restriction? Business Support Home status, IDs, permissions Work from the affected object with an authorized administrator Policy Which standard and which ad, destination or business practice are named? Rejection history, creative, copy, targeting, landing page Correct the named policy mismatch across every affected surface Identity and verification Do entity, domain, payer, app and documents describe the same legitimate business? Security Center state, registration, domain and role records Reconcile genuine records; explain legitimate entity relationships Security and access Was an administrator or asset compromised? Alerts, sessions, access history, unauthorized changes Contain access, restore security and document unauthorized activity Payment Is delivery stopped by an amount due or payment-risk issue? Billing notice, invoice, payment owner, bank response Resolve the supported billing problem with the legitimate payer Destination and product Does the live page or app match the ad and eligible product? Final URLs, redirects, mobile/market tests, store listing Restore a functional and truthful path consistent with the ad Category and market Is the product eligible for this market, audience and account setup? Product function, licences, age/geo controls, permissions Confirm eligibility and evidence before relaunch Data use Is Events Manager restricting an event source rather than advertising access? Dataset notice, event payload fields, category and consent records Repair the integration and data governance separately
One business can have more than one layer open. A failed payment does not disprove a policy restriction. A verified business can still run an ineligible product. A compliant landing page cannot restore a compromised administrator. Resolve dependencies in the order shown by the evidence.
Reconcile ownership and permissions
Only the right person can complete some steps. Meta’s permissions model distinguishes people with full access from those with task access, and portfolio-level access from access to individual assets (Meta: Business portfolio and business asset permissions). Build an access table before the review:
Asset Business owner Full-access administrators Agency or partner role Review authority Exit owner --- --- --- --- --- --- Business Portfolio Legal business Named trusted people Partner business where applicable Confirmed administrator Legal business Ad account Portfolio or documented owner Named trusted people Campaign/task access Administrator shown in the restriction Legal business Page and Instagram account Brand owner Named trusted people Content/ads tasks Administrator if Page is restricted Brand owner Pixel, dataset or app Business/product owner Named technical owners Minimum integration access Dataset administrator Business/product owner Domain and payment profile Legal business Authorized operations/finance owners No shared credentials Authorized owner Legal business
An agency can help organize evidence and operate eligible campaigns, but it should not impersonate the advertiser, become the undocumented owner or ask for personal passwords. Use supported partner and task access. If the real owner cannot see the restricted asset, access governance is part of the incident—not an administrative detail to postpone.
Correct in dependency order
Unless the account notice requires another sequence, use this order:
Contain compromise and payment risk. Secure people and assets, preserve unauthorized changes and resolve any controlling billing issue.
Identify the exact restricted object. Do not appeal from a different Page, account or portfolio because it is easier to access.
Confirm product and market eligibility. A review cannot make an ineligible product, audience or geography eligible.
Reconcile ownership and verification. Align the legal business, portfolio, account, payer, domain, app and supporting records.
Repair the destination and product representation. Test final URLs, redirects, mobile behaviour, app/store identity, disclosures, offer terms and market availability.
Correct the named ads and business practices. Address the actual policy issue across creative, copy, targeting and landing pages.
Validate the complete chain. Have an accountable owner verify each correction against the preserved before-state.
Request review from the affected asset. Use the current action displayed in Business Support Home and submit a concise evidence packet.
Meta’s troubleshooting guidance says the available steps can include confirming identity, completing verification, securing the account and requesting review; the combination depends on the restriction type and the stage of the process (Meta: Troubleshoot a disabled or restricted account). Complete prerequisite actions instead of treating the missing review button as proof that no path exists.
What if there is no “Request review” button?
Do not infer a hidden reason from the missing button. Check observable facts:
Are you signed in as an administrator of the restricted asset?
Are you viewing the correct profile, Page, ad account and Business Portfolio?
Does “What you can do” require identity, verification or security work first?
Is the issue an ad rejection, billing failure or data restriction with a different route?
Has a review already been completed for this decision?
Does Business Support Home show an official contact-support option for this account?
Meta’s public review guidance says an administrator may be able to request review in Business Support Home by selecting the restricted account and following the action shown there (Meta: Request a review for a restricted advertising account). It does not establish that every account receives the same button, number of reviews, support channel or outcome. Record what the private account actually displays.
Do not use unofficial appeal forms, paid “insider” access or a borrowed profile as a substitute for the account’s available path. Do not send passwords, authentication codes, complete payment credentials or unnecessary personal data to an agency or supposed Meta representative.
What belongs in the review packet?
Keep the submission narrow enough for a reviewer to verify:
The restricted asset type, ID and exact notice.
The legitimate business, product, app, website and target markets.
The named policy or risk layer and the affected objects.
A short factual root-cause statement, including uncertainty where it remains.
A policy-to-asset table listing each issue, correction, owner and proof.
Before-and-after evidence for ads, destination, verification, access, billing or data use as applicable.
Authentic licences, registrations or authorizations only when the product and market require them.
A timeline of relevant changes and prior reviews.
A relaunch-control plan that prevents the same mismatch from recurring.
Avoid generic apology templates and unsupported claims that the business “has always complied.” State what was observed, what changed and how the team verified it. The platform decides the review; the operator’s job is to make the evidence coherent.
Tactics that can make the enforcement problem worse
Do not:
Create or buy a replacement ad account or Business Portfolio to continue the same activity.
Borrow, rent or create another personal profile to hide the restricted administrator.
Use proxy owners, unrelated payment methods or fabricated agency relationships.
Alter, crop, watermark, mislabel or forge verification and licence documents.
Rotate domains, apps, redirects or Pages so reviewers and users see different products.
Hide words or claims with symbols, images or deliberate obfuscation.
Re-submit the same ads or conflicting review stories from several assets.
Give a “recovery service” full control, credentials or authentication codes.
Claim a security incident without access evidence or erase the changes that would establish it.
These are not durable operating solutions. They can add account-integrity and evasion concerns to the original incident. Meta’s public Advertising Standards are the controlling policy reference, not an online seller’s promise of a “stable” replacement account (Meta Advertising Standards).
A fictional diagnosis
Consider a fictional subscription app whose ad account stops spending after several rejected ads. The growth team assumes the creative language caused an account ban. The incident record shows four separate facts: two ads were rejected, the payment profile has an amount due, a former contractor still has full access and Business Support Home places the active restriction on that contractor’s personal advertising access rather than on the app’s ad account.
The right response is not one appeal about ad copy. The business preserves all four notices, removes unauthorized or obsolete access through supported controls, resolves the legitimate billing issue, corrects the rejected ads and landing-page claims, and has the affected person follow the profile-level action Meta displays. The business also records who owns the portfolio and which administrators can act if one person loses access.
This example does not predict restoration. It shows why asset scope, dependencies and ownership must be established before a campaign team changes ads.
Relaunch safeguards if advertising access returns
Restored access is not evidence that every campaign is compliant, measurable or commercially ready. Before turning spend back on:
Reconfirm which profiles, Pages, accounts and portfolios are eligible.
Use only documented business owners, administrators, partners and payment methods.
Test the final destination, app/store identity, offer, disclosures and market eligibility again.
Recheck the current policy for regulated products, age or location restrictions and required authorization.
Keep a register connecting each live ad to its product, market, destination, claim evidence and accountable owner.
Separate policy status, billing, security, Events Manager data quality and campaign performance in monitoring.
Start with a bounded scope that the preserved evidence supports.
Record who may change creative, domains, verification details, payment methods and access.
Stop the affected campaign when the ad, product or destination no longer matches the approved operating record.
For gambling, real-money gaming, social casino, sweepstakes or chance-based mechanics, use the separate gambling account-suspension framework before assuming this general workflow is sufficient. A TikTok restriction follows a different Account Health and appeal diagnostic. Teams comparing another channel after the incident can use the Meta Ads versus TikTok Ads decision framework; channel fit should be decided after eligibility and access are known.
When an outside account and campaign audit is useful
An outside team cannot see a private Meta account from a screenshot alone, guarantee a review outcome or replace legal counsel. It can help a legitimate operator build one accountable view across Business Support Home, ownership, permissions, product classification, ads, destination, app/store presentation, billing, security, data sources, measurement and relaunch controls.
Sharply Labs’ growth and performance marketing practice is relevant for teams that need a compliance-first Meta account and campaign diagnosis and, when eligible, help operating the paid-acquisition program. For app businesses, our mobile app growth practice connects that work to acquisition, creative, store conversion, attribution and retention. The output of a focused review is an asset-scope diagnosis, evidence gaps, correction order, access map and campaign relaunch plan. It is not legal advice or a promise of restored access, approval, refund, account stability, lower CPA or media performance.
If that is the problem you need to solve, contact Sharply Labs for a compliance-first Meta Ads audit. Bring redacted notices, IDs and supporting evidence; do not send passwords, authentication codes, unnecessary personal data or complete payment credentials.