First identify what actually stopped. An ad rejection, an account restriction, a failed payment and a missing conversion event need different responses. A screenshot saying sales are down does not tell you which one occurred. The first hour should produce a clear incident record and an assigned next action, rather than a flurry of account changes.
Meta’s advertising restriction guidance describes restrictions on business portfolios, ad accounts, Pages and personal profiles, as well as limits on particular features. The notice on the affected asset is the starting point. A restriction is not always a complete shutdown, and its scope should not be guessed.
In this guide
Match the symptom to the next check
| What you see | Check first | Next action |
|---|---|---|
| One ad rejected | Ad ID, policy reason and destination | Review that ad and its landing page; edit or request review where available. |
| Account or business asset restricted | Exact asset ID and restriction notice | Open the asset in Business Support Home and follow its available actions. |
| Payment failed or billing disabled | Billing status and payment notice | Use the payment troubleshooting route rather than changing the creative. |
| Spend continues, reported purchases disappear | Store orders, events and reporting window | Investigate measurement and checkout before calling it an account ban. |
| Active status but little delivery | Review state, schedule, budget, limits and reporting freshness | Identify the delivery constraint before submitting a restriction appeal. |
Minutes 0–15: establish the facts
- Record when the issue was noticed, with timezone. Separate that from the last known delivery time.
- Capture the full restriction message, affected asset ID and any case reference. Keep the original wording.
- Check whether the issue affects one ad, one account, a Page, the business portfolio or a person’s access.
- Compare campaign delivery with store orders and checkout availability. State what is confirmed and what is still unknown.
- Assign one incident owner so several people do not submit conflicting changes or explanations.
If someone sends a supposed Meta warning, navigate to the business tools directly rather than signing in through an unfamiliar message link. If the account shows unexpected admins, payment changes or ads you did not create, treat that as a potential security incident and follow Meta’s account-security instructions.
Minutes 15–30: open the official recovery path
On a computer, open Meta Business Support Home. Select the restricted asset from the account overview and inspect “What you can do.” Depending on the case, Meta may ask for identity confirmation, business verification, security steps or a review request. An account admin is required to request a review. Follow the steps shown for your asset, not a screenshot from another advertiser’s case. Official troubleshooting instructions.
Complete the requested prerequisites before expecting a review button to become available. If no review option is shown, record the exact message and use any support route offered to that business. Do not assume every restriction has the same appeal options, an open review window or a fixed response time.
Minutes 30–60: prepare an evidence-based explanation
A useful review request is short enough to understand and specific enough to investigate. Identify the decision you are asking Meta to review. Explain the product, market and relevant policy. If something was wrong, describe the concrete correction. If you believe the decision was mistaken, connect that explanation to evidence rather than saying only that the account is important to your business.
- Affected asset and ad IDs, plus the original decision text.
- The relevant product and landing-page URL.
- Required licenses or authorizations, where applicable to that offer.
- The final creative version and an explanation of any corrections.
- A concise timeline and one contact responsible for follow-up.
Submit only documents the official process requests, through the official channel. Never provide personal login credentials to a stranger offering a guaranteed reinstatement. Avoid repeatedly submitting unchanged ads or moving the same unresolved violation to another account; that does not fix the cause and may conflict with Meta’s enforcement rules.
What to tell the rest of the business
Keep an operational update to four facts: affected campaigns, confirmed delivery impact, next action and next update time. If reporting is delayed, say so. “Orders attributed to this campaign are not updating” is more precise than “all sales are zero” when the store still has orders. Keep customer support, fulfillment and the marketing team working from the same evidence.
Prepare lawful continuity work while the case is open: resolve the landing-page issue, organize creative files, verify measurement and maintain consented customer communications. Any future campaign needs to be eligible in its own right. A replacement account is not permission to bypass an unresolved restriction.
After the decision: close the loop
Record the result and any remaining limitations. If access returns, verify campaign status, budget, schedule and tracking before assuming delivery has resumed. If the decision stands, document which activities remain unavailable. Give the team a clear rule for preventing the same issue, and update the relevant brief or access process.
For peptide offers, start that prevention work with product-category and policy review. When evaluating outside support, ask who owns the case, what information you receive and which commitments are written down. Our provider evaluation guide gives a practical scorecard. Adnoxx support should be assessed on that clarity and its actual service scope, not a promise to control Meta’s decision.