# Check TikTok pixel events before trusting results

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

Pixels and their events read for volume and recency, the TikTok leg of measurement trust.

**Intent.** Whether the events the account optimises to actually fire.

## When to use

- Before optimisation changes.
- After site releases.

## When not to use

- As the full audit: tracking-audit crosses systems.

## Sources

Required: TikTok 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 events. — tools: `tiktok_get_pixels`, `tiktok_get_events`
2. Check volumes against site reality. — tools: `tiktok_get_insights`

## Decision rules

- **When** The optimised event's volume is implausibly low → **conclude** Measurement first: the campaign optimises toward silence.

## 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

- Event deduplication settings change counts without changing reality.

## 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)