TLDR: Most marketing teams are making budget decisions using incomplete data and they aren’t aware of it. Ad blockers, Safari’s Intelligent Tracking Prevention (ITP), and browser privacy restrictions are taking away 10 to 30% of conversion data from standard client-side tracking setups. That’s the difference between a campaign that looks like it’s underperforming and one that’s driving revenue you can’t see.
Server-side tracking is one of the most effective ways to recover that missing data. Most people haven’t implemented it yet, and those who have aren’t entirely sure how it works, this guide explains it clearly.
What is server-side tracking?
With client-side tracking, the user’s browser sends data directly to platforms such as Google Analytics or Meta. A tag fires, a pixel loads and the data makes its journey straight from the visitor’s device to the ad platform.
Server-side tracking adds another step. Instead of the browser talking directly to Google or Meta, data is sent to your own server first, then forwarded on to those platforms. That extra step gives you more control, more accuracy and far more resilience against the things that break client-side tracking – ad blockers, ITP and browser privacy restrictions.
Client-side vs server-side tracking – what’s the difference?
These two types of tracking solve the same problem in different places.
Client-side tracking
This relies on tags and pixels firing inside the browser. If a user has an ad blocker, a strict privacy browser, or a shortened cookie lifespan, the data doesn’t make it out.
Server-side tracking
This fires from your own server after the event has already been confirmed. It doesn’t get blocked by the browser, so it avoids those restrictions almost entirely.
Client-side tracking depends on the browser cooperating, whereas server-side tracking doesn’t need it to.
How does server-side tracking work?
Here’s how server-side tracking works in practice. When a website user takes an action on your site, adding to cart, completing a purchase, signing up for a demo etc, that event is captured on your server rather than relying on a browser tag firing correctly. Your server then creates a clean, complete piece of data and sends it on to Google, Meta, or whichever platform you’reusing.
Because the data travels server-to-server, it bypasses ad blockers and browser-level restrictions entirely. There’s no extension or cookie blocker mid-journey.
Does server-side tracking use cookies?
Server-side tracking doesn’t rely on third-party cookies at all. It can use first-party cookies set by your own server, and those behave very differently – they have a longer lifespan and aren’tsubject to the same browser restrictions that third-party cookies face.
That makes server-side tracking more privacy-friendly and easier to align with GDPR requirements than traditional client-side tracking. The data is captured and stored on your server, which means it doesn’t depend on a user’s browser accepting, or persisting, a cookie in the first place.
Why does server-side tracking matter right now?
Ad blockers are now used by a significant proportion of web users. Safari’s ITP limits cookie lifespans to as little as 24 hours. In many European markets, GDPR consent rates mean 20 to 40% of users decline analytics cookies entirely.
The result is a growing gap between what really happened on your website and what your analytics platform can see. For marketers making budget decisions off that data, it’s not entirely accurate.
What data are you losing without it?
It’s happening every day, in ways that are easy to miss:
- Cross-device journeys where the cookie ID breaks between an app’s in-browser view and the user’s default browser
- Conversions on iOS Safari where ITP has already wiped the cookie before the sale completes
- Purchases attributed to the thank-you page instead of the ad campaign that actually drove them
- Users who had an ad blocker running at the exact moment they converted
Each of these can be small problems in isolation, but added together across a full funnel, they can meaningfully understate what your paid channels are actually doing.
How to implement server-side tracking
Implementing server-side tracking doesn’t require rebuilding your entire tech stack. There are three main routes, depending on your team’s setup and technical resource.
Google Tag Manager server-side container
This is the most common route for Google Ads and GA4 measurement. A server-side GTM container is deployed on Google Cloud, or an alternative like AWS or Azure, and it acts as a proxy between your website and the platforms that you’re sending data to.
It’s the recommended option for most accounts because GTM’s interface is familiar and the setup process is well documented. It also makes collecting user-provided data for Enhanced Conversions far more straightforward. For the full technical walkthrough, Google’s official server-side GTM documentation is the best starting point.
Meta Conversions API (CAPI)
Meta’s server-side solution works alongside your standard Meta Pixel, sending conversion events directly from your server rather than relying solely on browser-side pixel firing. If you’rerunning any meaningful paid social spend on Meta, CAPI isn’t optional, it’s essential. It recovers exactly the conversion data that ITP and ad blockers are stripping from pixel events.
Managed server-side platforms
If your team doesn’t have significant developer resource, managed platforms like Stape or Elevar offer pre-built server-side tracking with ready-made connectors for Shopify, WooCommerce, and other ecommerce platforms. The technical work is lower, deployment is faster and setup typically takes one to two days rather than weeks.
How ASK BOSCO® connects to your server-side data
Once server-side tracking is in place and your conversion data is more complete, the next challenge is making sense of it across channels. That’s where ASK BOSCO® comes in.
ASK BOSCO® pulls your Google Ads, Meta, GA4, and ecommerce data into a single unified reporting layer, so the cleaner conversion data your server-side setup generates feeds directly into the budget planning and cross-channel reporting the platform is built around. The quality of the data underneath the model matters and server-side tracking is one of the smartest ways to improve it.
Want to see what your data could look like once it’s complete? Book a demo with ASK BOSCO® and find out.
