Recipe
Audit measurement presence on every ad platform
Pixels and conversion wiring checked platform by platform, the measurement half of onboarding.
IntentWhich platforms have working event wiring, in one table.
- 2
- Steps
- 4
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Onboarding.
- Quarterly measurement hygiene.
Do not use it when
- As the deep audit: tracking-audit crosses against GA4 and quantifies gaps.
What it needs first
No single source is required: this one reads across whatever you have connected.
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.
Check pixels and conversion setups everywhere.
Table: platform, wiring present, last activity, optimised events.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
A platform spends without its own wiring
Conclude
It optimises blind: highest-priority measurement finding.
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.
- Present is not correct: presence auditing finds absences, tracking-audit finds lies.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.