Meta Ads Manager frozen: 9 reasons your ads stopped delivering

Executive summary

When a Meta ad account goes cold overnight, the message inside Ads Manager is almost never the full story. Nine distinct failure modes present as a "not delivering" line item; only three of them are visible in the Business Manager notifications feed by default. This guide walks the diagnostic in the order that resolves the largest fraction of cases with the least clicking — status triage first, then policy, then billing, then account status, then pixel signal, then learning phase and audience size.

The August 26, 2026 Shopify checkout upgrade compounds the problem set for Shopify merchants specifically. Any store that ran a hard-coded Meta Pixel snippet on legacy checkout.liquid loses that snippet on the new checkout unless it was reinstalled through the Shopify Meta channel or the Conversions API. That is a pixel-signal-loss cause dressed as a "not delivering" symptom, and it looks nothing like a policy hold in Ads Manager.

The recovery order at the end of this guide is the practical sequence: unblock the fastest fix first (billing, minute-scale), then policy (hour-scale), then account (day-to-week scale), then pixel (day-scale plus platform integration work), then delivery optimization. Reversing that order is the most common mistake — rebuilding a campaign from scratch when the actual cause was a declined credit card wastes two days of learning-phase re-accumulation.

Status triage: what Ads Manager is actually telling you

Meta documents four delivery-status values in the Ads Manager delivery-status reference: Active (Delivering), In Review, Not Delivering, and Not Approved / Rejected. Only the first is a healthy state. Each of the other three has a hover-tooltip that gives the specific reason. Before doing anything else, read the tooltip on every non-delivering ad and copy the reason text into a scratch note. That reason text is the single most reliable pointer into the correct one of the nine failure modes below.

Common tooltip strings and what they map to:

• "Ad in review" — normal 24-hour policy re-review; not a failure unless it exceeds 24 hours.
• "Not Approved" / "Rejected" — policy decision. Section 1 below.
• "Account spending limit reached" — section 2.
• "Payment failed" — section 3.
• "Ad account disabled" — section 4.
• "Domain verification required" — section 5.
• "Pixel not receiving events" — section 6.
• "Learning limited" — section 7.
• "Audience too small" — section 8.
• "Below minimum bid" — section 9.

1. Policy hold on a specific creative or landing page

The single most common cause of an overnight delivery stop on an ad set that was healthy the day before is a re-review triggered by any edit to the creative, the primary text, the destination URL, or an image swap. Meta's Advertising Standards are enforced at both pre-publish and continuous re-review; a landing-page change on the Shopify store side can trigger the same re-review even without any change to the ad itself. If the domain now serves a product page with a restricted-category product, language, or before/after imagery, the entire ad set can be paused with no top-level notification.

Diagnostic steps for a suspected policy hold:

1. Open Ads Manager, filter Delivery = "Not Delivering", and hover the info icon on each affected ad.
2. If the tooltip mentions review status or the ad shows "In Review" past 24 hours, this is section 1.
3. Click the ad, open the "See details" panel, and read the policy category cited.
4. Compare the specific creative and landing page against the cited policy at the Advertising Standards library entry for that category.
5. If the citation is wrong, click "Request Review" and file the appeal via the Business Support Center. If the citation is correct, edit the ad or the landing page and re-submit.

Appeals go through the same Business Support Center thread system as account restrictions. Meta's published guidance is that most creative appeals resolve within 24 hours; complex cases involving personal-attributes, health, or financial-services policy categories may escalate to a human reviewer with a multi-day turn.

2. Account spending limit reached

The account spending limit is a soft cap advertisers set in Business Manager under Billing > Payment Settings; it is separate from the individual campaign budget. When the cumulative spend across all campaigns hits the limit, Meta halts delivery on every campaign in the account and displays the "Account spending limit reached" delivery reason. The account spending limit reference documents both the setting and the reset procedure.

