Server-side tracking: why cookieless measurement is the future

The digital advertising landscape is changing faster than ever before. Browsers block third-party cookies, users install adblockers, and privacy regulations like GDPR impose increasingly strict requirements on data collection. For advertisers who rely on accurate conversion data, this means one thing: the way you measure must fundamentally change. Server-side tracking is no longer an optional upgrade but the indispensable foundation for future-proof Google Ads campaigns in 2026.

What is server-side tracking and how does it work?

Conversions tracked per method (relative)

Client-side (base)

62%

Server-side (SST)

100%

SST + Enhanced

+38% vs. client-side

Client-side only

Server-side tracking

SST + Enhanced Conversions

With traditional client-side tracking, all measurement logic runs in the user's browser. A JavaScript tag fires when someone loads a page, submits a form, or completes a purchase. That tag then sends a request to external platforms like Google Analytics or Google Ads. The problem is that adblockers, Intelligent Tracking Prevention (ITP) in Safari, and browser restrictions intercept those requests with increasing frequency. The result is a growing gap in measurement data, while ad algorithms need more signals than ever to perform well.

Server-side tracking works fundamentally differently. Instead of the browser communicating directly with advertising platforms, the browser sends an event to your own server or a dedicated tracking server. That server processes the event, optionally enriches it with additional data, and only then forwards it to Google Ads, Meta, or other platforms. Because the communication happens server-to-server, adblockers and browser restrictions have no effect on it. You retain full control over which data is forwarded, in what format, and to which platform.

A concrete example: ToetsJeKennis.nl, a platform for online knowledge assessments, processes hundreds of test registrations and course purchases daily. By switching to server-side tracking via Google Tag Manager Server-Side, the number of registered conversions in Google Ads increased substantially, simply because events previously blocked by Safari or Firefox now arrived correctly. This provided better data for Smart Bidding and ultimately a lower cost-per-acquisition.

Privacy, GDPR and the cookieless future

The cookieless future is no longer a distant horizon; it is the present. Apple's Safari has blocked all third-party cookies by default for years through Intelligent Tracking Prevention. Firefox followed with Enhanced Tracking Protection. And Google itself is developing Privacy Sandbox alternatives for third-party cookies in Chrome, while simultaneously improving its own first-party data communication through server-side infrastructure.

From a privacy legislation perspective, server-side tracking is equally attractive. Because you as the advertiser control which data is stored and forwarded, it is far easier to comply with GDPR and the European ePrivacy Directive. You can specify exactly which data fields are transmitted, hash personal data before sending, and document the data processing in your privacy policy. This is not only legally responsible, it also builds user trust in your platform.

Advertisers who correctly combine server-side tracking with Consent Mode v2 and Enhanced Conversions see an average of 23% more conversions tracked compared to cookie-based client-side measurement alone. This figure increases further as the share of Safari and Firefox users in the target audience grows. For platforms like ToetsJeKennis.nl, where students and professionals often browse on Apple devices, this makes a substantial difference in the quality of data fed back to Google Ads. Better data means better-trained Smart Bidding algorithms, and therefore a higher return on ad spend over the long term.

Client-side vs. server-side tracking: an honest comparison

To make an informed decision, it is helpful to compare both methods side by side. The table below provides an overview of the key characteristics and differences.

Feature	Client-side tracking	Server-side tracking
Vulnerability to adblockers	High (many events blocked)	Low (first-party communication)
Cookie restrictions (Safari/Firefox)	Heavily affected by ITP	Virtually no impact
GDPR compliance control	Limited (data goes directly to third party)	Full (you control the data)
Page load time impact	Noticeable due to multiple tags	Minimal (less JS in browser)
Implementation complexity	Low to medium	Medium to high
Data completeness (2026)	60-75% of actual conversions	90-100% of actual conversions
Future-proofing	Declining	Growing

What stands out immediately: server-side tracking requires a higher initial technical investment and low ongoing server costs, but delivers a significantly better outcome on virtually every other dimension. Data completeness is particularly decisive in 2026. Advertisers relying on client-side tracking are feeding their automated bidding on only 60 to 75 percent of actual conversions.

