Meta will disapprove an ad and not tell you. This is the monitor we would build for that.

Status, before anything else

This product does not exist. There is no checkout, no trial, no beta, no private preview, and no code. What exists is a design that we are confident is buildable, and a decision not to build it yet.

The reason is specific rather than vague. To read ad data for the accounts a customer manages, a Meta app needs Advanced Access to the ads_read permission. Advanced Access requires Meta Business Verification and App Review. Both are multi-week queues on Meta’s side, both need a working app to submit, and neither has been started for this product. We are also not going to pretend the sequencing is only about Meta: Digital Empire Holdings has four products already shipped and zero paying customers across them. Opening a fifth build ahead of getting the first four in front of buyers would be the wrong call, and a page that implied otherwise would be selling you a schedule we have no intention of keeping.

So there is no date here. Not a quarter, not a month, not “early next year”. An earlier version of this page said January 2027. That date was made up, and it is gone rather than replaced with a better-sounding one.

What it would do

You connect the Meta ad accounts you run. The monitor watches them and emails you when one of these happens. Each item below is a documented field in the Meta Marketing API, not a projection of what we hope to infer.

• An ad gets disapproved. Ad.effective_status carries the values that matter here, including DISAPPROVED and WITH_ISSUES. The alert would carry Meta’s own itemized reason from Ad.ad_review_feedback, which breaks the rejection down per ad and per placement, plus anything in Ad.issues_info.
• An ad account gets restricted or disabled. AdAccount.account_status flips off active, and disable_reason gives the category Meta assigned.
• Delivery stops on billing. Meta reports this as the PENDING_BILLING_INFO status rather than as a policy problem, which is exactly why it is easy to miss: spend just stops.
• Delivery checks fail. failed_delivery_checks reports the checks Meta ran that an ad did not pass, before or during delivery.
• Meta itself flags a setup problem. The recommendations field returns issues Meta has surfaced against the account or the ad.
• A Page has not authorised the ad account. AdAccount.has_page_authorized_adaccount is a boolean, and when it is false it is a real cause of ads that never leave review.

The reason this is worth a product at all is timing. Ads Manager shows all of this to someone who is logged in and looking. It does not go and find the person who needs to know. If a client account gets restricted at 2am, the first signal most teams get is the spend graph the next afternoon, or the client asking first.

How it would work, and what it would not touch

Two mechanisms, both official, both documented, both server-side.

The first is the Meta Marketing API, read-only, on an access token you grant and can revoke at any time from your own Meta settings. The second is Meta’s Graph API webhooks. In July 2026 Meta shipped a webhook subscription on the ad_account object for the effective_status field, covering delivery blocks and policy rejections. That is what makes near-real-time alerting possible without hammering the API on a polling loop, and it is the backbone of the design.

There is no browser extension. There will not be one. An earlier version of this page described a Chrome extension that read the Meta UI as the product’s primary signal, and argued it was acceptable because it only read pages you already have access to view. That argument is wrong on its own terms: Meta’s Platform Terms prohibit automated collection from Meta surfaces regardless of whether the collection happens while logged in. Building on that would have put every customer’s account on the wrong side of Meta’s terms in order to sell them account safety, which is a genuinely stupid trade. Nothing is scraped, and no Meta session is read.

What it will not do

This list is as load-bearing as the one above, and it is here because the last version of this page promised several of these.

• No account quality score. Meta does not publish an account quality score, health score, or risk number to third-party tools. We are also not going to compute one of our own and let it be mistaken for Meta’s. You would get the status Meta set and the reason Meta gave, with a timestamp.
• No appeal tracking. It would not file appeals, track their state, or tell you when one resolves.
• No Page or Business Manager restriction monitoring. Those are a different surface from ad accounts, and this would not cover them.
• No pre-publish ad review. Judging your creative against Meta’s Advertising Standards before you publish is a separate product with separate risks, and it is not part of this one.
• No claim of 100% detection. It can report what Meta publishes through the API and webhooks, when Meta publishes it. If Meta does not expose a change, or exposes it late, neither would we.

Pricing

There is none, and we are not going to invent one. This page previously listed $99 a month for one account, $199 for up to ten, and $399 for up to fifty. Those numbers were priced against a fleet-wide account quality reader, and that capability does not exist to be sold. Rather than move the same numbers onto a different product, they have been withdrawn.