Fix: raise or reset the limit at Business Manager > Billing > Payment Settings. Delivery resumes on Meta's next optimization cycle, which is typically under one hour but can extend to several. An account whose limit was hit and reset does not lose learning-phase progress; the pause was on the account not the campaign.

3. Payment method failure

Meta bills advertisers on a threshold-plus-monthly cycle, with the threshold increasing as an account establishes payment history. When an auto-charge attempt fails (expired card, insufficient funds, foreign-transaction block, 3D-Secure re-authentication required), delivery halts within hours and the account shows an "Action needed" banner at Business Manager > Billing > Payment Methods. The payment method troubleshooting reference walks through the retry procedure.

Diagnostic sequence:

1. Go to Business Manager > Billing > Payment Methods and check for red-banner warnings.
2. Confirm the primary card on file has valid expiration, correct billing address, and adequate limit.
3. Manually pay the outstanding balance via the "Pay now" button.
4. If the auto-charge still fails after payment, add a secondary payment method as fallback.

A payment failure resolves the fastest of any of the nine causes here — typically minutes from a successful manual payment to delivery resumption. Check billing first whenever the tooltip does not mention policy or review.

4. Ad account restriction or disablement

Account-level restrictions are stricter than ad-level policy holds. They halt every campaign on the account, appear as a red banner in Business Manager, and route the fix through the Business Support Center appeal system. Meta documents two categories in the ad account restrictions reference: temporary restrictions (usually 24 to 72 hours, resolves automatically) and disabled ad accounts (requires an appeal).

The appeal path:

1. Open Business Support Center via business.facebook.com/business/help/support.
2. Look for the "Account Quality" or "Ad Accounts" entry with a review status.
3. Follow the "Request Review" flow, keeping the appeal short and specific: cite the exact policy category cited, state the corrective action taken, and attach one screenshot proving the issue is resolved.
4. Save the case ID; the reply comes back in the same Business Support Center thread within Meta's observationally hours-to-weeks window.

For the full appeal walkthrough with sample templates, see our Meta ad account suspension appeal guide.

5. Business Manager domain-verification failure

Meta requires the destination domain of every ad be verified in Business Manager > Brand Safety > Domains before certain ad types will deliver, and mandatorily before setting event priority for the Aggregated Event Measurement (AEM) framework Meta rolled out after iOS 14.5. A verification that lapses (DNS TXT record removed, meta-tag file deleted on Shopify) can re-trigger a delivery halt on all campaigns pointing at that domain. Re-verify via one of three methods documented in the Meta help center: DNS TXT record, HTML file upload, or meta-tag verification.

6. Meta Pixel signal loss (Shopify checkout upgrade fallout)

Conversion-optimized campaigns depend on continuous purchase-event volume flowing back from the Meta Pixel. If the pixel stops firing (missing snippet after a theme update, server-side Conversions API misconfigured, browser blocking driving events to near-zero on a consent-heavy audience), the algorithm has no signal and delivery slows to a halt. The Meta Events Manager Diagnostics reference documents the alert states.

The August 26, 2026 Shopify checkout upgrade is the current highest-frequency cause of this specific failure. Stores that ran hard-coded Meta Pixel snippets in legacy checkout.liquid lose those snippets on the upgraded checkout. Purchase events drop to zero, campaigns throttle down over the following days, and Ads Manager displays a "pixel not receiving events" diagnostic in Events Manager while showing plain-old "not delivering" at the ad-set level. For the full pixel-recovery walkthrough see our Shopify Meta Pixel not tracking purchases guide.

Fix path:

1. Open Meta Events Manager > Data Sources > the pixel > Diagnostics tab.
2. Confirm which events are missing (Purchase, AddToCart, InitiateCheckout).
3. In Shopify Admin, install the Meta channel from Sales channels; ensure the pixel is connected under Facebook & Instagram sales channel > Settings > Data Sharing.
4. Enable server-side Conversions API per Meta's Conversions API documentation.
5. Wait 24 to 48 hours for a full event-volume recovery to feed the optimization algorithm.

7. Learning phase reset after edits

