The day Meta restricts your account: what happens in the first hour

Every advertiser in this category eventually gets the notification. What separates a bad morning from a lost week is not whether it arrives but what is already in place when it does. This is the first hour as it actually runs: how the restriction is noticed, what the appeal realistically looks like, what the transfer desk moves to the spare and what it cannot, and what you see in your panel while it happens.

Three different events that all get called “restricted”

Meta can object at three levels, and the response to each is different. Treating them as one thing is how people over-react to a rejection and under-react to a restriction.

An ad is rejected

The narrowest event. One ad fails review, at submission or after it has run, and stops delivering; the rest of the ad set, the campaign and the account continue. Meta attaches a policy reason, and in this category the common ones concern how the product is described and what the landing page claims. This is the one event you can resolve yourself, by changing the creative or the page it links to. It is also sometimes the first step toward the next one, so repeated rejections are a warning, not noise.

The ad account is restricted

The account itself is disabled from advertising. Every campaign in it stops at once, regardless of which ad triggered the review. Meta attaches a reason, a policy category or a statement that the account did not pass a review of its advertising activity, and offers a review request. You cannot resolve this by editing an ad. This is the event the spare account exists for.

A payment is held

The account stops spending for a different reason: Meta could not collect against the payment method, or has placed the account under a billing hold. Nothing about your ads is in question. Because the payment method Meta bills is ours and not yours, this is handled on our side without you touching a card. From the outside it looks identical to a policy stop, which is why we read the reason Meta gives rather than inferring it from stopped spend.

Minute zero: how the restriction is noticed

Nobody logs into the account, so nobody sees a red banner in Ads Manager. The account’s status and the review verdict on every ad are read through Meta’s Marketing API with the same system-user token that reads your spend. When Meta changes a status, the next read picks it up and the panel changes with it. That is what starts the clock: not someone on our side happening to notice, and not you writing to support. With shared logins, a restriction is discovered when someone tries to log in; reading it through the API is quieter and earlier.

The first hour: two tracks run at the same time

Once the status changes, two things start in parallel, and neither waits for the other.

The appeal

Our team files the review request with Meta: what the account was doing, what the ads were, and where the objection is wrong, or what was changed if it is not. Here is the honest timeline: there is no fixed clock. Some review requests come back within hours with an automated answer. Some go to a human reviewer and take days. Some are declined, and a declined review on a disabled account is often final. We file every one, and we do not pretend to know in advance which kind it will be. That uncertainty is why the second track exists.

The transfer desk

While the appeal sits in Meta’s queue, the transfer desk rebuilds your campaign on the spare. The spare was allocated to your brand before you needed it: warmed, with billing attached and the pixel already shared to it, so there is nothing to apply for and nothing to wait on. The campaign definition lives in our system as data, because that is how it was created; the rebuild is not a reconstruction from memory. The goal is delivery the same day. It is not a promise that the appeal will succeed.

What moves to the spare

Everything that belongs to the brand carries over; the only thing that changes is the account.

• The verified domain — already verified in your brand’s Business Manager, so ads on the spare link to your storefront with nothing to redo
• The pixel and the Conversions API — they do not move; the spare spends against the same pixel, so event history keeps accruing in one place and nothing on your site changes
• Creatives, copy, targeting, placements, schedules and budgets — rebuilt from our records, not re-uploaded by you
• Audiences — defined against the pixel, so the same custom audiences are built again on the spare and lookalikes derived from them
• Your remaining wallet balance — never tied to the account, it moves across with the campaign

You do not re-install, re-verify or send us files. If nothing about the offer has changed, the rebuilt campaign is the same campaign with a different account ID under it.

What stays behind

Two things do not carry over, and it is better to know them on a normal day than to discover them on this one.

The first is the account’s own history: its ID, its delivery record, and whatever Meta’s delivery system had learned about your audience on that specific account. Ad sets on the spare start a fresh learning phase, so the first days after a transfer look like the first days of any new account, even though nothing about your tracking, audiences or offer has changed. Expect it; the first two days on the spare are not a verdict on the product.

The second is the reason Meta gave. It does not vanish because the account changed. We show you which ad was objected to and what the objection was, in plain words, and we address it in the appeal. But if the same creative goes live unchanged on the spare, the spare is being handed the same review. The transfer desk moves the campaign; whether an objected ad runs again unchanged is decided together before it does.

What you see in the panel that day

You are not asked to be online for any of this. When you open the panel, this is what is there:

• The restricted account shown as restricted, with a note from us on what happened and what is being done
• If an ad was rejected, the ad is named and the objection shown in your own language, next to what to change
• The rebuilt campaign under the spare account, same name, creatives and budgets, its spend and results reading live from Meta as soon as delivery begins
• Your wallet balance unchanged apart from what was spent; nothing is lost in the move

And you can verify it without a login. Once the rebuilt campaign is delivering, its ads appear in Meta’s public Ad Library under your Page, and pixel events keep arriving on your own site, because the pixel never moved.

Continuity, not a guarantee

It would be easy to end with a promise. We do not, because the only honest promises in this category are structural. Meta reviews peptide and research-compound advertising closely. We do not promise an ad will be approved, we do not promise an account will never be restricted, and we do not run ads that break Meta’s rules on prescription or unapproved drugs. What we promise is what this post describes: the restriction is noticed by the system rather than by luck, the appeal is filed by a person, the spare is already there, and the campaign is delivering again the same day with its domain, pixel, creatives, audiences and balance intact.

A restriction is an event in the account’s life. It should not become an event in the brand’s.

On a normal day, the useful part of this post is the list of what stays behind. Make sure the campaign you would hate to lose can be rebuilt: creative on file, audiences defined against a pixel that keeps accruing whichever account spends, a domain verified in a container that belongs to the brand alone. That is the whole of the preparation, and it is the difference between the first hour and the first week.