What this Skill helps with

Server-Side Tracking Auditor reviews supplied evidence for server-side GTM, Meta Conversions API, client and server event flow, deduplication, event parameters, match quality, consent, hashing, and hit ratios.

Who this Skill is for

It is intended for analytics engineers, paid-media teams, agencies, developers, and privacy owners reviewing whether server-side conversion events are complete, consistent, and handled appropriately.

What you provide

  • Server-side stack inventory and container or gateway configuration
  • Event taxonomy and required parameters
  • Client and server test-event evidence
  • Event IDs, timestamps, names, values, and currency examples
  • Meta Event Match Quality and diagnostic screenshots
  • Client-to-server hit counts, consent behavior, and hashing method
  • GA4, Google Ads, Meta, or other destination mappings

What it produces

  • PASS, WARNING, or FAIL review by tracking surface
  • Client and server event-flow map
  • Deduplication and event-ID checks
  • Parameter, hashing, consent, and PII-handling observations
  • Hit-ratio and match-quality review
  • Ranked engineering and verification checklist

How the Skill works

The workflow compares matching client and server events, checks naming and parameter consistency, and looks for duplicate, missing, late, or improperly handled events. It distinguishes evidence from configuration claims and records where a live test is still required.

Installation and first use

  1. Download and add the Skill to Claude.
  2. Provide the stack inventory, event taxonomy, and destination list.
  3. Attach matching browser and server test-event evidence.
  4. Add consent, hashing, deduplication, and hit-ratio details.
  5. Have analytics, engineering, and privacy owners verify changes in a controlled environment.

Example workflow and expected output

Provide Pixel and Meta CAPI evidence for Purchase and Lead events, including event IDs, timestamps, parameters, match quality, and hit counts. Ask for a flow map, deduplication review, missing parameters, privacy cautions, and a retest checklist.

Limits and review guidance

The Skill cannot prove live firing from configuration text alone. Browser tools, platform test-event panels, server logs, consent tests, and destination reports remain necessary. Privacy and data-use requirements should be reviewed by qualified owners for the relevant markets.

Frequently asked questions

Does it test events directly?

No. Supply test-event output, logs, screenshots, or exports for analysis.

Can it check event deduplication?

Yes. Include matching client and server event IDs, names, timestamps, and platform diagnostics.

Does hashed customer data remove privacy obligations?

No. Hashing does not replace consent, lawful collection, minimization, access control, or policy review.