Analytics & Growth

Every growth team we onboard has the same quiet problem before we say a word: GA4 and the bank statement don't agree, and nobody has measured by how much. Safari's Intelligent Tracking Prevention, ad-blockers running on a meaningful share of mobile Chrome, and cookie consent banners that (correctly) let users opt out — stacked together, these routinely erase 18–32% of real conversions from client-side analytics. The dashboard isn't wrong out of negligence. It's wrong because the browser itself is designed to make it wrong.

The fix isn't a GA4 setting or a new UTM convention — it's moving the measurement layer off the browser entirely. A server-side tagging deployment (we run this on sGTM and Stape) captures the conversion event on your own infrastructure and forwards it to each platform's conversion API directly, sidestepping the blockers and the tracking prevention that only target client-side scripts. That alone typically recovers a large share of the gap; reconciling the recovered events against CRM and bank data closes the rest.

Once the event layer is trustworthy, we add a second, independent read on top: marketing mix modelling, which estimates channel contribution from spend and outcome data rather than from cookies at all. It's slower to update than a live dashboard and it won't tell you which ad set to pause this afternoon — but it's the number that keeps working when a browser vendor ships the next privacy change, which is not a hypothetical, it's a quarterly event now.