# Check Meta pixel and event health

> Tier: recipe. Operating recipe: real tool sequence, core rules, known traps.

Pixels, their recent activity and event volumes, read before any conversion-based judgement.

**Intent.** Whether the pixel and its events still feed the account truth.

## When to use

- Before optimisation changes.
- After site releases.
- When results moved implausibly.

## When not to use

- As the full cross-system audit: that is tracking-audit.

## Sources

Required: Meta Ads

## Preconditions

- The account is ticked in the dashboard, confirmed via list_accounts.

## Inputs

- `window`: Analysis window. Default: last 30 days.

## Procedure

1. List pixels and their status on the account. — tools: `meta_get_pixels`
2. Read recent event volumes against expectations. — tools: `meta_get_insights`

## Decision rules

- **When** The optimised event's volume dropped while sessions held elsewhere → **conclude** Measurement suspect first: route to tracking-audit before touching campaigns.

## Evidence requirements

- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.

## Human approval boundary

- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.

## Failure modes

- Browser-side losses (consent, ITP) are invisible here: pixel 'active' does not mean complete.

## Output

- **Readout**: The figures, with windows and accounts named.
- **Flags**: What deserves a deeper skill or a human decision.

## Related

- Skill: [tracking-audit](https://www.getmcpads.com/skills/tracking-audit.md)