7 GTM Server Container
GSS creates and updates the server container’s required clients, tags, and triggers in your selected GTM workspace. Approve each row’s proposed change.
Note: This step content was written for the original dual-run architecture and is being updated for the current setup workflow. The guide overview reflects the current approach.
This step is being finalized. Content is accurate but will be updated and expanded before full release.
Deliverable
Server container forwards events with equivalent parameters.
Validation
This step covers the server GTM container. Configure creates or updates the GA4 client, the server All Pages trigger, and the sgtmgaaw forwarder tag in the GSS workspace (plus the Web Container Client on the first-party loader profile), then detection re-runs. The required GTM items panel shows which items are Ready, Missing, Changed, ambiguous, or intentionally ignored.
After configuration, switch to GTM server preview mode and walk an event all the way through the container. Confirm the GA4 client claims the incoming request, the forwarding tag fires, and important fields such as page_location are correct in the forwarded payload. This is the step where you verify the server container is transforming and forwarding traffic the way you expect.
Finish by checking the server-side GA4 DebugView (or equivalent real-time destination) to confirm the forwarded events actually arrive. If a config check passes but preview or DebugView doesn’t line up, stop and reconcile the discrepancy before moving to production validation.
Step Values
| Field | Current value |
|---|---|
| GTM Server Container | Pending |
| Workspace | Pending |
| Loader profile | Pending |
| GA4 client | Pending |
| Forwarding tag | Pending |
| IP redaction | Pending |
7.1 Validate Server Container Configuration
Click Create on each Missing item, Reset on each Changed item, and Pick on each Multiple-matches item, then Re-check. The item cards show what is Ready, Missing, Changed, or has multiple matches.
Checks
- HTTP First-party /gtm.js endpoint returns valid JS.
- API GA4 client is enabled in the server container.
- API GA4 client is configured to use default claim paths.
- API GA4 Configuration tag references the server measurement ID.
- API GA4 Configuration tag trigger is configured correctly.
- API IP address is not redacted before forwarding.
- API All default event parameters are included in forwarded hits.
7.2 Verify Runtime Behavior in Server Preview
Open GTM Preview for the server container and navigate to a page to verify.
Expected: GA4 client claims requests, forwarding tag fires, page_location is correct, events appear in server DebugView.
Checks
- Browser GA4 client claims incoming requests in preview mode.
- Browser GA4 Configuration tag fires successfully in preview mode.
- Browser page_location parameter is correct in forwarded hit.
- Browser Events appear in the server GA4 DebugView.
Documentation
Fields recorded during this step.
| Field | Description |
|---|---|
| GTM Server Container | GTM server container and its public ID. |
| Workspace | GTM server workspace used for edits. |
| Loader profile | Standard or first-party GTM loader. |
| GA4 client | GA4 client name and type in the server container. |
| Forwarding tag | GA4 event tag name and measurement ID. |
| IP redaction | Whether IP is redacted before forwarding. |
Use the app to validate this step automatically.
Request access