AdAce AdsIs your Meta pixel working? Last event, volumes and silence alerts
A broken pixel silently ruins Meta optimization. The pixel health card and monitor catch it the same day.
What it does
With every structure collection the service reads the account's pixels — name, last fired time, availability — and hourly event statistics for 7 days, including server events from the Conversions API. The card shows the state, which ad sets and campaigns optimize on the pixel, and event volumes.
The “Meta pixel health” monitor is critical: it fires when a pixel used by active ad sets with recent spend is unavailable, silent for longer than the set hours (24 by default) or when the optimization or KPI event drops to zero after a normal level of at least 5 per day.
Why it helps
- Catch tracking breakage before budgets are wasted.
- Know which campaigns depend on which pixel.
- Server-side events are included in volumes.
How to set it up
- Open Analytics for a Meta account and find the “Pixel status” card.
- Review state, last event and volumes.
- Create a monitor from the “Meta pixel health” template in Agents to get alerts.
Good to know
- Detailed event statistics depend on the app's access level; without it you still see last event time and availability.
- The signal uses the latest collection and is skipped if data is stale.
Try it on your own accounts
Create a workspace, connect Google or Meta in a couple of clicks and see your accounts clearly. Changes follow your approvals or the policy you configure.
Create your workspace