Back to notes

October 1, 2026 · 5 min read

Client-Side Tagging Still Has a Place, Don't Let Anyone Tell You Otherwise

Server-side tagging has become the default recommendation for everything, and that's overcorrecting. Client-side still wins for a lot of real situations.

Hot TakeTagging

I've started hearing 'just move it server-side' as an automatic answer to tagging problems that have nothing to do with server-side tagging's actual benefits. A client asked me to migrate a low-traffic internal tool's basic pageview tracking to server-side GTM because they'd read it was 'the modern way to do it.' There was no ad blocker problem, no data ownership need, no enrichment requirement. Just cost and complexity added for a label.

Server-side tagging earns its complexity when you actually need what it provides: first-party data enrichment that can't happen in the browser, PII stripping before a third-party vendor sees a payload, or genuinely meaningful resilience against ad blockers on high-value conversion events. None of that is free. It's infrastructure you now operate, monitor, and pay for continuously, and for a huge share of tracking needs, that cost buys nothing you didn't already have.

Where client-side is still the right call

  • Low-traffic sites where Cloud Run cost and operational overhead outweighs any ad-blocker resilience gained.
  • Internal tools and admin dashboards with no third-party ad platform dependency and no PII-sensitive payloads to strip.
  • Early-stage implementations still iterating on what to even track — standing up server infrastructure before the measurement plan has stabilized is premature.
  • Teams without the engineering capacity to actually monitor and maintain a server container, where an unmonitored pipeline is worse than a simpler one that at least fails visibly in GTM's own debug tools.
Server-side tagging is infrastructure you now own. Owning infrastructure you don't need isn't rigor, it's just a more expensive way to track a pageview.

The actual decision criteria

Ask what server-side specifically buys you — enrichment, PII control, deduplication logic, ad-blocker resilience on revenue-critical events — and if the answer is 'nothing specific, it just seems like the right thing to do now,' that's the tell. Client-side tagging, done with a clean data layer and real DebugView discipline, is still a completely legitimate architecture for a large share of real sites, and the industry's collective swing toward treating it as deprecated is mostly vendors with Cloud Run infrastructure to sell.