RecipeTikTok Ads
Check TikTok pixel events before trusting results
Pixels and their events read for volume and recency, the TikTok leg of measurement trust.
IntentWhether the events the account optimises to actually fire.
- 2
- Steps
- 3
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before optimisation changes.
- After site releases.
Do not use it when
- As the full audit: tracking-audit crosses systems.
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 events.
Check volumes against site reality.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
The optimised event's volume is implausibly low
Conclude
Measurement first: the campaign optimises toward silence.
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.
- Event deduplication settings change counts without changing reality.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.