Key benefits of SST for Google Ads campaigns

Server-side tracking has direct, measurable consequences for the performance of your Google Ads campaigns. Here are the most important benefits:

• More complete conversion signals: Google Ads Smart Bidding learns from every registered conversion. The more conversions are correctly tracked, the more accurately the algorithm can bid. For ToetsJeKennis.nl, this translated into a demonstrably better CPA after SST implementation.
• Better attribution models: Server-side tracking enables more accurate attribution to the right touchpoint, because the server always has access to complete session information regardless of browser restrictions.
• Improved page speed: With less JavaScript loading in the user's browser, Core Web Vitals scores improve. This indirectly benefits both user experience and Quality Score in Google Ads.
• Enhanced Conversions without privacy risk: Hashed user data, such as a SHA-256 email address, is sent securely via the server without exposing raw personal data in the browser.
• Future-proofing: The infrastructure you build now will continue to work when Chrome definitively phases out third-party cookies and new privacy legislation comes into force.
• Better data quality for reporting: Google Analytics 4 analysis becomes more accurate, leading to better decisions about budget allocation and targeting.

Enhanced Conversions and Consent Mode: the perfect complement to SST

Server-side tracking rarely stands alone. The greatest gains come when SST is combined with two other Google technologies: Enhanced Conversions and Consent Mode v2.

Enhanced Conversions adds hashed first-party user data to conversion events. When a user of ToetsJeKennis.nl purchases a course and is logged in with an email address, that hashed email can be sent alongside the conversion event via the server. Google then matches this with the user's Google account and can track conversions that would otherwise be invisible, even when cookies are absent.

Consent Mode v2 completes the picture. When a user does not consent to tracking cookies, Google still registers a pinged conversion and models based on the behavior of similar users who did consent. This produces modeled conversion data that Smart Bidding algorithms can use without violating the user's privacy choice. The combination of SST, Enhanced Conversions, and Consent Mode v2 represents the most robust measurement architecture available in 2026.

Want to learn how this approach translates into campaign results? Explore our approach to see how AdBrains integrates SST into every campaign structure by default.

Frequently asked questions about server-side tracking

What is the difference between client-side and server-side tracking?

With client-side tracking, measurement logic runs in the end user's browser via JavaScript tags. Those tags are vulnerable to adblockers and cookie restrictions. Server-side tracking moves the measurement logic to your own server. That server receives events from the browser and forwards them to advertising platforms, out of reach of adblockers and browser restrictions. The result is a more complete, more reliable dataset.

Is server-side tracking GDPR-compliant?

Yes, when correctly configured. Because you as the advertiser or agency manage the server, you have full control over which data is processed and forwarded. Personal data can be hashed before being sent to advertising platforms, and you can document the data flow precisely in your privacy policy. Combined with Consent Mode v2, the architecture is both technically and legally sound.

How much does it cost to set up server-side tracking?

Infrastructure costs for a GTM Server-Side container via Google Cloud Run are typically modest: between five and thirty euros per month, depending on traffic volume. Implementation costs depend on the complexity of your existing tracking setup. A basic implementation is usually achievable within one to two weeks with a specialized agency. The payback period is short: advertisers switching to SST see an almost immediate improvement in the number of registered conversions, which has direct value for Smart Bidding performance. Curious about pricing for a professional SST implementation at AdBrains? We explain it transparently.

Does server-side tracking affect page speed?

Positively, in fact. Since part of the tracking logic moves from the browser to the server, fewer JavaScript files need to load in the user's browser. This reduces page load time and improves Core Web Vitals scores. For ToetsJeKennis.nl, this meant not only better tracking data but also a noticeable improvement in the LCP score, which enhances user experience and indirectly supports Quality Score in Google Ads.

Does server-side tracking work for smaller advertisers too?

Absolutely. While the initial setup requires some technical knowledge, ongoing costs are low and the benefits are significant for any advertiser who takes measurement seriously. Even for a mid-sized platform like ToetsJeKennis.nl, with a modest daily conversion volume, SST delivered immediately visible improvements in the quality of data fed back to Google Ads. Have more questions? Visit our FAQ page for more answers.