Server-Side Google Tag Manager Will See Full IP Addresses From January 2027

Server-side Google Tag Manager (SGTM) will process visitors' full IP addresses starting January 11, 2027. Google confirmed the date in an official statement: "Starting January 11, 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 personalization."

This is a confirmed Google policy change, announced by email to advertisers. It replaces the current container-wide IP redaction model with per-tag processing. The email, posted on X by Govind Singh, states the shift plainly: "Server containers in Google Tag Manager will transition from container-wide IP address redaction to individual tag-level processing."

What changes on January 11, 2027?

Under the current model, SGTM can redact — remove or obscure — IP addresses across the entire server container. That single switch governs every tag inside the container. From January 11, 2027, control moves to the individual tag level, and behavior splits by tag type:

• Google Ads tags will be able to receive the visitor's full IP address.
• Google Ads, Display & Video 360, Search Ads 360 and Campaign Manager 360 tags will now accept the full IP address, per Google's email.
• Google Analytics tags will continue to apply IP redaction, unchanged.
• Third-party tags will maintain independent control over which network signals they accept; each provider decides.
• Transformations can still redact or remove these signals before any tag accesses the data.

Advertisers who want to keep IP addresses out of specific tags retain a technical path. Transformations sit ahead of tag execution, so redaction can survive the migration — but it will require configuration rather than a single container-wide default.

Does this force full IP collection?

No. Google framed the shift as a change in default data-handling behavior, not a requirement to send full IP addresses to every service. Tags gain the capability to process standard network signals; whether each one does depends on tag type and configuration.

The privacy stakes are real but bounded. An IP address counts as personal data under EU data-protection law in many circumstances. Receiving one, however, does not automatically identify a person by name. The announcement concerns what signals tags can process — it does not mean every visitor will be automatically and personally identified, a distinction that matters for GDPR assessments and consent flows.

Who does this affect?

The change targets advertisers running SGTM server containers with Google Ads and the broader buy-side stack — Display & Video 360, Search Ads 360 and Campaign Manager 360. For those accounts, the update should improve Ads measurement and personalization, since full IP signals can strengthen conversion modeling and audience matching. Google Analytics properties keep their existing redaction posture. Publishers and advertisers leaning heavily on third-party server-side tags face a per-vendor review: each provider now sets its own signal policy.

For EU-based operators, the January 2027 date doubles as a compliance deadline. Teams will need to decide whether transformations should redact IP addresses for every non-Google tag, and document those choices before the default flips.

What to monitor next

Watch Google's Tag Manager release notes and the SGTM preview interface for transformation templates tied to network signals between now and January 11, 2027. The X thread started by Govind Singh, which surfaced the advertiser email, is one place practitioners are already trading configuration screenshots — expect Google to publish migration guidance as the date approaches.