Audit
Audit reads your existing GTM web container and GA4 property and produces a readiness report — a tag-by-tag classification of what can move server-side, what needs review, and what stays in the browser. Nothing in your live setup changes during audit. No infrastructure is deployed, no tags are modified, no traffic is rerouted.
The output is an approved audit: a reviewed, acknowledged readiness report that the rest of the build executes against. Until audit is approved, the Build, Cloud, Connect, Publish, and Go Live stages stay locked.
Stage path: Discover & Select → Review Report → Approve
Four Classification Categories
Every tag in the live web container ends up in exactly one of these buckets. The bucket drives the readiness checks, the per-tag rows in the report's tag inventory, and what the Build stage ultimately writes into the server container.
| Category | What it means | Build effect |
|---|---|---|
| Routable as-is | GA4 Event tags (or equivalents) that map directly to a server-side equivalent without modification. | Mirrored to the server container during Connect. |
| Routable with review | Routable in principle, but the tag references variables or has parameters GSS isn't sure how to resolve server-side. Needs human acknowledgement. | Mirrored after the user explicitly acknowledges the review item on the Report step. |
| Browser-only | Tags that fundamentally cannot run server-side — they need browser context (DOM access, page-load timing, third-party SDKs that talk to the page). | Stays in the web container; not migrated. |
| Unsupported | GSS doesn't know how to classify the tag. Often custom HTML, vendor SDKs without server equivalents, or tag types the classifier doesn't model. | Stays in the web container; informational only. |
Article
What can move server-side and what can't
A deeper look at the four classification categories with real examples — what moves cleanly, what needs review, what stays in the browser, and why.