You logged in this morning and Shopify has your store under review, or your payouts are held, or the admin URL just returns a notice you cannot click past. Your campaigns are still delivering, still spending, still pointing at a URL that can no longer take money. This piece covers the half of that emergency nobody writes down: what actually happens to your ad account, your pixel, your domain verification and your live campaigns when the store underneath them goes dark, and the order to deal with it in.
Your store and your ad account are 2 separate failure points
Shopify and Meta do not share an enforcement system. A trust and safety decision on the store side does not fire a signal into Meta that disables your ad account. Operators assume it does because both things go wrong on the same morning, but the shared cause is almost always your own offer, not a pipe between the 2 companies.
What actually connects them is 4 things, and each one is repairable at a different speed: the destination URL your ads point at, the pixel that fires on the storefront, the domain verification that gives you control over link edits and event configuration, and the card that pays for the ads. A store suspension breaks all 4 at once, which is why something that starts as a payments problem is an advertising problem before you have finished reading the notice.
Work out which of the 3 states you are actually in
These 3 states get called the same thing in forum threads and they are not the same thing at all. Read the notice for the word it uses, not the tone. Reviews and restrictions are reversible states with a document request attached, and that request usually arrives by email rather than in the admin, which is how people miss the deadline. Termination is a decision, and the escalation path from there is slow enough that you should plan the next 2 weeks of revenue around it not coming back.
Whichever of the 3 you are in, the media side runs on its own clock and it does not wait for the appeal. Every hour your ads keep pointing at a dead destination is an hour of spend with no chance of a conversion, plus a review risk you are creating for yourself. The state you are in changes the spend decision, not whether you have to make one today.
- Under review. The storefront is still up and checkout is normally still taking orders while the review runs, so nothing in Ads Manager looks wrong. The exposure is that you are buying into a store that can lose checkout mid flight, and the notice rarely tells you when the decision lands.
- Payments restricted. Shopify Payments is switched off, the storefront still loads, and every click you buy lands on a page that cannot complete a sale. This is the most expensive of the 3, because nothing looks broken from inside Ads Manager and the spend keeps clearing normally.
- Terminated. Admin access is revoked, the storefront serves a notice instead of a product page, and your data, your theme and often your domain sit behind a login you no longer have.
What breaks and what survives
Sort your assets into gone, frozen and untouched before you touch anything. Most operators get this wrong in the same direction: they panic about the pixel, which is fine, and ignore the domain, which is not.
- The ad account survives. It is a Business Manager asset and Shopify has no ability to reach it. Your history, your spend limit and your payment method are all intact, and it is the fastest thing on this list to repoint.
- The pixel survives but goes quiet. Event history stays where it is and the pixel ID keeps working. It just has no page left to fire on, and the server side feed goes with it, because the Conversions API events were being sent by the Shopify app that is now offline. Signal stops in both channels at the same hour.
- Custom audiences drain on a timer. A 30 day purchaser audience is empty 30 days after the last Purchase event. Nothing deletes it, it just runs out, and that gap cannot be backfilled once it has passed. The same clock is running on every retargeting pool and every lookalike built off one.
- The catalog goes stale. A Shopify connected feed stops syncing at the last successful pull, so catalog and Advantage+ shopping ads keep serving products at stock levels and prices that are no longer real, to a URL that no longer resolves.
- Domain verification is the dangerous one. It lives in your business settings rather than on Shopify, but whether it survives depends entirely on how you verified it in the first place.
- The card is the quiet one. If the ad account is funded by a card drawing on the account Shopify has just frozen, your ads stop for a billing reason days before anyone works out why.
Your ads start getting rejected before anyone notices the store is down
Meta re-checks destinations. Ads that passed review a month ago get crawled again, and a URL that now serves a password wall, a 404 or a store unavailable notice reads as an unavailable landing page. Rejections arrive on ads you have not touched in weeks, which is why the first symptom often looks like a delivery bug rather than a store problem.
Once is survivable. Leaving it running is not. A stack of rejections on the same account over a few days is the pattern that turns a delivery issue into an account level review, and then you are fighting on 2 fronts with the same cash. If the store is dark and you cannot repoint today, pause the ads yourself instead of letting the review system do it for you. The triage for an asset that gets pulled out from under a live campaign is the same shape on the account side.
The first 3 hours, ordered by what is costing you fastest
Do these in order. The order matters more than the speed, because 2 of them stop being possible the moment admin access is revoked, and nothing you do afterwards gets them back.
- Stop delivery to the dead URL. Pause at ad set level, not campaign level, so the structure and the learnings stay in place while you decide where the traffic goes.
- Export everything while you can still see it. Ads Manager reports, audience definitions, the pixel ID, your domain verification record, your catalog feed URL. If any of it lives inside a business you do not administer, you are already too late to collect it.
- Decide repoint or hold. Editing an ad's destination is a significant edit and can push the ad set back into the learning phase. If you have a working URL today, take the reset. If your standby destination is 4 days out, holding costs you less than 2 resets on the same ad set.
- Move the ad account off the frozen card. Do it before the next billing threshold hits, not after the decline. A failed payment stops delivery on its own and, left alone, becomes a restriction of its own.
- Ask support for the customer export. Once admin access is revoked, a ticket is the only route to your customer list, and the queue gets longer every day you wait. That list is the only asset in this whole stack that outlives the platform it was collected on.
Domain verification is what you cannot rebuild in a hurry
Domain verification sits in your business settings under brand safety, and Meta lets exactly 1 business hold a domain at a time. Whoever holds it configures the conversion events allowed on that domain and controls link edits for it, so it is not a formality you can leave parked with somebody else. That single holder rule is also what produces the error people paste into search verbatim: domain already verified by another business. It shows up in 2 situations, and only 1 of them is fixable by you alone.
If you verified with a DNS TXT record at a registrar you control, the verification survives a store freeze untouched, because the record has nothing to do with Shopify. If you verified with a meta tag in the theme or an HTML file on the storefront, the proof lives on a site that is now offline, and re-verification fails until you have a live site again. That is the whole argument for verifying by DNS on day 1, and it costs nothing to do it that way.
If the domain itself was registered through Shopify it is worse. The transfer out is started from an admin you have just lost access to, and support will normally want the account back in good standing and the balance cleared before anyone moves it. A domain registered in the last 60 days also sits under the ICANN transfer lock, which no registrar can waive on request.
The other version is the partner version. If an agency verified your domain inside their business, the release has to come from them, and a relationship that has just ended badly is not a fast release. Working through how the pixel and domain verification actually sit together is worth doing before you hand either one to anybody.
The questions to ask before you rent a standby account
Standby infrastructure is the piece of this you cannot buy quickly. A backup processor can be approved in days. A domain can be moved once the lock clears. An ad account with real spend history behind it cannot be produced on the Tuesday you need it, which is why this decision gets made badly under pressure. If you are shopping for one now, these are the questions, each with the answer that should end the conversation.
- Who owns the Business Manager the account sits in? If the answer is theirs and you get user access, every asset you build inside it is theirs on the day the relationship ends. The trade off between an agency account and your own business comes down to exactly that.
- Where will domain verification live? If they want your domain verified inside their business, you are rebuilding the exact single point of failure you are trying to insure against, and you are handing over your event configuration with it.
- Whose pixel gets used? A pixel can only be shared out by the business that owns it. If that business becomes unreachable, so does the pixel, and event history cannot be moved into a new one.
- What is the fee, and what is it a percentage of? A cut of ad spend means your cost of running ads climbs precisely when volume climbs, which is the wrong direction, and it climbs hardest in the month you are trying to rebuild.
- What happens to the balance on the account if it gets banned? Get that answer in writing before money moves. A prefunded balance held by somebody else is the part of this market with the worst public record, and the tiers where you put your own card on the account do not have this problem at all.
- How fast is a replacement, and what does the transfer actually involve? Read how the handover is supposed to work before you compare 2 providers on monthly price alone.
The honest version of what any of this changes
None of it makes an ad account safe. Accounts at every tier of trust get restricted, and a provider telling you otherwise is selling a story rather than infrastructure. Standby capacity is also a cost you carry in every month where nothing goes wrong, which in a good year is all 12 of them.
What it changes is the shape of the outage. If the store, the pixel, the domain and the ad account all sit inside 1 business somebody else administers, a single decision takes all 4 down together and you rebuild from zero. If the ad side is separate, funded on its own card, verified on DNS you control and priced as a flat monthly line instead of a share of spend, a store outage stays a store outage. You repoint traffic to a standby destination the same day and you keep the account, the history and the audiences that cost months of spend to build.
If the failure runs the other way and it is the ad account rather than the store that goes down, the recovery sequence for a disabled ad account is the same runbook pointed in the opposite direction.