Server-side tracking: why cookieless measurement is the future

Server-side tracking (SST) is a measurement method where event data is sent to advertising platforms like Google Ads and Meta Ads via your own server, rather than through the user's browser. This structurally bypasses the limitations of browser cookies, ad blockers, and iOS privacy restrictions. In 2026, SST implementation is no longer optional for advertisers who want their data to accurately reflect reality.

Key takeaways

• Server-side tracking routes measurement data through your own server, removing cookies and ad blockers from the equation entirely.
• Client-side tracking loses a significant share of conversion data due to ITP, ad blockers, and cookie refusal, which distorts Smart Bidding signals.
• A proper SST implementation requires a server-side Google Tag Manager (sGTM) container, first-party cookie configuration, and signal enrichment via Enhanced Conversions.
• GDPR compliance and cookieless measurement are compatible: SST gives you more control over what data is shared and when.
• AdBrains uses its own sGTM infrastructure to enrich conversion signals and improve Smart Bidding performance beyond what standard client-side tagging can achieve.

What exactly is server-side tracking?

Server-side tracking means routing measurement events, such as purchases, form submissions, or page views, from your own server environment to the advertising platform. With traditional client-side tracking, a browser tag places a JavaScript pixel on the user's page, which communicates directly with Google or Meta. The problem: the user's browser sits between you and your data.

Browsers like Safari block third-party cookies via Intelligent Tracking Prevention (ITP). Firefox does the same through Enhanced Tracking Protection (ETP). Ad blockers actively suppress pixels. And the growing requirement for cookie consent means a portion of your visitors are never measured, even when they do convert.

With server-side tracking, the data flow is different. The browser sends an event to a server-side container hosted on your own domain, typically a sGTM container. That container processes the data and forwards it to Google Ads, Meta, or other platforms. Because the request now comes from a server rather than from the user's browser, ad blockers and ITP restrictions are largely bypassed.

Why client-side tracking is becoming less reliable

Client-side vs. Server-side tracking

What changes when you switch to SST?

Client-side (cookie)

• Dependent on browser cookies
• Blocked by ad blockers
• Limited cookie lifetime (ITP, ETP)
• Data routed through user's browser
• Vulnerable to iOS privacy restrictions
• No control over data quality

Server-side tracking (SST)Recommended

• Works independently of browser cookies
• Cannot be blocked by ad blockers
• First-party data with longer lifespan
• Data routed via your own server
• Privacy-resistant and GDPR-compliant
• Full control over signal enrichment

The reliability issues with client-side tracking are not new, but they compound every year. Apple has tightened ITP multiple times. Third-party cookies are increasingly restricted or blocked. Consent management platforms mean that a meaningful share of your visitors simply never accept cookies.

In practice, this means your Google Ads account reports fewer conversions than actually occur. Smart Bidding, which depends entirely on conversion signals to optimise bids, works from a distorted picture. A Target CPA or Target ROAS strategy running on incomplete data steers in the wrong direction. You may end up paying too much for traffic that converts but goes untracked, or cutting budgets at moments that are actually performing well.

For ToetsJeKennis.nl, an online exam and course platform with an average order value of around 50 euros, every missed conversion event directly skews the ROAS calculations in Google Ads. If 30 percent of purchases go unrecorded, the algorithm optimises toward a fictional efficiency. Server-side tracking captures the conversions that would otherwise be lost to ad blockers or Safari restrictions, making the overall picture for Smart Bidding substantially more accurate.

How SST implementation works technically

An SST implementation revolves around three core components: a server-side container, a first-party cookie setup, and signal enrichment. The steps involved in a correct implementation include:

1. Set up a server-side GTM container: Create a sGTM container in Google Tag Manager and host it on your own subdomain (e.g. metrics.yourdomain.com). To the browser, this traffic appears as first-party.
2. Reconfigure the client-side GA4 tag: Point the GA4 configuration tag on the website to the sGTM container rather than directly to Google, so all data flows through your server.
3. Route Google Ads conversion tracking via sGTM: Place the Google Ads conversion tag inside the server-side container, so conversion events are sent server-to-server.
4. Set up first-party cookies: Use sGTM to set first-party cookies on your own domain. These have a longer lifespan than third-party cookies and are not restricted by browsers.
5. Enable Enhanced Conversions: Send hashed customer data such as email addresses alongside conversion events, allowing Google to match conversions even without a cookie.
6. Test and validate: Use sGTM preview mode and Google Tag Assistant to verify all events fire correctly and that no duplicate measurements occur due to missing deduplication keys.

These steps require solid knowledge of GTM, GA4, and the Google Ads API. Combining GA4 server-side tracking with correct event forwarding to Google Ads is where most of this complexity lives. Implementation errors, such as missing deduplication logic or incorrect trigger configuration, result in double-counted conversions or missed events. That is exactly why an automated, monitored approach adds so much value.

Server-side tracking and GDPR compliance

A common misconception is that server-side tracking conflicts with GDPR or cookie law. The opposite is true. SST gives you more control. Through the sGTM container, you decide exactly which data is forwarded to which platform and when. You can link the data stream to your cookie banner consent signal, so only data from users who have given consent reaches the platform. This setup works seamlessly with Consent Mode v2, ensuring that consent status is passed to Google for compliant conversion modelling even when a visitor declines cookies.

For Clima-Active.nl, which depends on quote requests as its primary conversion, a long cookie lifespan is especially relevant. The sales cycle for a heat pump or air conditioning installation is not a single day. If a user first visits the website in week one and submits a quote request in week three, you need to be able to attribute that conversion correctly. With client-side cookies in Safari, that has become nearly impossible. With first-party SST cookies and proper consent linkage, it works reliably.

