← Back to blog
trackingprivacyconsentserver-side

Privacy-Oriented Tracking: Measuring Without US Services, Consent Mode v2 & Server-Side

Setting up privacy-oriented tracking: Server-Side, Consent Mode v2, First-Party Data. With concrete tools, checklists and honest assessment – no legal advice.

· Valorferrum

Tracking is only as valuable as its legal basis. Since the GDPR (2018) and the TTDSG in Germany (2021), the situation is actually clear: anyone processing personal data or accessing the user’s end device requires active consent. Most website operators know this too. But let’s be honest: few of them actually implement it cleanly in technical and legal terms.

I describe here how tracking can be set up in a privacy-oriented way – with server-side tracking, Consent Mode v2 and first-party data. Important up front: This is not legal advice. Legal assessment must always be done by a specialized attorney. I am talking here about technical handling within the tracking cosmos, not about legal conformity guarantees.

Why privacy-oriented tracking is not a contradiction

I often hear: “GDPR-compliant tracking doesn’t even exist, or it destroys all data.” That’s not quite right. What does exist is privacy-oriented tracking – tracking that implements Privacy by Design:

PrincipleWhat it meansTechnical implementation (as I know it)
Data minimizationOnly collect what is necessary for the purposeNo unnecessary events, IP anonymization, no forwarding of raw data
Purpose limitationUse data only for defined purposesServer-side filtering, no uncontrolled forwarding to third parties
TransparencyUsers know exactly what is collectedClear privacy policy, understandable consent banner without dark patterns
ConsentActive opt-in before any trackingConsent Management Platform (CMP) that sets denied as default

The goal is not “zero tracking”. The goal is: tracking that respects user rights and still enables data-driven business decisions. The user is in the foreground – not the data usage.

The three pillars of privacy-oriented tracking

1. Server-Side Tracking: Control over data flows

What it is: Instead of loading tracking pixels (like the Meta Pixel or GA4) directly in the user’s browser (Client-Side), all data runs through your own server. The server filters, anonymizes (e.g., IP addresses) and forwards only the necessary, cleaned data to the platforms.

Why it is often used:

  • Adblocker resistance: Studies on adblocker usage (e.g., PageFair/Statista) cite values around 30–40 % for desktop users in Germany. Server-side tracking bypasses these blocks because the request comes from your own domain (First-Party), not from google-analytics.com.
  • Cookie lifetime: Browsers like Safari (ITP) and Firefox (ETP) often limit third-party client-side cookies to 24 hours to 7 days. Server-side cookies on your own first-party domain can technically live longer, which improves data continuity.
  • Data control: In the server container, it can be decided which data goes to Google or Meta – not the user’s browser or an opaque script.

Typical architecture:

User → Website → Own Server (e.g., GTM Server-Side) → Google Analytics / Meta CAPI

Tools I know:

  • Google Tag Manager Server-Side: Free testing on Google Cloud, otherwise hosting costs.
  • Stape.io: Affordable, specialized hosting for GTM Server-Side (from approx. €20/month).
  • JENTIS: Enterprise solution with a strong focus on Privacy-by-Design.
  • Matomo (Self-Hosted): Open source, full data control, servers in the EU.
  • Effort: 4–8 hours initial setup + ongoing maintenance. Often oversized for small SME websites, but essential for e-commerce or data-sensitive areas.

What it is: Google Consent Mode v2 (mandatory since March 2024 for using Google Ads in the EU) allows sending anonymized “pings” (modeling signals) to Google even when consent is denied.

Assessment on practice (IP issue & Tag firing): Even if Consent Mode v2 only sends “pings” on denied consent, the user’s IP address can technically still be captured or transmitted before anonymization kicks in. According to a strict data protection interpretation, tracking tags are therefore often only executed with explicit, tool-specific consent.

The only technical exception: It can be ensured before the tag executes that the IP address is not accessible (e.g., through strict anonymization or pseudonymization directly in the server-side container, before the data is passed to the respective tool). As long as this technical guarantee does not exist, the rule in practice is often: No explicit consent = no tag firing.

How it works (with granted consent):

  • User agrees → ad_storage and analytics_storage are set to granted.
  • The tag fires and sends the data (ideally already cleaned by server-side logic).
  • Google uses this data for reporting and optimization.

Typical requirements:

  • A consent banner that correctly controls the Google-specific states (ad_storage, analytics_storage, ad_user_data, ad_personalization).
  • An implementation in Google Tag Manager or directly in GA4.

Possible first steps: The consent banner can be checked using the Google Consent Mode documentation. Are the states set to denied by default when the page loads, and only changed to granted upon clicking “Accept”? If not: adjust CMP configuration.

3. First-Party Data: Independence from third parties

What it is: Data collected directly and with explicit consent from the user – independent of Google, Meta, or other platforms.

Typical first-party data:

  • Newsletter subscribers (email, preferences)
  • Customer accounts (purchase history, support requests)
  • Own, privacy-first analytics solutions (e.g., self-hosted Matomo)

Why it is often recommended: Third-party cookies are blocked by browsers and regulated by laws. First-party data remains the only reliable basis for long-term marketing and attribution.

Possible first steps: An own newsletter can be built up. Tools like Brevo (GDPR-compliant servers in the EU) are quickly integrated. Every subscriber is a direct, platform-independent channel.

