Google Ads Tags Get Full Visitor IPs in sGTM on Jan 11 Unless You Opt Out
Starting January 11, 2027, server-side Google Tag Manager will let Google Ads, Display & Video 360, Search Ads 360 and Campaign Manager 360 tags receive the full visitor IP address, according to a Google email reported by PPC Land. Google Analytics tags keep redacting IPs. Because the change is opt-out, any container nobody touches starts passing full IPs to four ad products by default.
The email reached Google Ads customers under the subject line "Updates to network signal processing in server-side tagging," and it surfaced publicly when Rotterdam-based freelancer Adriaan Dekker posted it on LinkedIn on November 2. As far as I can tell there's no matching Google blog post or release note yet. The email points to a Help Centre article for the opt-out but doesn't name it, and PPC Land couldn't find one either. So we're working from an email screenshot about a change that lands in about ten weeks. Not ideal.
Most of the early chatter I've seen is about match rates. Full IPs should help Google's ad tags with conversion matching, invalid traffic filtering and probably geo signals. Fine. I think that's the less interesting half of the story.
Container-wide redaction is going away, and that's the real change
Today, a server container can strip the IP for every tag in one move. That's a big part of why a lot of teams bought into server-side tagging in the first place: one chokepoint, one privacy setting, one sentence in the privacy policy that says "we don't share full IP addresses with ad platforms."
After January 11, Google says sGTM "will allow tags to process standard network signals like IP address" at the tag level. Google's four ad products "will now accept the full IP address." Analytics tags "will continue to apply IP redaction." And third-party tags like Meta, TikTok or LinkedIn "will maintain independent control over the signals that they accept," which, honestly, is a sentence that raises more questions than it answers. The email doesn't say whether their behavior changes at all.
Think of the old setup as a single bouncer at the front door checking everyone. The new setup moves the bouncers inside, one per room, and Google's four ad rooms come with a standing guest list.
On paper, Google gives you a way to keep the old behavior. The email says "transformations can redact these signals before any tag accesses the data." Transformations have existed since 2023 and let you allow, augment or exclude event parameters before tags read them. The catch, as PPC Land points out, is that Google's transformations documentation doesn't mention IP addresses anywhere. So nobody outside Google seems to know yet whether "exclude the IP" is a checkbox, a per-tag switch, or a rule you build yourself and hope covers every path.
The privacy policy you wrote in 2024 may now be wrong
This part surprised me a little. Plenty of agencies sold sGTM migrations partly on privacy grounds. If your documentation, DPA or cookie notice describes the container as IP-stripping, that description becomes inaccurate on January 11 unless someone acts. Nothing breaks. No error shows up in Tag Assistant. The policy just quietly stops matching what the server does.
Google's email puts the burden squarely on you: "proper end-user notices and legally required consents" must be "in place before data collection begins." In the EEA, advertisers must follow Google's EU user consent policy, which also covers the UK and Switzerland even though the email only mentions the EEA. Elsewhere, you're told to comply with local privacy laws and platform terms. Standard language, sure. But it's standard language attached to a default that moves more personal data.
And IPs count as personal data in Europe more often than marketers like to admit. The Court of Justice of the EU ruled in the 2016 Breyer case that dynamic IP addresses can be personal data for a website operator, even when the operator can't identify the person alone. Server-side tagging never got you out of that. Iubenda made the same point recently when it told marketers server-side tracking still needs consent.
The default direction is also worth noticing. When Google gave AdSense publishers full-IP sharing earlier this year, it shipped off by default. For ad tags in sGTM, it ships on. Same company, same signal, opposite defaults. Probably two product teams with different incentives. Still, it tells you which side of the ledger this one sits on.
The consent-denied gap nobody has answered
The bit I'd chase hardest is the consent side. Google's server-side consent mode documentation explains what Google Ads conversion, remarketing and Floodlight tags do with cookies when ad_storage is denied. Conversion tags, for instance, send a pixel to a cookieless domain. What the docs don't cover is IP handling for those denied pings.
That matters because PPC Land notes that since July 2025, Floodlight tags in sGTM send unconsented requests server-to-server to improve modeled conversions. Will those requests carry full IPs after January 11? The email doesn't say. If you run Campaign Manager 360 with EEA traffic, that's a question for your Google rep and your DPO this month, not in January.
I could be wrong and the answer might be "no, denied pings stay redacted." That would be the sensible design. I'd still want it in writing before I signed off on anything.
A 30-minute container audit before December 11
Give yourself a hard internal deadline of December 11, a month before the switch, because legal review always takes longer than the tag work. Per server container, this should take under 30 minutes:
- List every tag that will receive the IP. Filter the server container for Google Ads conversion, Google Ads remarketing, Floodlight (part of Campaign Manager 360), DV360 and SA360 tags. If the count is zero, you're mostly done.
- Find where redaction lives today. Is it a container-level setting, a GA4 tag option, or a custom transformation someone built? Write it down. Once redaction moves to tag level, a container-wide setting probably won't cover the ad tags anymore.
- Pull your privacy notice and your client DPA. Search for "IP." If either says IPs are truncated, anonymized or not shared with advertising partners, flag it.
- Make the decision explicitly. Either accept full-IP sharing and update the notice, or plan an exclude transformation and test it. Simo Ahava's transformations walkthrough is the clearest guide I know for the mechanics, and Tag Assistant's preview mode lets you compare original and transformed parameters.
- Check consent gating on third-party tags. Since Meta and TikTok tags "maintain independent control," confirm they're already blocked for consent-denied users. If they aren't, that's a separate problem you had before this email.
Benchmark for "done": every container has a named owner, a written decision (accept or redact), and a privacy notice that matches the decision. If you manage 10+ client containers, you're looking at a day of work. Annoying, but very doable.
This also stacks with other sGTM changes we've covered. Safari has been capping subdomain sGTM cookies at 7 days since 2023, and Google Ads is dropping its hashing requirement for uploaded data on November 16. If you're opening the container anyway, check all three.
Who actually opens their container before January
My guess: fewer than 1 in 5 sGTM containers get a documented decision before January 11. Most will just flip to full-IP by default because the email went to an ads inbox and the container belongs to an analytics contractor who left in March. Honestly, that's just how these things tend to go.
And to be fair, full IPs might genuinely help your Google Ads measurement. Better invalid traffic filtering is a real benefit, even if Google hasn't published numbers for it. Redacting everything by reflex would be its own mistake. My only ask is that whatever your container does after January 11 should be something a person chose, with a privacy notice that says the same thing.