Tag Audit

Implementation observability

See what your GTM container is really doing.

Tag Audit Studio reads a GTM export locally, maps its dependencies, and turns structural risk into a practical remediation queue.

Local processingExplainable findingsJSON never executed
example / ecommerce-prod

Example audit

92 / 100

Healthy overall

3 critical issues

Tags

42

Triggers

28

Variables

57

Priority signals

{{dlv - email}}Meta - PurchaseAll Pages

A focused audit surface

Start with the work, not a dashboard tour.

Open a workspace to retain audit summaries, then move directly into a new container review. Every screen keeps the current audit, its findings, and the next action in reach.

Open workspace

Health in context

Score, severity, and next actions in the same workflow.

Actionable evidence

Each finding points to its rule, dependency, and JSON context.

Local history

The workspace retains the current audit summary in this browser.

Dependency Canvas

Follow the path from trigger to variable.

The Dependency Canvas makes the container structure visible. Broken and risky links are surfaced in the graph and open the relevant JSON context.

Open canvas
app.tagaudit.local / workspace / acme

Dependency canvas

SCANNING

TRIGGERS

TAGS

VARIABLES

A repeatable workflow

From export to an accountable next step.

  1. 01

    Import

    Upload a GTM JSON export. The file is validated and processed locally.

  2. 02

    Understand

    Review the score, priority findings, and dependency map.

  3. 03

    Fix

    Open the context, confirm in GTM Preview, and retain the next step.

Built to become a SaaS

Useful locally today. Explicit about production tomorrow.

The local flow runs in the browser and stores only structured audit summaries in the active browser workspace. Clerk, Cloudflare D1, and Stripe are foundation modules that require production configuration before they enforce access or retain client data.

View production requirements

Privacy

Local first

Access

Owner / Editor / Viewer

Data

Clerk + D1

PWA

When enabled

FAQ

Clear boundaries, not vague claims.

Does my JSON leave my computer?+

Not in the local flow. The file is analyzed in the browser and the local workspace retains only the structured audit summary.

Does this validate a published page?+

No. The engine reads export structure. Always confirm results in Preview, Tag Assistant, and GTM version review before publishing.

Can I manage multiple clients?+

The local product includes a workspace and role model. Client isolation and server-enforced access require Clerk and D1 configuration.

Can I buy a plan?+

Not in this deployment. The local auditor is available; checkout and commercial plans should only be enabled after operational and legal setup.

Make tracking work visible.

Open the workspace to organize the review, or begin straight from a GTM export.