NEWS · NOVEMBER 3, 2026 · ADVERTISING

Google ad tags in server-side GTM will receive full IP addresses

Search Engine Journal reported on November 3, 2026, citing a Google notice to advertisers, that starting January 11, 2027 Google Tag Manager's server-side containers will allow Google's ad tags (Ads, DV360, SA360 and CM360) to take in complete visitor IPs. Analytics tags will keep masking them.

01 · WHAT HAPPENED

Google is changing how server containers handle IP addresses

Search Engine Journal (SEJ) reports that a Google notice to advertisers says server-side Google Tag Manager will, starting January 11, 2027, allow tags that send data to Google's ad products to accept the full IP address. Four products are named: Google Ads, Display & Video 360, Search Ads 360 and Campaign Manager 360. Google Analytics tags will continue to redact IP addresses.

The notice is titled "Updates to network signal processing in server-side tagging." In it, Google describes a shift for server containers: IP redaction will no longer apply across the whole container but will be handled tag by tag. It surfaced not as a public Google announcement but through a LinkedIn post by Google Ads specialist Adriaan Dekker on November 2. The notice carries no issue date, and SEJ notes that Tag Manager's release notes did not mention the change as of November 3.

02 · DETAILS

Four effects, a default, and a way out

As PPC Land quotes it, the notice says tags sending data to those four products "will now accept the full IP address." It lists three more points: third-party tags keep their own control over which signals they accept, Transformations can strip or mask those signals before a tag ever sees the data, and Analytics tags keep redacting. SEJ adds that the notice covers only server containers and is silent on the browser-based Google tag and web containers.

The change arrives switched on, and Google points to a Help Center article for opt-out instructions; PPC Land reports that the notice does not name the article, and SEJ says the screenshot shared does not show where the link points. Google's Tag Manager help page documents the current method: create a custom template variable that calls getAnonymizedIpAddress, then use an Augment event transformation to write a partially redacted IP into the ip_override field. The page advises testing in Preview before publishing. Some third-party tags read IPs from custom headers or event parameters instead of ip_override, so they may need a transformation of their own.

03 · WHY IT MATTERS

The default reverses a choice some server-side setups made

Server-side tagging lets a business's own server, rather than the browser, decide what each tag receives. PPC Land observes that a business which picked server-side tagging partly to limit the data flowing to Google's ad systems now faces a set date on which that setup changes. Google's stated rationale is that the update uses privacy-enhancing technologies plus spam and invalid-traffic filtering to improve campaign performance.

There is a legal side too. Google says advertisers need the right notices to end users and any legally required consents in place before any data is collected. Advertisers in the EEA must follow Google's EU user consent policy, which also reaches users in the United Kingdom and Switzerland. According to SEJ, the notice does not address how the change interacts with consent mode, or where and for how long full IP addresses are stored.

04 · TÜRKİYE

The sources say nothing about Türkiye, so this section is commentary

Neither SEJ, PPC Land nor Google's help pages mention Türkiye. What follows is therefore UNALSOFT commentary, not a finding from the sources. The sources give no information on how advertisers in Türkiye will be affected or whether any separate notice or exception applies there, and this article makes no such claim.

Our view: an IP address can count as personal data under many legal regimes, so this is legal preparation as much as a technical task. How Türkiye's data protection law (KVKK) applies is our own reasoning, not something in these sources. A business running server-side tagging should map, before January 11, 2027, which tag reads which IP field, and check with legal counsel whether its cookie and consent flow covers it.

The UNALSOFT view

For clients on server-side tagging, the first job is an inventory: which Google ad tags sit in which server container, which field each reads the IP from, and whether the consent flow covers it. Whether the IP goes out full or partially redacted is then written down as a deliberate decision and tested in Preview, so the default never takes effect silently. See how we approach this in ad management. For the wider shift in measurement tooling, see our piece on Google tag and Tag Manager merging.

How do your server-side tags handle IP addresses?

Let's review which tag reads which field, and what your consent flow covers, before January 11.

Message on WhatsApp