Ever noticed your analytics numbers don’t quite add up? Conversions disappearing into thin air, attribution gaps, or data that feels suspiciously low? You’re not alone. Between ad blockers, privacy legislation, and shifts in browser policy, your team could be working with incomplete data.
Almost 40% of UK users now block ads, while Apple’s iOS updates reduced reported conversions by as much as 50% in some accounts. Google Chrome has also been experimenting with new privacy features that affect how cookies are handled.
With this level of signal loss, relying only on traditional client-side tracking is no longer enough. That is where server-side tracking comes in. Before we look at how it works, let’s revisit the older method most of us still know well.
Client-side tracking is the standard method websites have used for years. When someone visits your site, JavaScript tags (such as the Meta Pixel or GA4 tag) run in their browser. These scripts record actions like page views, clicks, and purchases, and send that information directly to the platforms you use for analytics or advertising.
For a long time, this was simple and effective. But with ad blockers, cookie restrictions, and mobile privacy settings, many of these tags never fire. Businesses often lose 20–30% of their conversion data as a result, making it harder to measure performance and optimise spend.
Server-side tracking pulls analytics out of the browser’s hands and into yours. Instead of the user’s device calling home with tracking data, your secure server does the talking. You control what gets packaged up and sent to the platforms.
Think of client-side tracking as whispering across a noisy pub. Server-side? It’s like sending a note in a soundproof room — same message, but a lot less risk of it being garbled or blocked.
Yes, but in a smarter, more durable way. Rather than juggling flaky third-party cookies, server-side gives priority to first-party data, the stuff you own.
Example: A UK retailer relying solely on client-side tracking might lose nearly 40% of conversions to blockers. Post server-side switch, those conversions typically bounce back into view — improving attribution and cutting wasteful ad spend.
Google has adjusted its timeline and moved away from a full deprecation of third-party cookies. Instead, Chrome users will have more choice over how cookies are managed. For now, third-party cookies remain in Chrome.
Both continue to block third-party cookies by default. For ecommerce websites and marketers relying on accurate data and attribution, this means signal loss in these browsers is already baked in.
Client-side tracking still plays an important role. Most marketing teams have transitioned to server-side tracking or are implementing server-side tagging alongside client-side to improve consistency and give them greater control over what data is collected.
If you run paid search campaigns in the UK or EEA, you need to comply with Google Consent Mode V2. This update introduced two additional consent signals, ad_user_data and ad_personalisation, which let Google know whether they can use personal data for advertising and remarketing.
Consent Mode V2 is now mandatory if you want remarketing lists and modelled conversions to continue working in Google Ads and GA4 within the UK and EEA
Client-side tags often lose conversion data to ad blockers, cookie restrictions, or browser privacy settings. By routing events through your own server, more signals get through, meaning stronger attribution and smarter optimisation.
Every extra tracking script slows your website. Moving heavy tags server-side reduces browser load, improving site speed by 0.5–1 second on average. Faster pages aren’t just better for users; they’re rewarded by Google with stronger SEO performance.
Client-side libraries often collect more than you intend, from device details to browsing behaviour. With server-side tracking, you decide what data leaves your server and how it’s packaged. That means stricter control of personally identifiable information (PII) and compliance with privacy regulations like GDPR, POPIA, and DMA.
Lost signals mean smaller remarketing lists. Server-side tracking captures more consistent data across browsers and devices, allowing advertisers to grow audiences more quickly and reliably. That translates into larger remarketing pools, better lookalikes, and lower costs per conversion.
Ad blockers often kill requests to known vendor domains (e.g., google-analytics.com). With server-side tagging, you can route data through a first-party subdomain (e.g., analytics.yoursite.com), making it much harder for blockers to strip out your events.
Safari’s Intelligent Tracking Prevention (ITP) limits JavaScript-based cookies to 7 days or less. But cookies set server-side can last longer, helping businesses maintain user session history and conversion paths. While Apple has tightened some loopholes, server-issued cookies still provide more stability than client-only approaches.
Run client and server-side tags together carefully to avoid duplication.
Always test to make sure forms, downloads, and other critical events are tracked.
Mapping events to ad platforms requires accuracy. Mistakes lead to gaps in reporting.
Even with server-side in place, forgetting to integrate consent is often the biggest oversight. Even server-side tracking is still required to remain compliant and honour user consent.
For small websites with limited traffic, server-side tracking may be overkill. But if you’re investing heavily in paid media, remarketing, or data-driven optimisation, it quickly pays for itself through better attribution, cleaner compliance, and higher-performing campaigns.
Server-side tracking isn’t a flip-the-switch solution. It comes with technical and financial requirements that won’t suit every business:
While Google Tag Manager’s server-side container is free to configure, you’ll need to host it on a cloud service (Google Cloud, AWS, etc.). A standard setup typically costs $120–150/month (that’s about £90-£110 per month), scaling up with traffic volumes.
Unlike drag-and-drop client tagging, server-side tagging requires knowledge of JavaScript, APIs, and cloud infrastructure. You’ll need a developer or analytics specialist (like us) to set it up, map data flows, and maintain it.
To connect platforms like Meta (Conversions API), Google Ads (Enhanced Conversions), or TikTok, you’ll need to configure server endpoints carefully to avoid issues like double-counting or dropped events.
Browsers evolve, privacy regulations change, and platforms update APIs. Server-side setups require more active monitoring than client-only tracking.
While the benefits (greater accuracy, faster websites, better privacy control) are clear, the technical setup can be a hurdle for most businesses. Implementing server-side tracking is more complex than traditional client-side setups. It requires knowledge of:
This is where Verkeer can help. Our team specialises in advanced tracking, analytics, and SEO, and we’ve implemented server-side solutions for clients across multiple industries. Whether you need a full setup, troubleshooting, or ongoing optimisation, we’ll ensure your tracking is accurate, compliant, and future proof.
Client-side tracking is not going away, but it is no longer enough on its own. Server-side tracking is becoming the standard for improving data accuracy, protecting site performance, and staying compliant in a changing privacy landscape.
In the race for accurate, compliant, and actionable data, the real question isn’t should you move server-side, it’s how fast can you get there?
Want help making the switch? Verkeer’s got your back.
Client-side tracking happens in the user’s browser. Tags such as GA4 or the Meta Pixel run on-page and send data directly to platforms. Server-side tracking routes those same events to your own server first, giving you control over what is passed on. This improves data accuracy, reduces the risk of events being blocked, and allows you to manage privacy compliance centrally.
In Google Ads, server-side tracking often refers to using tools like Google Tag Manager’s server-side container or Enhanced Conversions to pass conversion data directly from your server to Google. This helps fill gaps left by blocked or missing client-side signals and improves the accuracy of conversion modelling.
Yes, server-side tracking is legal as long as it is implemented in compliance with privacy regulations like GDPR, POPIA, or CCPA. The key is consent. Users must be informed about what data you are collecting and how it will be used. Tools such as Google Consent Mode V2 ensure that server-side setups remain compliant while still allowing platforms to model performance data.
When a user interacts with your website, their actions are captured by tags or APIs as normal. Instead of sending that data directly to platforms from the browser, the information is sent to your server first. From there, your server packages and forwards the events to advertising and analytics platforms. This extra step allows you to enrich, filter, or anonymise data before it leaves your environment.
Key benefits of server-side tracking include more accurate data and attribution, faster website load times with fewer tracking scripts slowing page loads, larger remarketing audiences (as fewer signals are lost), and better compliance, since you control what data is sent to each platform.
In GA4, server-side tracking means routing measurement events through your own server before sending them to Google Analytics. This helps ensure more reliable event delivery, even when browsers block client-side tags. It also supports Enhanced Conversions, which use first-party data to improve attribution while respecting consent.