RecipeMeta Ads
Check Meta pixel and event health
Pixels, their recent activity and event volumes, read before any conversion-based judgement.
IntentWhether the pixel and its events still feed the account truth.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before optimisation changes.
- After site releases.
- When results moved implausibly.
Do not use it when
- As the full cross-system audit: that is tracking-audit.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
List pixels and their status on the account.
Read recent event volumes against expectations.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The optimised event's volume dropped while sessions held elsewhere
Conclude
Measurement suspect first: route to tracking-audit before touching campaigns.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- Browser-side losses (consent, ITP) are invisible here: pixel 'active' does not mean complete.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.