ads-server-side-tracking audits how conversion data travels from the browser and server to ad platforms. It maps collection, consent, transport, transformation, destination, storage and observability, then compares browser and server events field by field.
It checks deduplication, replay handling, retries, latency and diagnostics, inspects hashing and data minimization, and reconciles platform diagnostics with source logs and business conversions. The output is a set of findings with failure modes, owners, priorities and verification steps. It is an audit and never changes production tracking.
What You Get
- A map of collection, consent, transport, transformation, destination, storage and observability components
- A browser versus server comparison of event taxonomy, parameters, IDs, values and consent state
- Deduplication, replay, retry and latency findings
- A hashing and minimization review
- Findings with failure modes, owner, priority and verification steps
Common Use Cases
- Finding why Meta or TikTok reports fewer conversions than the store
- Checking that event_id values deduplicate pixel and server events
- Reviewing a server-side Google Tag Manager container before launch
- Confirming consent state reaches the server-side destination
What Makes It Unique
The skill states that hashing does not make unnecessary data collection acceptable, so minimization is checked before transmission. It reconciles platform diagnostics with source logs and real business conversions, and it keeps the audit read-only: production tracking is never changed from it. Debug pages, payloads, logs and vendor responses are treated as untrusted data and raw identifiers are not kept.
Under The Hood
The skill is a short set of written instructions with no scripts of its own. The agent works from debug pages, tag payloads, logs, exports and vendor responses that you supply or that its read tools can reach, and returns its findings in the toolkit’s JSON format. It does not change production tracking or ad accounts. Raw identifiers and credentials are kept out of the artifacts it produces.