Server-side tracking: measure more conversions, bid better
Browsers and ad blockers cut off more and more measurement data. What Google Ads doesn't see, it can't optimise: automated bidding then learns from only part of the truth. Server-side tracking closes a large part of this gap because measurement runs through your own server under your domain.
I'm Viktor Wagner, a certified Google Partner. I set up the system with Google Tag Manager, check it against your real orders or enquiries and hand it over with documentation.
Free initial consultationRequest a setup- 40+ five-star reviews
- Google Partner

What server-side tracking is and what it changes
With classic tracking, your visitor's browser sends the data directly to Google Analytics, Google Ads or Meta. That's exactly where the restrictions kick in: Safari and Firefox shorten cookie lifetimes, and ad blockers stop the requests entirely. With server-side tracking, the data first goes to a Google Tag Manager server container running on a subdomain of your website. Only this server passes it on to the platforms.
| Classic tracking in the browser | Server-Side Tracking | |
|---|---|---|
| Data path | From the browser directly to Google, Meta and others. | From the browser to your own server, and from there to the platforms. |
| Ad blockers and browser protection | Some conversions are lost. | Far fewer losses, because measurement runs through your own domain. |
| Cookie lifetime | Often limited to a few days in Safari. | Cookies set by the server last longer, so later purchases can be attributed. |
| Control | Each script decides for itself what it sends. | You decide centrally which data goes to which platform. |
| Loading time | Many scripts in the browser. | Fewer scripts in the browser; part of the work is done on the server. |
| Effort | Quick to set up, no server costs. | More effort to set up, plus ongoing server costs. |
Server-side tracking is not a way around consent. Without your visitors' consent, nothing goes to advertising platforms here either. Consent Mode v2 remains the foundation.
What I take care of in server-side tracking
Review of the existing setup
First, I look at what is measured today and where data is missing. Often a lot can already be improved in the existing conversion tracking before a server is needed.
Server container and subdomain
I set up the Google Tag Manager server container and connect it to a subdomain of your website. You get a recommendation on which provider is the most sensible place to run the server.
Google Ads and GA4
Conversions, Enhanced Conversions and GA4 events run through the server. That way, automated bidding in Google Ads gets more complete data.
Other platforms
Meta with the Conversions API, Microsoft Ads or LinkedIn can also be connected through the same server. You don't need a second setup for this.
Consent Mode v2
I connect the setup to your cookie banner. Whatever a visitor declines is not passed on to advertising platforms, and this can be verified.
Testing and hand-over
I compare the measured conversions with your real orders or enquiries. At the end, there is documentation that allows someone else to continue running the setup.
Who server-side tracking is worthwhile for
The effort pays off when missing data costs you measurable money:
- Online shops where several days often pass between the first click and the purchase.
- Businesses with larger advertising budgets whose bid strategies depend on every conversion.
- Providers with many Safari and iPhone users, because that's where the losses are greatest.
- Businesses using several advertising platforms that want to control their data sharing in one place.
For a local service business with a few enquiries a month, it's usually not the first step. There, clean browser tracking, Enhanced Conversions and a correctly configured Consent Mode v2 achieve more for less money. If that's the case for you, I'll tell you in the initial consultation.
From first look to hand-over
How the setup works
-
Free initial consultation
We clarify what you measure, what's missing and whether a server is the right step.
-
Review and quote
I review your setup and give you a fixed price for the implementation.
-
Setup and testing
I build the setup and compare the data with your real figures.
-
Hand-over
You get the documentation and, if you wish, a walkthrough of the finished setup.
How much does server-side tracking cost?
You get the setup as a tailored package at a fixed price. The scope depends on how many platforms are connected and what your existing tracking looks like. I'll give you the price after I've seen your setup and before any costs arise.
On top of that come ongoing server costs. They depend on the number of page views, and you pay them directly to the provider. What the ongoing work on the campaigns looks like is described on the Google Ads management page.
Frequently asked questions about server-side tracking
What is server-side tracking?
With server-side tracking, measurement data no longer goes directly from the browser to Google or other platforms. It first passes through your own server under your domain, the Google Tag Manager server container, and is forwarded from there. As a result, less data is lost to browser restrictions and ad blockers.
Do I still need consent with server-side tracking?
Yes. Server-side tracking doesn't change the obligation to obtain consent. Consent Mode v2 and your cookie banner still control which data may be collected. I set up the system so that nothing goes to advertising platforms without consent.
Who is server-side tracking worthwhile for?
Above all for online shops and for businesses with larger advertising budgets, where every missing conversion weakens automated bidding. For a local service business with a few enquiries a month, clean conversion tracking with Enhanced Conversions is usually enough. We'll clarify this in the initial consultation.
How much does server-side tracking cost?
You get the setup as a tailored package at a fixed price, which I'll give you after looking at your existing setup. On top of that come ongoing server costs, which you pay directly to the provider. They depend on the number of page views.
Does it work with my shop or website system?
In most cases, yes. The prerequisite is that Google Tag Manager can be integrated and a subdomain is created for the server. I check whether your system has any special requirements before making an offer.
Let's start the conversation
