Module 01
Server Container Hygiene
28
Tags, clients, triggers, custom templates and approval state on the server container.
TagsClientsTemplatesApprovals
SERVER-SIDE TAGGING VALIDATION
Audit your server container from request to destination.
86 checks across 3 modules — catches the gaps between client events fired and conversions actually delivered.
ssgtmaudits.com · live audit
▲Client / server event count mismatch (-12%)4s ago
✗Meta CAPI missing event_id on 18% of events11s ago
▲First-party cookie domain mismatch on /checkout18s ago
✗GA4 server tag missing user_id when signed in25s ago
86
validation checks
3
audit modules
GA4 + CAPI + Ads
destinations
how it works
Three layers of evidence.
Configuration alone lies — what's there isn't always what fires. We pair the source of truth with live execution data and version history, so every finding has receipts.
L1 · CONTAINER
Read the server container.
Pull every server tag, client and trigger via the sGTM API. Validates transports, request mappings and client-server event parity.
L2 · TRANSPORT
Watch the traffic in motion.
Replay client events through your custom domain. Check first-party cookie scope, signed payload integrity, and 5xx rates from a real region.
L3 · DOWNSTREAM
Verify what actually arrives.
Compare client and server event volumes against GA4, Meta CAPI and Google Ads enhanced conversions. Flag dedupe failures and silent destination drops.
audit coverage
3 modules. 86 checks.
Every check ties back to a specific failure mode our team has seen in production. No filler. No “best practice” tax. Run the suite or pick a module — both are first-class.
Module 02
Transport Integrity
30
Custom domain DNS, first-party cookie scope, signed-request validation, error-rate budget, and downstream timeouts.
DNS1P cookiesSigningErrors
Module 03
Downstream Parity
28
Per-destination dedupe, match keys, currency consistency, conversion event coverage and client/server volume drift.
GA4CAPIAdsDedupe
sample findings
A taste of what typically surfaces.
Pulled from real reports (anonymised). Every finding includes evidence — a screenshot, a request trace, a JSON snippet — and a clear explanation of why it matters.
most-flagged · last 30 daysacross 2003 audits
01Client / server event count mismatch (-12%)
02Meta CAPI missing event_id on 18% of events
03First-party cookie domain mismatch on /checkout
04GA4 server tag missing user_id when signed in
the rest of the suite
One engine. Many audits.
Every tool reads its own surface but shares the same crawler, evidence store and report format. Run them independently or stitch them into a single integrity report.