Google emailed the owners of server-side Google Tag Manager containers an undated heads-up: starting January 11, 2027, tags inside those containers will begin receiving the full IP address of every visitor by default. The email, titled “Updates to network signal processing in server-side tagging,” was first reported publicly on November 2, 2026 by Google Ads freelancer Adriaan Dekker, then picked up independently by Search Engine Journal, PPC Land, and Search Engine Roundtable, all citing the identical line from Google: “Starting on 11 January 2027, server-side Google Tag Manager (sGTM) will allow tags to process standard network signals like IP address to facilitate improvements to ads measurement and personalisation.”
If your account runs server-side tracking for Google Ads, that single sentence changes what kind of data leaves your server. Here is what shifts on that date, what Google says is your responsibility and not theirs, and what to check before the switch flips.

From Container-Wide Redaction to Tag-by-Tag Decisions
A server-side GTM container currently applies IP redaction uniformly: whatever rule the container sets, every tag inside it follows. From January 11, 2027, that uniformity goes away. Processing moves from the container level to the individual tag level, which means each tag now decides on its own what to do with the IP address it receives.
Google names the tags affected explicitly. Tags sending data to Google Ads, Display & Video 360, Search Ads 360, and Campaign Manager 360 will accept the full IP address by default. Google Analytics tags are the exception: they keep applying partial redaction automatically, confirmed on Google’s own Tag Manager Help page for IP address redaction in server-side tagging. Third-party tags vary. Some read the IP from the standard ip_override field and follow whatever your container sets; others pull the signal from a custom header or event parameter you would need to check vendor by vendor.
Nothing here requires you to do anything for the change to take effect. It is a change of default, not an optional upgrade: unless you configure your container otherwise, every Ads, DV360, SA360, and CM360 tag will start receiving full IPs on its own.
A Full IP Address Is Not a Technical Footnote
The Court of Justice of the European Union settled the legal status of IP addresses a decade ago. In its October 19, 2016 ruling in Breyer v. Bundesrepublik Deutschland (Case C-582/14), the Court held that a dynamic IP address counts as personal data for a website operator whenever that operator has a reasonable legal means of asking a third party for the additional information needed to identify the visitor. The distinction between static and dynamic addresses carries no legal weight afterward: what matters is whether identification is realistically possible, not whether the address happens to be fixed.
Under partial redaction, the last octet of an IPv4 address or the last 80 bits of an IPv6 address gets zeroed out before any tag sees it, which is generally enough to put the signal outside the scope of directly identifying data. Full IP processing removes that buffer. For any EU, UK, or Swiss advertiser, that is the difference between a signal your consent banner probably already covers and one that needs a specific legal basis spelled out.
Google’s own email does not leave this ambiguous. It states plainly that advertisers using Google’s advertising products must make sure proper end-user notices and legally required consents are in place before data collection begins, and that European Economic Area customers specifically must follow Google’s EU User Consent Policy. The obligation sits with the advertiser account, not with Google.
What to Check Before January 11, 2027
The checklist is short, but each item has a real consequence if skipped.
- Inventory your server-side containers. List every sGTM container in use and every tag inside it that sends data to Google Ads, DV360, SA360, or CM360. A container you forgot about is still subject to the default change.
- Check your consent banner’s actual scope. Confirm the consent categories your banner collects cover network signal processing for ads measurement, not just cookies, and that the wording matches what those tags will now do.
- Confirm the EEA/UK/Swiss consent policy is applied correctly if any portion of your traffic originates there, since Google points to its EU User Consent Policy by name in the announcement.
- Decide, tag by tag, whether full IP processing is acceptable for your account, rather than assuming the same answer applies to every destination.
Accounts already auditing their setup for AI-driven defaults elsewhere in Google Ads and Meta Ads will recognize the pattern: a platform ships a new default, and the compliance work of reviewing it falls on the account that uses it.
If You Want to Keep Anonymizing, Set Up a Transformation

Google documents a voluntary path back to anonymization, and it lives inside the Transformations feature of server-side GTM, applied per tag rather than for the whole container. The setup has two parts. First, create a Custom Template Variable whose code calls the built-in getAnonymizedIpAddress function. Second, add an “Augment event” transformation that overrides the ip_override field with that variable, scoped to the specific tags you want redacted.
The function itself is narrow in what it does: it zeroes the last octet of an IPv4 address (203.0.113.25 becomes 203.0.113.0) and the last 80 bits of an IPv6 address. That is the same masking Google Analytics already applies automatically, now available to Ads, DV360, SA360, and CM360 tags as an opt-in rather than a default. It is worth testing this against your own conversion tracking setup, the same way you would verify conversion data quality after any tagging change, since a misapplied transformation silently degrades signal rather than throwing an error.
FAQ
Does this change apply if I do not use server-side tagging?
No. The change is specific to server-side Google Tag Manager containers. A standard web (client-side) GTM container is not affected by this particular update.
Will Google Analytics tags start receiving full IP addresses too?
No. Google’s own documentation confirms Google Analytics server tags keep applying partial IP redaction automatically. The default change applies to Google Ads, Display & Video 360, Search Ads 360, and Campaign Manager 360 tags.
What happens if I do nothing before January 11, 2027?
Every affected tag in your server-side containers will start processing the full IP address by default, with no change to your consent setup unless you make one yourself. The compliance gap, if there is one, opens automatically on that date.
Can I apply redaction to only some tags and not others?
Yes. Because processing now happens at the tag level, an Augment event transformation can be scoped to specific tags, letting you keep full IP processing for one destination while re-anonymizing for another.
Before the Default Flips
Nothing about January 11, 2027 is hidden or contested: Google named the date, named the tags, and named the consent policy that applies. The only open variable is whether your account reviewed its own setup before the switch happened on its own. For a B2B account running server-side tracking, that review is a short one, container inventory, consent banner wording, and a transformation if you want it, done once rather than discovered after the fact.
If this pushes you to recheck how your account handles signals you assumed were already redacted, write to us. We’re curious what else turns up.
Sources: Google Tag Manager Help, IP address redaction for server-side tagging; PPC Land, “Google ad tags gain full visitor IP addresses in server-side GTM in 2027”; Court of Justice of the European Union, Press Release No 112/16, Breyer v. Bundesrepublik Deutschland.
Photo credit: Pixabay.







