What it checks
- Visible GTM container IDs and loader patterns
- Consent markers that likely change tag visibility
- Runtime-only tagging behavior when plain fetch is inconclusive
- Signals that suggest fragmented ownership or architecture drift
New Diagnostic
See what your GTM setup reveals before anyone else does.
The GTM Visibility Audit checks what an external observer can see, whether GTM appears visible at all, and whether the implementation suggests privacy or governance issues worth immediate review.
Visibility HTML-first scan
Checks what is plainly visible before escalating to runtime rendering.
Runtime Browser fallback
Used only when GTM looks JS-injected, consent-gated, or otherwise incomplete.
Outcome Private result access
No public report pages. Expiring, non-indexed result flow only.
Who it is for
This is built for marketing leaders, measurement owners, analytics leads, and privacy-conscious implementation teams who need a fast external read before they invest in a deeper review.
Why this exists
Many organizations assume their measurement layer is invisible, deliberate, and governed. In practice, a surprising amount is externally observable, inconsistently gated, or operationally fragmented. This scan is meant to surface that quickly.
“Shock report first, deeper privacy review second.” The scan is a diagnostic wedge, not the full audit.
Ready
Open scan.julienlenestour.com