Meta Ads Manager won’t alert you when an active ad gets restricted. Meta Ad Fleet Monitor does.

What Meta actually exposes to third-party tools

Every SaaS vendor that says it “monitors your Meta account health” is doing so on top of a very specific, and very limited, public API surface. Meta Ad Fleet Monitor took the inversion of this reality seriously enough during the August 2026 planning cycle to re-architect the product before writing code. Here is exactly what the Meta Marketing API AdAccount reference publishes for compliance signals: two fields. account_status is an integer enum that flips from 1 (active) to 2 or 3 when Meta disables or restricts the account. disable_reason is a companion enum that gives a coarse category (policy violation, unsettled balance, and so on) for the disablement.

That is the entire compliance-adjacent Marketing API surface. There is no account_health_score field. There is no /policy_violations endpoint. There is no way, through any documented public API, to programmatically read the traffic-light “Account Quality” status Meta shows a logged-in human at business.facebook.com/accountquality, or the itemized ad-level restrictions Meta displays alongside it. This is verified against the Meta Marketing API v25.0 changelog and every prior public version in the changelog.

Any product that claims to give you “Meta’s Health Score” is either relabeling something else, a proprietary performance metric that is not compliance- relevant, or an aggregated risk model the vendor computes themselves, or it is overpromising. Meta Ad Fleet Monitor, deliberately, does not make that claim. What Meta Ad Fleet Monitor publishes is an Meta Ad Fleet Monitor Risk Score: a score computed by Meta Ad Fleet Monitor, from Meta Ad Fleet Monitor- collected signals, that Meta Ad Fleet Monitor stands behind. That distinction matters to procurement at the agency and enterprise level, and it matters even more the day Meta changes its private scoring model and every vendor claiming to expose “Meta’s score” has to explain why their number is wrong.

Why the Chrome extension is the primary signal

The most useful compliance information on a Meta ad account, the traffic-light Account Quality status, the itemized list of restricted ads and their reason codes, the pending appeals, only exists inside the Meta UI. A logged-in human can see it; a server-to-server Marketing API call cannot. That leaves exactly two options for a monitoring product: (1) hire a human to log into every client account every morning, or (2) run a browser extension inside the browser profile the operator is already using, and read the same DOM the operator already has access to view.

Meta Ad Fleet Monitor does option two. The Chrome extension attaches to the Account Quality page, reads the traffic-light color and reason codes for every ad account the logged-in Meta user already has access to, and pushes those signals into Meta Ad Fleet Monitor’s fleet dashboard. If a client agency has thirty Meta accounts and the paid-media lead opens Ads Manager once per morning, Meta Ad Fleet Monitor has already captured that morning’s Account Quality snapshot across all thirty and can flag any account whose status changed overnight, without waiting for a human to page-by-page audit.

The extension does not read anything a Meta user account without that access could not already see. It does not proxy through Meta Ad Fleet Monitor’s own Meta app for Account Quality, the Marketing API app is the secondary signal, used for the account_status / disable_reason fields that a server-to-server call is genuinely capable of reading. Both signals together are the product; the Chrome extension is the primary one because it captures the strictly richer signal Meta only publishes through the UI.

Pre-flight ad review before Publish

The Chrome extension’s second job is a pre-flight compliance scan on any new ad you are about to publish. The scan runs against Meta’s published Advertising Standards , restricted-category signals, banned-content patterns, disallowed claim structures for regulated verticals like financial services, health, alcohol, employment, housing, and credit, and returns a risk assessment before you hit Publish, not after Meta reviews it.

The pre-flight scan does not use an LLM to judge ad content. Every rule is deterministic and inspectable. When Meta Ad Fleet Monitor flags an ad, the operator sees exactly which rule fired and why, and can override, edit, or ship as-is with the decision on the record. That deterministic approach is a deliberate choice: agencies running paid media at scale need the flag reasoning to be auditable and defensible, not the output of a probabilistic model that might reason differently tomorrow than it did today. If Meta’s standards change, as they do, roughly quarterly for major categories, the deterministic rule file changes with them, and every past decision remains reproducible against the exact rule set that was in effect on that date.

Who Meta Ad Fleet Monitor is designed for

The primary buyer is the paid-media lead at a small-to-mid performance-marketing agency managing three to thirty client Meta ad accounts, plus their own agency account. At that scale, an account restriction on a client’s ad account that goes unnoticed for even a few hours can translate into a losing week for the client and an escalation call for the agency. Manual daily audits do not scale; the paid-media lead does not have time to log into thirty client accounts every morning.

The secondary buyer is the paid-media operator at a direct-to-consumer brand spending $10,000 or more per month on Meta ads, running the account themselves without an agency in the loop. At that spend level, an unexpected restriction is a material revenue event. A fleet monitor is overkill for one account, but the pre-flight scan and single-account tier give operators the same before-and-after-Publish protection an agency’s paid-media lead would use, at a price that reflects the single-account scope.

Planned pricing at launch

Planned pricing at January 2027 launch is $99/mo for a single account, $199/mo for an agency tier that covers up to ten Meta ad accounts, and $399/mo for the scale tier covering up to fifty accounts, with an additional $12/mo per additional account beyond tier caps (billed via a Stripe usage meter, so agencies that add or drop client accounts mid-cycle are not double-charged). All plans include the pre-flight ad review, all include the Chrome extension, all include monthly cancellation, and all offer a 25% annual discount.

