B Validation

This phase guide is being expanded including detailed walkthroughs. The structure and steps below are accurate.

Set up the server-side path, validate it with a temporary property, and confirm everything works before touching production.

What this phase does

Phase B builds the server-side path and tests it safely. You create a temporary GA4 property, deploy a server container on Cloud Run, and route a copy of your traffic through the server path to the test property. The assistant runs validation checks — event arrival, parameter presence, volume sanity, routing health — and shows pass, fail, or needs attention for each critical event.

Your production property stays untouched throughout this phase. The temporary property exists only for validation.

Before you start

Phase A complete: setup scanned, readiness report reviewed.
A GCP project selected (deferred from Platform Setup to this phase).

What you'll do

Select your GCP project. The assistant verifies you have the right access and required APIs enabled.
Create a temporary test GA4 property. You create this in the GA4 Admin console; the assistant verifies it's accessible.
Create or connect a server container. Deploy the GTM server container on Cloud Run. The assistant provides instructions and verifies the deployment.
Select events for validation. Choose which events to validate server-side (default: all routable events plus critical events). You can adjust the selection.
Configure the server-side path. The assistant creates the necessary tags in the server GTM container via a dedicated workspace. You review the changes and confirm before publishing.
Configure the forwarding route. The assistant creates a forwarding tag in the web GTM container that sends a copy of traffic to the server path. You review and confirm before publishing.
Run validation checks. The assistant checks event arrival, parameter presence, volume sanity, and routing health. Review results on the validation dashboard.
Resolve issues. For any failures, the assistant shows issue cards with likely cause and recommended action. Resolve or accept known differences.

What you'll have when done

A validated server-side path with all critical events confirmed as arriving correctly. A validation dashboard showing pass/fail status per event. A readiness decision for whether to proceed to go-live.