r/GoogleTagManager • u/iubenda_team • 5h ago
Discussion Moving to server-side tagging doesn't remove the consent requirement. Two reasons, and most people only know one
This comes up as "we went server-side so we're first-party now, consent isn't our problem." But there are two things to consider, and usually only the first gets attention.
You're still writing to the device. Nearly every sGTM setup still sets a first-party cookie, whether the browser writes it or your own endpoint sets it on a first-party subdomain. ePrivacy 5(3) covers storing information on a device regardless of whether that information is personal data or whose domain it sits on. So going first-party changes the vendor relationship, but it doesn't change the storage question.
And even if you genuinely store nothing, the IP and behavioral data arriving at your endpoint are still personal data, so you still need a lawful basis. In that case, 5(3) may no longer apply, but the GDPR still does.
None of this means going server-side is a bad idea. You get better resilience against ad blockers, more control over cookie lifetimes and what gets sent to each vendor, and the chance to minimize payloads before forwarding them. Those are real benefits, just not a way around consent requirements.
In your setup, does the consent state actually reach the server container, or does the web container just forward everything without the server making any consent-based decisions?
(We're iubenda, and we work on consent tooling, so that's the angle we're coming from.)