Hamza JameelField sheet Nº 140

Free field sheet · Nº 140
Issued 4 Nov 2026

KeywordREDACT

Server-Side GTM IP Redaction Checklist

Checks
17
Do first
2
Parts
5
Cost
Free
Hamza Jameel
Prepared byHamza Jameel10+ yrs · $8M+ ad spend managed · 150+ page-one rankings
Checked 0/17Top

Google has told advertisers that from 11 January 2027, ad tags in server-side Google Tag Manager will accept visitors' full IP addresses, while Google Analytics tags keep redacting them. Search Engine Journal reported the notice on 3 November, after Google Ads specialist Adriaan Dekker shared it on LinkedIn. Use this checklist to decide what each tag should receive and, if you want the IP redacted, to build it before the date.

Part 1 of 50/5

What changes on 11 January 2027

  1. Google's notice is called 'Updates to network signal processing in server-side tagging'. It covers server containers, not the Google tag or web containers running in the browser.

  2. That includes Floodlight tags. If you do nothing, these tags get the full address from that date.

  3. Google's help page says Analytics server tags already apply partial IP redaction by default.

  4. The notice doesn't say whether their current redacted behaviour carries on, so check each one.

  5. The notice has no issue date, and as of 3 November the release notes didn't list this change. Google's help page doesn't mention the date either.

Part 2 of 50/3

Find out what you have

  1. Look for a container of type Server next to your web container. If you only use a web container, this notice doesn't cover it.

    Wheretagmanager.google.com › Accounts

  2. Note each Google Ads and Floodlight tag. You'll select them in the transformation below.

    Wheretagmanager.google.com › [Server container] › Tags

  3. Many read ip_override. Others read a custom header or event parameter. Check the vendor's documentation, or inspect the requests in Tag Assistant.

Part 3 of 50/2

Decide before you build

  1. Partially redacted means the last part of the address is zeroed: the last octet of an IPv4 address, the last 80 bits of an IPv6 address. Google says the full address improves campaign performance, but it gives no measurement data.

  2. Google says end-user notices and legally required consents must be in place before data collection begins. Its EU user consent policy covers the EEA, the UK and Switzerland, and other regions have their own rules. Ask whoever handles privacy for you.

Part 4 of 50/6

To redact: Google's method

  1. It returns the anonymized IP. The template needs the user_ip permission. Google's help page gives this code:

    Copy this
    const getAnonymizedIpAddress = require('getAnonymizedIpAddress');
    return getAnonymizedIpAddress();
  2. Set it to override the ip_override field and map that field to your IP variable.

    Wheretagmanager.google.com › [Server container] › Transformations › New

  3. Use Matching Conditions or Affected Tags. Google's examples are Google Ads, Floodlight and other non-Google tags.

  4. Override that vendor's field with the same IP variable, and limit it to that tag.

  5. Do this before 11 January 2027. Nothing changes on live traffic until you publish.

Part 5 of 50/1

After the date

  1. The notice doesn't explain how this works with consent mode or non-consenting Floodlight requests, so check what your tags really send.

Want me to look at yours?

If you have gone through this and want a second pair of eyes, book a free call. We open the account together and look at what is actually happening. No deck, no pitch.

More free sheets

Sources
  1. https://www.searchenginejournal.com/google-ad-tags-in-server-side-gtm-to-get-full-ip-addresses/595807/
  2. https://support.google.com/tagmanager/answer/18646937
  3. https://developers.google.com/tag-platform/tag-manager/server-side/api
  4. https://ppc.land/google-ad-tags-gain-full-visitor-ip-addresses-in-server-side-gtm-in-2027/