Nice To E-Meet You!



    What marketing services do you need for your project?

    Server-Side Tracking And GDPR: What You Need To Know In 2027

    Last updated: November 19, 2026

    Server-side tracking can be GDPR compliant, but it is not compliant by default. Moving tags from the browser to your own server changes where data is processed, not whether you need consent. You still need a lawful basis, usually consent for marketing and analytics cookies, plus data processing agreements, sensible hosting and clear rules about what each vendor receives. Done properly, server-side tagging actually makes GDPR easier, because it gives you one place to filter, hash or drop personal data before it leaves your control.

    This guide explains how server-side tracking interacts with GDPR and the ePrivacy rules, where businesses go wrong and what a compliant setup looks like in 2027. It is not legal advice, so check your final setup with your data protection officer or lawyer.

    What Server-Side Tracking Changes

    In a traditional client-side setup, the visitor’s browser loads scripts from Google, Meta, TikTok and others. Each script sets its own cookies and sends data directly to its vendor, often including the IP address, user agent and page URL. You have little control over what is collected once the script runs.

    In a server-side setup, the browser sends events to a server on your own subdomain, such as a Google Tag Manager server container. That server receives the data first, applies your rules and then forwards a cleaned version to each vendor through its API. The vendor never runs code in the visitor’s browser.

    From a GDPR point of view, three things improve. You can remove or truncate IP addresses and other identifiers before forwarding. You can decide, vendor by vendor, which fields are sent. And you can keep processing inside the EU by choosing EU hosting for your server. What does not change is the need for consent to set or read non-essential cookies and to use data for advertising.

    Consent Still Applies

    The ePrivacy Directive, implemented in national laws such as the Dutch Telecommunicatiewet and Germany’s TDDDG, requires consent before storing or reading information on a user’s device unless it is strictly necessary. Analytics and advertising cookies are not strictly necessary in most countries, so consent is needed whether the cookie is set by a vendor’s script or by your own server.

    Setting a first-party cookie from your own server does not make it essential. Regulators look at the purpose of the cookie, not who sets it. If the cookie identifies a visitor for analytics or ads, it needs consent.

    GDPR then applies to any personal data you process. Under GDPR, pseudonymous identifiers such as client IDs, hashed emails and IP addresses are still personal data. Your server-side setup therefore needs a lawful basis for each purpose, which for marketing will almost always be consent captured by your consent management platform.

    In practice, this means your consent banner must work with your server container. The consent state captured in the browser should travel with every event, and the server should forward data to a vendor only if the visitor agreed to that purpose. Google Consent Mode v2 handles this for Google tags, and well-built server setups apply equivalent rules to Meta, TikTok and others. Our list of the best Google Consent Mode v2 CMPs covers tools that do this well.

    Where Businesses Get It Wrong

    Using server-side tracking to bypass consent

    Some vendors and agencies have marketed server-side tracking as a way to track people who decline cookies or use ad blockers. Recovering data lost to ad blockers from people who did consent is legitimate. Tracking people who refused consent is not, and data protection authorities treat it as unlawful processing however it is technically done. If a proposal promises to track everyone regardless of consent, reject it.

    Hosting in the wrong place

    If your server container runs in a US region, or on a host that processes data outside the EU, you are transferring personal data internationally. The EU-US Data Privacy Framework currently allows transfers to certified US companies, but many organisations prefer EU regions to remove the risk. Google Cloud, AWS and managed hosts such as Stape, Addingwell and TAGGRS all offer EU hosting.

    Forwarding everything

    The default templates for many server-side tags forward the full event, including IP address and user agent. Review each tag and remove fields the vendor does not need. For Meta’s Conversion API, send hashed email or phone only when the visitor consented to marketing and you have told them in your privacy notice.

    Forgetting the paperwork

    Your hosting provider and every vendor you forward data to are processors or joint controllers. You need data processing agreements, a record of processing activities that describes the server setup and a privacy notice that explains it in plain language.

    What A Compliant Server-Side Setup Looks Like

    A compliant setup in 2027 usually has these parts:

    • A consent management platform that records choices, supports Google Consent Mode v2 and exposes consent states to your tag manager.
    • A web container that sends events to your own subdomain only after defaults are set, and attaches the consent state to every event.
    • A server container hosted in an EU region, with each vendor tag set to fire only when the matching consent is present.
    • Transformations that remove or truncate IP addresses, drop unneeded parameters and hash identifiers before forwarding.
    • Data processing agreements with your host and vendors, and an updated privacy notice and record of processing.
    • Monitoring, so you notice when a template update starts sending fields you had removed.

    Some companies go further and use cookieless measurement for visitors who decline consent, such as aggregated, non-identifying counts. Whether that is allowed depends on the country and the exact method, so take advice before relying on it.

    Does Server-Side Tracking Help With Data Minimisation?

    Yes, and this is its biggest privacy benefit. GDPR requires you to collect only the personal data you need. In a browser setup, each vendor’s script decides what it collects. In a server setup, you decide. You can send GA4 an event without the full IP address, send Google Ads only the conversion value and click identifier, and keep customer details out of tools that do not need them.

    Server-side tagging also reduces the number of third parties that can see your visitors at all. Fewer scripts in the browser means fewer vendors able to read page content, form fields or other cookies, which lowers the risk of accidental data leaks through badly configured pixels.

    The UK, Switzerland and Beyond

    The UK applies its own version of GDPR and the Privacy and Electronic Communications Regulations, which also require consent for non-essential cookies. The rules for server-side tracking are therefore much the same as in the EU, although the UK has signalled a lighter approach to some low-risk analytics cookies, so watch for changes. Switzerland’s revised Federal Act on Data Protection is close to GDPR in spirit. In the United States, state laws such as California’s focus more on opt-outs and the sale or sharing of data, so a server setup there must honour signals such as Global Privacy Control. If you operate in several regions, configure consent defaults by region rather than applying one rule everywhere.

    Choosing Partners and Tools

    If you build the setup yourself, compare hosting providers in our list of the best server-side tracking tools, paying attention to EU hosting and data processing terms. If you want a team to own it, our list of top server-side tracking agencies includes several European specialists who design consent into the build from the start.

    How We Researched This Guide

    We reviewed guidance from European data protection authorities, Google’s documentation for server-side tagging and Consent Mode, and the published material of server-side hosting providers and consent management platforms. We focused on practical points that affect real implementations. Read how we research and rank for more about our process.

    Frequently Asked Questions

    Does server-side tracking remove the need for a cookie banner?

    No. If you set or read cookies for analytics or advertising, you still need consent in the EU and UK, whether the cookie is set by a vendor script or by your own server.

    Is first-party data collected server-side still personal data?

    Yes. Client IDs, IP addresses, hashed emails and similar identifiers are personal data under GDPR when they can be linked to a person, even if they are pseudonymised.

    Can I use server-side tracking to recover data from ad blockers?

    You can recover events from visitors who gave consent but whose browsers blocked vendor scripts. You should not track visitors who refused consent.

    Where should I host my server container for GDPR?

    An EU region is the safest choice. Google Cloud, AWS and managed hosts such as Stape and Addingwell all offer EU hosting options.

    Conclusion

    Server-side tracking and GDPR work well together when consent is respected and the server is used to minimise data rather than collect more of it. Keep your consent platform at the centre, host in the EU, strip what vendors do not need and document everything. Do that, and server-side tagging gives you better data quality and a stronger privacy position at the same time.

      Once a week you will get the latest articles delivered right to your inbox