Server-side tagging and a warehouse are powerful. They are also optional, and the industry's habit of treating them as mandatory has cost more projects than it has helped. This article covers what the heavy stack does, what it costs, and how to decide.
The stack, honestly
Consented collection starts in the browser. Consent state gates what fires; nothing heavy changes that, it only changes where the event goes next.
Server-side GTM is a first-party endpoint that receives events, transforms them, and routes them onward. Its real benefits are control (you decide exactly what leaves) and cookie lifetime on your own domain.
Cloud Run hosts the sGTM container, and it is where the bill and the operational burden live. It is also the component most teams do not actually need.
BigQuery is the warehouse: raw events, queryable, joinable to backend truth. For most organisations this is the component that survives even when sGTM does not.
One event's full journey
When NOT to use the heavy stack
The decision variable is not volume — it is whether you need first-party cookie control and event transformation. If you do, sGTM earns its operational cost. If you do not, the other criteria apply: low event volume, no engineering owner, questions answerable by client-side plus the GA4 BigQuery export. Volume alone rarely justifies the heavy stack. The cost autopsy measured the Cloud Run bill and the maintenance load before removing the stack for exactly these reasons. The consented first-party stack article documents when the heavy stack was the right call — consent-gated collection into BigQuery with a reporting layer on top — and both lessons are folded in here.
The backend-truth reconciliation
The point of a warehouse is not storage; it is the join. Platform-reported conversions versus backend-measured outcomes, reconciled so neither is silently overwritten — that is what turns collection into decisions. The consent and blending article explains why the sources disagree in the first place.
Where to go next
- Agentic web analytics implementation — the lighter half of the measurement loop
- The agent telemetry stack — the unifying claim of this site: the same collection, reconciliation, and honest-unknowns discipline governs AI systems and marketing data. The tools differ; the method is one method.