Why your tracking quietly stopped working

If your marketing data feels less reliable than it did a few years ago, you’re not imagining it. Browser restrictions on third-party cookies, Apple’s privacy changes, ad-blockers and consent requirements have steadily eroded traditional client-side tracking — the kind that runs entirely in the user’s browser. The result is under-reported conversions, broken attribution and a growing gap between what actually happened and what your analytics say. This isn’t a tooling failure you can ignore; it’s a structural shift that any business scaling paid spend has to address.

GA4, in leader’s terms

Google Analytics 4 is the current standard, but out of the box most implementations are configured around pageviews rather than the commercial events that matter. The fix isn’t “install GA4”; it’s configuring it around your real questions — which events represent a qualified lead, a booking, a purchase, an activation — so the data answers “is this working?” rather than “how many pages were viewed?”. Google’s own Tag Manager documentation covers the mechanics; the value we add is deciding what to measure against your commercial model.

What server-side tagging actually does

Server-side tagging moves the collection of data from the user’s browser to your own server. In plain terms: instead of the browser sending events directly to Google, Meta and others (where ad-blockers, browser restrictions and data loss intervene), events go first to a server you control, which then forwards them. The benefits for a marketing leader are practical — more complete and accurate data, more resilience to browser and platform changes, better control over what data is shared and with whom, and often improved site performance. It’s more work to set up, and for any business serious about scaling spend it’s worth it.

Consent and privacy are built in, not bolted on

Under UK GDPR and PECR, non-essential tracking requires consent. Done properly, server-side collection works with a consent management platform and Google’s Consent Mode so that tags respect user choices — and you still recover modelled data where consent is declined, rather than simply losing it. The point is that privacy compliance and good measurement aren’t in tension when the stack is designed correctly from the start. (This is a technical and legal area — implement with a consent platform and, where needed, a legal review.)

What “good” looks like

A healthy setup: GA4 configured around commercial events; server-side collection for resilience and accuracy; Consent Mode wired to your consent banner; and the whole thing feeding a single view of CAC, payback and pipeline (see the measurement stack pillar). You don’t need a huge team to run it once it’s built — you need it built right.

Not sure whether your tracking can be trusted? A Growth Diagnostic includes a measurement audit. Request a Growth Diagnostic → or explore analytics & attribution.