No Stripe SKU exists today. The pricing numbers on this page are prose-only, deliberately not embedded in this page’s product schema, so search engines cannot index a Product/Offer that no Stripe checkout can actually fulfill until launch. Waitlist members lock launch-week pricing when checkout opens.

Why we’re building Meta Ad Fleet Monitor

Meta Ad Fleet Monitor is the third product in a compliance-monitoring line Digital Empire Holdings LLC is shipping across the 2026-2027 window. The first, PixelProof, monitors Shopify Meta pixel and tracking-tag health. The second, PriceProof, monitors Shopify strikethrough pricing for FTC and state reference-pricing compliance. Meta Ad Fleet Monitor extends the same “continuous monitoring plus paste-ready fixes” pattern to the Meta-ad side of the same operator’s stack, the paid-media compliance surface a PixelProof or PriceProof customer likely already owns internally at a small ecommerce brand, or manages on behalf of clients at an agency.

We are shipping this pre-launch page five months before the target launch date because the sequencing forces it. Meta Developer app registration plus Business Verification take up to eight weeks on Meta’s side, with a long-tail of documented cases running two months or more. To be shippable in early 2027, those submissions have to be in front of Meta by early November 2026, and before Andy commits that review-window time, we want a concrete waitlist count telling us how many agencies would meaningfully use the tool. If nobody signs up, we will not push the button on Meta app registration and we will say so publicly instead of shipping a solution nobody asked for.

Primary sources

• Meta Marketing API, AdAccount reference (account_status, disable_reason fields) , Public reference for the only two real compliance-adjacent fields on the AdAccount object.
• Meta Marketing API, versioning and changelog , Documents the API surface across every published version. No account_health_score field, no /policy_violations endpoint.
• Meta Marketing API, Get Started guide , Confirms the App Review and Business Verification path required to ship a production Marketing API app.
• FTC endorsement, testimonial, and deceptive-advertising guidance , US baseline for ad claims that Meta advertisers, in addition to Meta policy, remain responsible for under Section 5.

Frequently asked

• Is Meta Ad Fleet Monitor live today?

  No. Meta Ad Fleet Monitor is targeting a January 2027 launch after PriceProof (its sibling product) clears its M4 revenue gate. This page is a pre-launch waitlist so agency and DTC brand ops teams get first access, launch-week pricing, and a direct signup link when it opens. Meta Developer app registration + Business Verification take up to 8 weeks on Meta's side, so Andy is submitting those in November 2026 to be ready, a waitlist signup is how we know how many agencies to prioritize for the initial cohort.

• Why can't you just use Meta's Ad Health Score API?

  There is no Ad Health Score API. Meta Graph API v25.0 exposes exactly two compliance-adjacent fields on the AdAccount object, `account_status` and `disable_reason`, and neither one gives you the same traffic-light detail the Account Quality page shows a human logged into business.facebook.com. Meta Ad Fleet Monitor uses the Marketing API for those two fields plus a Chrome extension that reads the Account Quality DOM on pages you already have access to view, so a fleet of 30 client accounts can be monitored without a human logging into each one every morning.

• Why does Meta Ad Fleet Monitor require a Chrome extension?

  The most useful compliance signal, the human-facing Account Quality status with its reason codes, only exists in the Meta UI. There is no server-to-server API that returns that same signal. A Chrome extension is the only way to read it, and it can only read what a Meta user account you already own has access to see. That's why the pre-flight scan and fleet-monitor features are packaged together into one extension per browser profile rather than sold as a pure SaaS.

• What is "pre-flight ad review"?

  Before you hit Publish on a new ad in Ads Manager, the Meta Ad Fleet Monitor extension runs a deterministic scan against your ad creative and copy (banned words, banned-image patterns, restricted-category signals). It returns a risk assessment based on Meta's published Advertising Standards. It does NOT use an LLM to evaluate ad content, every rule is deterministic and inspectable, so an agency knows exactly why an ad was flagged and can override or fix without waiting on a probabilistic model.

• How does the "Meta Ad Fleet Monitor Risk Score" work?

  Meta Ad Fleet Monitor combines Marketing API signals (account_status, disable_reason) with Chrome extension signals (Account Quality traffic-light color + reason codes) and historical restriction events into a single risk score computed by Meta Ad Fleet Monitor, from 0 to 100. It is our score, based on your data, it is explicitly not Meta's internal score, because Meta does not expose one to third parties.

• When will paid plans open?

  The Aug 2 2026 spec locks planned pricing at $99/mo starter (1 account), $199/mo agency (up to 10), and $399/mo scale (up to 50), plus a $12/mo Stripe Meter for accounts beyond a tier's cap. All planned pricing carries a 25% annual discount. No Stripe SKU exists yet, so no one can accidentally get charged from this page. Waitlist members get launch-week pricing locked when checkout opens.

• What happens if Meta terminates Meta Ad Fleet Monitor's API access?

  The v1.1 spec locks a hard-kill trigger: if Meta terminates Meta Ad Fleet Monitor's Marketing API access, the product shuts down immediately with no reassess window. Every waitlist member and paying customer would be refunded and notified. The Chrome extension leg would keep working (it uses your own Meta session, not Meta Ad Fleet Monitor's app) but the product would not be sold as a going concern without both legs. That risk is why the pricing model is designed around clear, monthly cancellation, no long-term commitments hedge the Meta-app risk.

Ready when we are

Meta Ad Fleet Monitor waitlist locks launch-week pricing and gets you the direct signup link when paid access opens. One email, no drip in between.