Meta documents the learning phase as the delivery-optimization stage during which the algorithm requires roughly 50 optimization events per ad set within a 7-day window to exit into stable delivery. Significant edits — budget change >20%, targeting change, creative swap, objective change — reset the learning phase and can visibly shrink delivery for days. This looks like a partial delivery halt without any error state; the delivery reason is "Learning limited" if the ad set cannot accumulate 50 events at the current budget within 7 days.

Recovery is not a fix so much as a discipline: batch edits, avoid budget swings above 20%, and let ad sets accumulate the event floor. Splitting ad sets to test creatives at low budget is often the wrong lever — the resulting per-ad-set event volume falls below the 50-event threshold and every branch stays learning-limited indefinitely.

8. Audience below minimum delivery size

Very narrow custom audiences or heavily-layered detailed targeting can fall below Meta's internal minimum-audience threshold for delivery. Ads Manager shows this as "audience too small" in the ad-set delivery summary. The remedy is to broaden the targeting; Meta's audience guidance recommends leaning on the algorithm's optimization by using broader targeting in the Advantage+ configurations.

9. Below the minimum-spend threshold for the objective

Certain objectives (Sales / Purchase optimization especially) have a de facto minimum-spend threshold below which the auction rarely wins impressions. If the daily budget was cut to $1 or $2 for testing, delivery can drop to zero without an error message. Raising the daily budget to at least $10 to $20 for a conversion-optimized ad set usually clears this state within one delivery cycle. This is not a policy or technical failure; it is an auction economics floor.

Recovery order — what to fix first

Ordered by speed to resolution and cost of the wrong sequence:

1. Billing (minutes) — check payment methods, resolve any "Action needed" banner.
2. Account spending limit (under one hour) — raise or reset if hit.
3. Policy holds (hours to 24) — read tooltip, either appeal or edit.
4. Domain verification (hours) — re-verify if the record was disturbed.
5. Account restrictions (24 hours to weeks) — file Business Support Center appeal.
6. Pixel signal loss (24 to 48 hours to full recovery) — Events Manager diagnostics, reinstall via Shopify Meta channel, enable Conversions API.
7. Learning phase and audience/budget economics (days) — only after signal and account health are confirmed.

Rebuilding the campaign from scratch is almost never the right first step. If the actual cause was a declined card or a lapsed domain verification, a rebuild spends two days of fresh learning-phase capital on a problem the original campaign did not have.

Preemptive monitoring so this does not recur

Four monitoring layers catch the nine failure modes above before a delivery halt shows in Ads Manager:

• Payment method expiration reminders — calendar the primary card expiration; add a fallback method by default.
• Business Manager notification hygiene — the notifications feed is under-used; assign at least one team member to monitor daily.
• Events Manager Diagnostics alerts — Meta will email on major event drops, but only if the alerting is enabled per pixel.
• Continuous pixel-and-checkout monitoring — the failure class where a Shopify theme update, checkout upgrade, or Meta API deprecation silently breaks tracking is exactly what PixelProof scans for.

Related reading: the 2026 comparison of Shopify pixel monitoring tools and the PixelProof methodology page.

FAQ

References and primary sources

1. Meta Business Help Center — Ad delivery status reference.
2. Meta Transparency Center — Advertising Standards library.
3. Meta Business Help Center — Account spending limit reference.
4. Meta Business Help Center — Payment method troubleshooting.
5. Meta Business Help Center — Ad account restrictions reference.
6. Meta Business Help Center — Domain verification reference.
7. Meta Business Help Center — Events Manager Diagnostics.
8. Meta for Developers — Conversions API documentation.
9. Meta Business Help Center — Learning phase reference.
10. Meta Business Support Center — Case appeal portal.
11. Shopify Help Center — Checkout upgrade reference.

Educational content, not endorsed by Meta. Meta, Facebook, Instagram, and Ads Manager are trademarks of Meta Platforms, Inc.; PixelProof is an independent monitoring tool.