One of the most common questions — and misconceptions: "if I deploy server-side, can I drop the cookie banner?" Short answer: not the way most people think. Here's what server-side really changes about consent.
What server-side does NOT change
If you process personal data or store cookies that require consent, you need it regardless of whether you measure client-side or server-side. Moving to the server doesn't change the legal obligation to obtain consent. So a cookie banner (i.e. a consent management platform) is still needed.
What server-side does change
- First-party cookies instead of third-party. Identifiers are set by your server from your domain. That's cleaner for privacy, but doesn't remove the need for consent where it's required.
- One place for consent rules. What gets forwarded based on consent and what doesn't is handled centrally in the container.
- Less data leaves the browser. Instead of dozens of third-party domains, one request goes to yours.
What you can do without full consent
Even when a visitor declines, within the rules you can collect aggregated, anonymous data with no identifiers — and in Consent Mode v2 advanced mode, modeled conversions appear, a statistical estimate without tracking a specific person. That gives you a picture even without full consent — but it's not the same as "measuring normally without a banner".
Why you still need a CMP
The banner / consent management platform is what collects consent and passes it to measurement. The server-side container then respects that signal. Without a CMP you have no source for whether consent was given — and without it you couldn't enforce the rules. Server-side and a CMP complement each other; one doesn't replace the other.
Summary
Server-side tracking doesn't mean "measuring without a cookie banner". You need consent just the same; server-side only changes where data is processed and gives cleaner control. The banner stays part of the setup — server-side makes it a more effective tool, not a redundant one. Details in is server-side tracking legal and GDPR.