Module 01
Schema Validation
52
Required keys present, types correct, enums in range, currency codes valid, nested arrays well-formed.
Required keysTypesEnumsCurrency
DATALAYER SCHEMA VALIDATION
Make the dataLayer behave before tags read it.
118 checks across 3 modules — catch missing keys, wrong types and ordering bugs before they pollute reports.
datalayeraudits.com · live audit
▲purchase event firing before consent_update4s ago
✗ecommerce.items[*].price serialised as string11s ago
▲Missing currency code on add_to_cart18s ago
✗user_id pushed inconsistently between routes25s ago
118
validation checks
3
audit modules
GA4 + GTM + Custom
schema support
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 · SCHEMA
Validate against the spec.
GA4 recommended events, the e-commerce 1.0 spec, and your own custom schema. Required keys, allowed types, enum membership — line by line.
L2 · ORDER
Catch race conditions.
Push order matters. Consent before measurement, page_view before purchase, identifiers before user-scoped events. Replay the timeline and flag every out-of-order sequence.
L3 · COVERAGE
Find the missing pages.
Crawl key user journeys end-to-end and flag pages where expected events never fire.
audit coverage
3 modules. 118 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
Event Ordering
36
Consent ordering, page_view sequencing, user identification before user-scoped events, e-commerce funnel order.
ConsentPage viewUser IDFunnel
Module 03
Coverage & Drift
30
Page coverage of expected events, dedupe of accidental double-pushes, drift detection across crawls.
CoverageDedupeDrift
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 2295 audits
01purchase event firing before consent_update
02ecommerce.items[*].price serialised as string
03Missing currency code on add_to_cart
04user_id pushed inconsistently between routes
05Duplicate page_view on SPA route change
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.