A Connect and Classify
This phase guide is being expanded including detailed walkthroughs. The structure and steps below are accurate.
Connect your GTM and GA4 accounts, scan your existing setup, and see a readiness report that classifies what can move server-side.
What this phase does
Phase A earns trust before asking for infrastructure. You connect your accounts, the assistant scans your live GTM container, and you see a readiness report showing which tags and events can move server-side, which need review, and which stay in the browser. No infrastructure changes happen in this phase.
GCP project selection is deferred — you don't need to commit to server-side infrastructure until Phase B. This phase is about understanding what you have.
What can move server-side and what can't
A deeper look at the four classification categories: what moves cleanly, what needs review, what stays in the browser, and what's unsupported in this setup.
Before you start
- Platform Setup complete: desktop app paired, Google account authenticated.
- Access to the Google account that owns or has edit access to the GTM and GA4 resources.
What you'll do
- Select GTM and GA4 accounts. Choose the GTM account containing the web container you want to scan, and the GA4 account with your production property.
- Scan. The assistant pulls the live (published) version of your web GTM container and GA4 property metadata. If a server container already exists, it's scanned too.
- Review the readiness report. See your full tag and event inventory classified into four categories: routable as-is, needs review, browser-only, and unsupported. The report includes a complexity rating, critical event detection, and recommended next steps.
What you'll have when done
A readiness report showing your full GTM/GA4 inventory classified by server-side suitability, with a complexity rating and recommended next steps. You'll know exactly what's involved before committing to any infrastructure.