What SST delivers for Smart Bidding and ROAS

Conversion flow: SST vs. client-side tracking

Example calculation: 10,000 sessions per month, average e-commerce site

Sessions (all visitors)

Starting point: all visitors

Measured with client-side

~35% loss due to ad blockers, ITP, cookie refusal

Measured with SST

Loss limited to genuine opt-outs

Usable for Smart Bidding

After deduplication and quality check

SST consistently delivers more usable conversion signals for Smart Bidding

The direct effect of a correct SST implementation is that Smart Bidding receives more and better signals. Target CPA and Target ROAS algorithms learn from conversion patterns. The more accurate conversion events the algorithm sees, the better it can identify which keywords, audiences, and time slots are profitable. This accuracy also makes conversion value rules, which adjust reported value by audience, location, or device, far more reliable inputs for the bidding algorithm.

Enhanced Conversions add another layer. By sending hashed email addresses or phone numbers alongside a conversion event, Google can match that conversion to a specific click, even without a cookie. This is particularly valuable when a user shops across multiple devices or browsers. According to Google Ads Help documentation (2026), Enhanced Conversions lead to a measurable improvement in conversion observation rates, though the exact impact varies per account.

For E-4motion.com, the webshop for new electric folding bikes, visitors typically need multiple sessions before purchasing. If the first-session cookie is cut short by ITP after one day, attribution to the original campaign disappears. SST with first-party cookies and Enhanced Conversions ensures the full journey is measured, from first click to purchase or test-ride request.

How AdBrains automates server-side tracking

AdBrains has built its own sGTM infrastructure that goes well beyond a standard SST setup. Where most agencies implement server-side tracking once and check it periodically, our AI technology actively integrates SST signals into the daily optimisation process.

Our server-side signal enrichment system enriches every conversion event with first-party data before it reaches Google Ads or Meta. That means hashed customer identifiers, session attribution data, and consent status are automatically included per event. Smart Bidding therefore always receives the most complete version of every signal, even when the user has an ad blocker or is using a privacy-focused browser.

Our multi-agent verification system monitors data quality continuously. Four independent AI agents check whether conversion events are being passed correctly, whether duplicate measurements occur due to missing deduplication keys, and whether the sGTM container is still functioning correctly after website or GTM configuration updates. When a deviation is detected, the system automatically generates a remediation recommendation, without any manual login required.

Automated tCPA/tROAS optimisation at AdBrains works directly with enriched SST signals. Because our AI evaluates conversion data quality daily, bidding strategy adjustments are grounded in reliable, complete data. For a client like LeroyBrouwer.nl, where lead quality varies by form type, this means the system monitors not just lead volume but also signal strength per conversion type, adjusting bids accordingly.

On top of that, AdBrains runs automated quality checks on Enhanced Conversions match rates. If the match rate drops, which can happen after a checkout flow change or a new payment provider, our system flags this proactively and adjusts the implementation. In practice, this means AdBrains clients maintain structurally higher match rates than accounts where SST was set up once and left unmonitored.

SST vs. client-side tracking: an overview

Benefits of SST implementation for advertisers

Qualitative impact score per benefit (scale 1-10, based on industry insights)

More complete conversion data

9

Better Smart Bidding signals

9

Less ad blocker loss

8

GDPR compliance

8

Longer cookie lifespan

7

Enhanced Conversions enabled

8

The table makes clear that SST outperforms on virtually every measurement-quality criterion, but also demands more in terms of setup and maintenance. That is precisely why automated monitoring, as provided by AdBrains, allows SST to deliver its full potential rather than degrading silently over time.

Who should implement SST now?

Server-side tracking is not reserved for large e-commerce businesses. Any advertiser running serious budgets in Google Ads or Meta Ads, and wanting their bidding strategy to be based on accurate data, benefits from SST. This applies to webshops with a high share of Safari users, lead generation companies with longer sales cycles, and industries where cookies are systematically refused by the target audience.

The following situations make SST particularly urgent:

• You have a high percentage of mobile visitors on iOS/Safari and notice that your Google Ads conversions lag behind your actual revenue figures.
• Your site category (health, finance, legal) has an above-average cookie refusal rate.
• You use Performance Max or Smart Shopping campaigns, where signal strength directly affects campaign performance.
• Your sales cycle spans multiple sessions or days, making last-click attribution on short-lived cookies structurally inaccurate.
• You want to use Enhanced Conversions but find the match rate too low to rely on for optimisation decisions.

Frequently asked questions about server-side tracking

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

With client-side tracking, the user's browser sends measurement data directly to Google or Meta via a JavaScript pixel. With server-side tracking, that data flow runs through your own server, so ad blockers and browser restrictions have no effect. SST gives you more control over what data is forwarded and is far less vulnerable to privacy measures in browsers like Safari.

Is server-side tracking cookieless?

Server-side tracking is not entirely cookieless, but it uses first-party cookies instead of third-party cookies. Those first-party cookies are placed on your own domain via the sGTM container, so they are not restricted by ITP or similar browser limitations. Combined with Enhanced Conversions, you can match conversions without any cookie being present at all, using hashed customer identifiers. That is what "server-side tracking cookieless" means in practice.

How long does an SST implementation take?

A basic SST implementation via sGTM can be set up technically within a few days, but a complete and validated implementation including Enhanced Conversions, deduplication, and consent linkage typically takes one to two weeks. The time is mainly spent on testing, validating, and refining event configuration, not on the technical setup itself. Active monitoring after launch is an ongoing task.

Does server-side tracking affect page speed?

Yes, positively. Because fewer JavaScript pixels are loaded directly in the browser, page speed generally improves. The browser has fewer external requests to process, which reduces load time. This is a useful secondary benefit alongside the primary measurement improvements.