Typical pitfalls

Google Analytics, Meta Pixel or Hotjar standardly transfer data to the USA. Since the “Schrems II” ruling by the ECJ (2020), data transfer to third countries without an adequate level of protection (such as an adequacy decision or effective supplementary measures) is legally highly risky.

Alternatives I know:

  • Matomo (Self-Hosted): Open source, full data control, servers in the EU.

Important: EU alternatives also require a legal basis (usually consent under TTDSG if cookies are set, or legitimate interest for purely anonymized evaluation). “No US services” is not an automatic free pass. Legal assessment must always be done by a specialized attorney.

Many banners show “Accept all” prominently and in color, while “Reject” is small, gray, or hidden in a sub-menu. Supervisory authorities (and NGOs like NOYB) are increasingly taking action here with warnings and fines.

What a banner often needs to be legally safe:

  • Equivalent presentation: “Accept” and “Reject” are visually equivalent (same size, same contrast).
  • Granular selection: Users can toggle individual purposes (e.g., only “Statistics”, not “Marketing”) individually.
  • No prior consent: No pre-checked checkboxes.
  • Easy withdrawal: Consent can be withdrawn as easily as it was given (e.g., via a permanently visible icon at the edge of the page).

3. Tracking without an updated privacy policy

Every collected data category and every service is transparently listed in the privacy policy: What is collected? For what purpose? How long is it stored? Who is the data processor?

Possible first steps: The privacy policy can be opened. Are all currently used tools (including server-side containers or CMP providers) listed? If not: update immediately or consult a specialized generator (e.g., eRecht24) or a specialized attorney.

What does this actually achieve?

MeasureExpected impact (evidence)Time effort
Activate Consent Mode v2Up to ~30–60 % recovery of modeled conversions (Google manufacturer statement)1–2 hours
Server-Side Tracking setup+30–50 % higher data quality & bypassing adblockers (IAB Europe / Digital Applied)4–8 hours
Optimize consent bannerHigher, legally clean consent rate, avoidance of warnings (NOYB precedents)30 minutes
Build first-party dataLong-term independence from third-party cookie deprecation (Gartner)Ongoing

Total effort: 6–12 hours for the basics. The ROI is indirect, but massive: legal certainty, better data quality, and long-term independence from arbitrary platform changes.

When that is not enough

These basics are the beginning – not the end. If complex requirements exist (e.g., e-commerce with server-side purchase events, international markets with different consent rules, deep CRM integration), specialized expertise is often required.

For SME operators, the limit is often clear: The basics can be set up yourself. Everything beyond that – server-side tracking architectures, complex consent logic, dataLayer strategies – requires experience that you don’t acquire on the side.

If the technical complexity is overwhelming or the time to deal with server-side tracking and privacy policies is missing, the point is reached where a tracking consultant makes sense. Not as a replacement for your own understanding, but as an accelerator.

The Website Tracking Check for €690 shows where the current setup stands – with a prioritized roadmap and honest assessment. How support costs are composed is shown in the open calculation.

Orientation checklist

  • Consent banner checked (equivalent buttons, granular selection, no dark patterns)
  • Consent Mode v2 correctly implemented in GA4 and GTM (states are set to denied)
  • Server-Side Tracking evaluated (Is it necessary for the traffic volume and compliance requirements?)
  • Privacy policy updated (all tracking services, CMP, and server providers listed)
  • US services checked (privacy-first alternatives like Matomo evaluated)
  • First-party data strategy started (e.g., newsletter, own analytics)
  • IP anonymization activated in GA4 (active by default, but worth checking)
  • Data processing agreements (DPAs) concluded with all services
  • Regular audits planned (quarterly checks of consent banner and tracking setup)

Privacy-oriented tracking is not a contradiction. It is tracking with respect for user rights – and still data-driven enough for sound decisions.

Sources

  1. European Union: General Data Protection Regulation (GDPR), esp. Art. 6 (Lawfulness) and Art. 25 (Data protection by design and by default).
  2. Federal Republic of Germany: Telecommunications-Telemedia Data Protection Act (TTDSG), § 25 (Storage of information and access to end devices).
  3. European Court of Justice (ECJ): “Schrems II” ruling (C-311/18, 16.07.2020) on data transfer to third countries.
  4. Google: Consent Mode v2 Documentation & Best Practices (Official platform specification).
  5. IAB Europe / Digital Applied: Reports on server-side tracking adoption and data quality (industry benchmarks, +30–50 % data recovery).
  6. PageFair / Statista: Studies on adblocker usage in Germany (orientation value: ~30–40 % desktop usage).
  7. NOYB (None of Your Business): Precedents and complaints regarding “dark patterns” in consent banners (e.g., unequal button design).
  8. Gartner: Research on the strategic importance of first-party data in light of third-party cookie deprecation.
  9. Own infrastructure: mailcow self-hosted, fonts local (no CDN) (see Tech Stack).

Note: This article serves general technical and methodological assessment. It does not replace legal advice. For binding information, consult a specialized data protection attorney. Valorferrum assumes no liability for legal decisions based on this article.

Next step

Questions the article does not answer?

In the free intro call (15 min) we look together at what your project really needs – honest, no obligation, no sales pressure.

Free intro call To the services