Pricing gets set when there is a working product to price, and it gets published at the same time as the checkout that can actually take the money. No Stripe SKU exists for this product, so nothing on this page can charge you, now or by accident.

Who it would be for

The person we have in mind is the paid-media lead at a small or mid-sized performance agency running somewhere between three and thirty client Meta ad accounts. At that scale the failure mode is not that the information is hidden, it is that nobody can be looking at thirty accounts at once. A restriction that goes unnoticed for a day is a lost week for the client and an escalation call for the agency.

The second case is the in-house operator at a brand spending five figures a month on Meta with no agency in the loop. One account, but an unexpected disapproval on the ad carrying most of the spend is a material revenue event, and nothing in Ads Manager goes looking for them to say so.

If that is you, the form is worth thirty seconds. If it is not, this page has nothing to sell you, which is the intended outcome.

Primary sources

• Meta Marketing API, Ad reference (effective_status, ad_review_feedback, issues_info) , The ad-level fields that carry disapproval state and Meta's own itemized rejection reasons.
• Meta Marketing API, AdAccount reference (account_status, disable_reason, has_page_authorized_adaccount) , Account-level status, the disablement reason enum, and Page authorisation state.
• Meta Marketing API, versioning and changelog , Documents the API surface across every published version, including fields added and removed in each.
• Meta Graph API webhooks reference , Webhook topics and fields, including the ad_account subscription that delivers status changes in real time.
• Meta app access levels, Standard Access and Advanced Access , Why this product is not available yet: reading another business's ad data needs Advanced Access, which needs App Review.
• Meta Business Verification , The verification step that gates Advanced Access. Not started for this product.
• Meta Platform Terms , Prohibits automated collection from Meta surfaces regardless of whether it happens while logged in. This is why there is no browser extension.

Frequently asked

• Can I buy Meta Ad Fleet Monitor today?

  No. Nothing is for sale on this page and there is no checkout behind it. The product is not built. The form is an interest signal and nothing more: it tells us whether to spend the weeks of Meta approval work this would take before any of it exists.

• When does it launch?

  We are not giving a date, because we do not have one, and any date we named would be invented. Reading ad data for accounts you manage through the Meta Marketing API requires Advanced Access to ads_read, which requires Meta Business Verification plus App Review. Both are multi-week processes on Meta's side and neither has been started for this product. We will not start them until enough people ask for this to justify the time.

• Does it use a Chrome extension?

  No, and it will not. An earlier version of this page said a browser extension reading the Meta UI was the product's primary signal, and defended that on the grounds that it only reads what you can already see. The defence does not hold: Meta's Platform Terms prohibit automated collection from Meta surfaces regardless of whether the collection happens while logged in. The design is server-side only, on the official Marketing API and Meta webhooks, using access you grant and can revoke.

• What would it actually detect?

  Ads Meta has disapproved or flagged, from effective_status, with Meta's own itemized rejection reasons from ad_review_feedback and issues_info. Ad accounts Meta has disabled or restricted, from account_status and disable_reason. Delivery blocked on billing, which appears as the PENDING_BILLING_INFO status. Ads failing Meta's pre-delivery checks, from failed_delivery_checks. Setup problems Meta itself flags through recommendations, and Pages that have not authorised the ad account, from has_page_authorized_adaccount. Every one of those is a documented field, not an inference.

• Will it show me my Account Quality score?

  No. Meta does not publish an account quality score, health score, or risk score to third-party tools, and we are not going to compute a number of our own and let it be mistaken for one. What you would get is the status Meta actually set and the reason Meta actually gave, with a timestamp.

• What will it not do?

  It will not track or file appeals. It will not monitor Page-level or Business-Manager-level restrictions, which are a different surface from ad accounts. It will not review an ad before you publish it. It will not give you an account quality score. And it cannot promise 100% detection: it can only report what Meta publishes through the API and webhooks, when Meta publishes it.

• What will it cost?

  We have not set pricing, and we are not publishing a number before the product exists. The previous version of this page listed $99, $199, and $399 per month. Those were priced against a fleet-wide account-quality reader that turned out not to be buildable, so they were withdrawn rather than re-labelled onto something else. Pricing gets set when there is a working product to price.

Tell us if you want this

This is an interest list, not a queue for something already coming. Leaving your email tells us whether to start the Meta verification and review work, and you will get one honest update when the answer changes, in either direction. If we decide not to build it, we will email you that too.