Latest posts Visit blog
In plain words: what is this page about?

This article is about counting visitors from your own server. Ad blockers and browsers hide data from normal tracking. Tracking on the server can bring some data back. It must still follow privacy law. Read on to see how we do it. Ask us for details.

Ad blockers stop tracking scripts in the browser. Safari blocks third-party cookies without exception (WebKit), and Firefox has confined them to a separate jar per website by default since June 2022 (Mozilla). The result: part of your conversions never shows up in Google Ads or Meta – and with it the basis for steering your campaigns. Server-Side Tracking addresses exactly that. We show you what it does, where its limits are, and how we implement it for your online shop.

The Problem: Your Data Is Disappearing

Classic tracking runs in your visitors' browsers. JavaScript tags send data directly to Google Analytics, Meta, or other platforms. This worked for years – until ad blockers, browser restrictions, and GDPR banners massively reduced the data flow.

ProblemWhat happensEffect on measurement
Ad blockersThe tracking script is never loadedThe event never happens
Safari ITPCookies set by script are deleted after 7 days (WebKit)Returning visitors count as new
Cookie banner opt-outNo tracking without consentNo attribution to the campaign
iOS App TrackingNo cross-device identifier without permissionAttribution breaks between app and web

The consequence: your Google Ads and Meta campaigns are optimized with incomplete data. You pay for conversions that never appear in the statistics and cannot attribute your ad spend cleanly. How large the gap is for you depends on your audience, their devices and your consent rate – it only becomes solid when you compare the orders in your shop with what the ad accounts report for the same period.

The Solution: Server-Side Tracking

With Server-Side Tracking, we move data collection from the browser to your own server. Your visitors' browsers send data to your domain (first-party), and only your server communicates with Google, Meta, or other platforms.

The Critical Difference

Data goes to tracking.your-domain.example instead of google-analytics.com. Many ad blockers do not catch that – the events reach your server.

Bypass Ad Blockers

Requests go to your own domain. Most ad blockers don't recognize this as tracking.

Longer Cookie Lifetime

Cookies your own server sets in the HTTP header are not covered by the seven-day cap on script cookies. If the subdomain resolves via CNAME to an outside service, WebKit applies the cap anyway – which is why delivery belongs on your own infrastructure.

Faster Load Times

Less JavaScript in the browser. One request instead of dozens of tracking pixels.

Full Data Control

PII filters, anonymization, consent checks – all on your server before data is forwarded.

What Changes in Your Measurement

For e-commerce businesses, the switch has an effect in several places:

MetricBeforeWith Server-SideWhat changes
Conversion captureDepends on browser, blocker and consentThe event is created on your serverFewer drop-outs caused by blockers
Meta Ads attributionIncompleteEvents also run through the APIMore stable attribution
Google Ads ROASUnderestimatedCloser to the orders in your shopBetter basis for decisions
Work in the browserEvery vendor brings its own codeOne call to your own domainFewer scripts on the page
How to measure your own gap

Compare the orders in your shop backend with the conversions Google Ads and Meta report for the same period. That difference is your real data gap. Figures from someone else's case study say little about your shop – the measurement in your own account does.

Our Server-Side Tracking Solution

We implement Server-Side Tracking as a complete solution for Shopware, WooCommerce (WooCommerce agency), and other shop systems. You don't have to worry about anything – we handle setup, hosting, and monitoring.

GTM Server-Side

Google Tag Manager Server Container on EU infrastructure with custom domain.

Meta Conversions API

CAPI for Facebook and Instagram Ads with event deduplication.

Google Ads Enhanced

Enhanced Conversions for better attribution and campaign optimization.

GDPR-Compliant from the Start

Server-Side Tracking is not a free pass for tracking without consent. On the contrary: It gives you control to demonstrably implement GDPR compliance.

  • EU Hosting – Servers in Germany or EU region, no US data transfers
  • Consent Mode v2 – Google requirement since March 2024, correctly implemented
  • Data Minimization – PII filters and anonymization before forwarding
  • Audit Trail – Documentation of all data processing for evidence

Optional: Matomo as Cookieless Alternative

Additionally or alternatively, we implement Matomo as a privacy-friendly analytics solution. In its cookie-free configuration, Matomo stores nothing on the device. Whether that removes the consent requirement under § 25 TDDDG belongs in privacy consulting – the assessment depends on the individual case.

Cookie-free: nothing stored on the device

Without a cookie or an identifier on the device, the opt-out rate stops being a measurement gap. In exchange you lose recognition over longer periods – cookie-free measurement is stronger on reach and weaker on return visits.

Why 2026 Is the Right Time

The tracking landscape is changing fundamentally. Those who don't act now will fall behind:

  • Third-party cookies – Safari blocks them without exception (WebKit), Firefox has isolated them per website since June 2022 (Mozilla)
  • Consent – § 25 TDDDG requires it for any storage on the device, no matter where the processing happens afterwards
  • Meta Ads quality – Without the Conversions API, Meta reports a lower Event Match Quality; optimization then works with fewer signals
  • Google Consent Mode v2 – Required by Google for advertisers in the EEA since March 2024; without correct implementation there are no remarketing lists
Act Now

The longer you wait, the more historical data is missing for machine learning and campaign optimization. The transition usually takes several weeks, depending on the number of tags and destinations.

How Implementation Works

We handle the complete implementation for your shop. You don't have to worry about anything:

  1. Analysis – We review your current tracking setup and identify data losses
  2. Concept – Tailored solution for your requirements (GA4, Meta, Google Ads, etc.)
  3. Setup – Server container on EU infrastructure, custom domain, all tags and triggers Our article on cookieless tracking on your own infrastructure describes running it in house.
  4. Integration – Connection to your Shopware, WooCommerce (WooCommerce agency), or other shop
  5. Testing – Comprehensive tests, event deduplication, consent flows
  6. Go-Live – Parallel operation, then switch with monitoring

Frequently Asked Questions

Typically yes. German § 25 TDDDG (and the ePrivacy Directive across the EU) require consent for non-essential storage on the user’s device, regardless of where the data is processed afterwards. Server-side changes the data architecture, not the consent obligation. Where nothing is stored on the device at all, the assessment differs – that case belongs in privacy consulting.

That depends on traffic volume and the hosting you choose; there are also one-time setup costs. We work both out concretely for your shop in the quote.

Yes, Server-Side Tracking complements your existing setup. Existing tags, triggers, and variables continue to work – they'll send their data through the server container going forward.

Usually a few weeks from kickoff to go-live. For complex setups with many platforms, it may take longer. We coordinate the timeline individually with you.

No, latency is typically 50–200 milliseconds. Data appears in GA4 and Meta practically in real-time – you won't notice a difference.

Yes, we also offer individual solutions. For Shopware shops and WooCommerce shops, there are plugin-based CAPI solutions that we set up for you.

Recover Your Data Quality Now

Blocked scripts, deleted cookies and missing consent hit client-side tracking in three places at once. Server-Side Tracking moves collection to where you control it: more solid data, traceable attribution, documented processing. Whether it works entirely without a banner is covered in our article on the shop without a cookie banner.

We implement the solution for you – from analysis through setup to ongoing monitoring. Request your no-obligation quote now.