4 Cloud Run Services
Create or select the Cloud Run preview and tagging services that run the GTM server container image.
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
Two Cloud Run services deployed and validated.
Validation
Use this step to validate the infrastructure that will host server-side tagging. Confirm that both the tagging service and the preview service exist, are reachable, and are the services you selected in Configuration. Treat any service mismatch here as a hard stop, because later tagging checks depend on these exact endpoints.
Check Cloud Run settings, not just service existence. Verify that the tagging service has minimum instances configured to reduce cold starts, that both services allow the access mode you expect, and that their /healthy endpoints return 200. Also verify that the public TLS endpoint is valid and that any DNS or CDN layer is configured so requests actually reach the tagging service without unintended proxy behavior.
Finally, confirm that GTM is pointed at the right runtime URLs: the live server container URL and the preview server URL. If GTM still points to an old environment, later preview and production validations will look inconsistent even though the underlying infrastructure is healthy.
4.1 Cloud Run Validation
Validates both Cloud Run services are deployed, correctly configured, and accessible.
Checks
- API Preview service is running
- API Preview mode enabled
- API Preview max instances ≤ 1
- HTTP Preview /healthy returns 200
- API Tagging service is running
- API Tagging min instances ≥ 1
- API CONTAINER_CONFIG set on both services
- API PREVIEW_SERVER_URL set on tagging service
- API Both services allow unauthenticated access
Use the app to validate this step automatically.
Request access