All posts

Google sGTM Sends Full IPs to Ad Tags from Jan 2027

From January 11, 2027, Google's server-side GTM will send full visitor IP addresses to Google Ads, DV360, SA360, and CM360 tags by default. Container-wide IP redaction stops applying. Here is what agencies need to do before the cutover.

Jaya Muvania
8 min read
Google sGTM will send full IPs to ad tags from January 2027
On this page

Google will begin sending full visitor IP addresses to ad tags in server-side Google Tag Manager from January 11, 2027, the company notified container owners on November 2. The change moves four ad products (Google Ads, Display & Video 360, Search Ads 360, and Campaign Manager 360) from container-wide IP redaction to tag-level processing by default. Agencies running sGTM must audit their containers and configure explicit opt-outs before the cutover date or full IPs will begin flowing to all four ad products automatically.

Quick Answer: Google is switching server-side GTM containers so that Google ad tags receive full visitor IP addresses from January 11, 2027. Container-wide IP redaction will no longer apply to Google Ads, DV360, SA360, or Campaign Manager 360 tags. Google Analytics tags are exempt. Agencies must add tag-level opt-outs inside their sGTM containers before January 11 or accept the new default.

Google sent an email on November 2, 2026 to all server-side GTM container owners titled "Updates to network signal processing in server-side tagging." The email states: "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." The affected ad products are Google Ads, Display & Video 360 (DV360), Search Ads 360 (SA360), and Campaign Manager 360. Google Analytics 4 tags are explicitly excluded and continue to redact IP addresses. Third-party tags retain their own signal controls and are not affected by the change. The cutover is a single global date with no phased rollout and no regional exceptions. Agencies have until January 10, 2027 to implement opt-outs or the new behavior becomes the default for all containers globally.

What changed and why Google made the move

Until January 11, container-wide IP redaction in sGTM applied to all tags uniformly. An agency that enabled it could trust that no tag, Google or third-party, would receive the visitor's full IP address.

After January 11, that guarantee breaks for Google's four core ad products. If container-wide redaction is currently enabled, it stops applying to Google Ads, DV360, SA360, and Campaign Manager 360 tags. Those tags will receive the full IP unless the agency explicitly adds tag-level opt-outs for each one.

Google's stated reason is measurement and personalisation improvement. Full IP addresses allow more accurate geo-signal for bid adjustments, improved invalid click detection, and better cross-device attribution matching inside Google's own modeling systems. These are genuine measurement benefits; they are also the reason privacy-focused agencies moved to sGTM in the first place, using container-wide redaction to prevent exactly this.

The practical read: Google is pulling back an IP redaction guarantee that agencies relied on as a privacy control, and replacing it with a more granular but more labor-intensive model where each tag must be individually configured.

Which agencies are affected

Server-side GTM is used by larger agencies and in-house paid media teams as a privacy-safe measurement layer. Common configurations include:

  • Agencies running Google Ads conversion tracking through sGTM to strip third-party cookies and reduce client data exposure
  • Managed service accounts using DV360 or SA360 where container-wide redaction was part of client privacy agreements
  • E-commerce brands using Campaign Manager 360 for cross-channel attribution who told clients that sGTM anonymizes visitor IPs

Any of these configurations will behave differently after January 11 without manual intervention.

Agencies that set up sGTM primarily for first-party data collection, without enabling container-wide IP redaction, are less likely to notice a change in behavior, since those containers were already operating with tag-level defaults.

This change joins the 2026 paid media platform tracker alongside other measurement and platform shifts logged since January.

What agencies must do before January 11

Google's change is opt-out, not opt-in. The three steps:

Step 1: Audit every sGTM container. Identify all containers running Google Ads, DV360, SA360, or Campaign Manager 360 tags. If container-wide IP redaction is enabled, list which clients and campaigns those containers serve.

Step 2: Add tag-level opt-outs. Inside each container, navigate to each affected tag's settings and configure signal-level controls to prevent IP address processing. Google's documentation on transformations and signal controls covers the mechanism; the specific IP address transformation must be tested because Google's own documentation does not explicitly list IP as a removable signal at the tag level.

Step 3: Test before January 10. Google preview mode in sGTM lets agencies verify what signals each tag receives before the change goes live. Run a test on a staging environment, confirm the tag-level opt-out is working, and document the configuration for client audit records.

To opt out of the new Google sGTM IP address default before January 11, 2027, agencies need to configure tag-level signal controls inside each affected server-side GTM container, not the container-wide redaction setting, which will no longer cover Google ad tags. The four affected ad products are Google Ads, DV360 (Display & Video 360), SA360 (Search Ads 360), and Campaign Manager 360. Google Analytics 4 tags do not require action and will continue redacting IPs. Agencies should audit every sGTM container currently using container-wide IP redaction, identify which of the four ad products are present, add tag-level opt-outs, and verify the configuration using sGTM preview mode before January 10. Containers without IP redaction enabled are less likely to need changes. Agencies should document the configuration for client privacy compliance records.

How Hellyeah handles the measurement shift

Attribution accuracy is what Hellyeah's X-Ray is built for. X-Ray tracks conversion signal across channels independently of the signals any single platform receives, which means it is not dependent on Google's IP processing model to measure campaign performance.

Author's Comment

"The container-wide redaction setting gave agencies a single switch they could point to in client conversations: we run sGTM, so IP addresses are anonymized before they reach any tag. That sentence stops being true for Google ad products after January 11. The agencies that will be caught off-guard are the ones that set up their containers years ago and have not revisited the configuration since."
Jaya Muvania, SEO and Attribution Lead at Hellyeah AI

For Managed Growth clients, the January 11 change means Google's ad products will receive richer geo-signal for bid optimization, which is a performance input Hellyeah's AIMA engine already factors in when adjusting bidding strategy. The performance improvement from fuller IP-based geo-signals, where it materializes, flows into the signals AIMA uses.

The compliance question is separate from the performance question. X-Ray does not resolve a client's contractual obligation to update their privacy policy or sGTM tag configuration if their legal terms promised full IP redaction. That audit is agency and legal work that must happen independently.

Sources

PPC Land: Google ad tags gain full visitor IPs in server-side GTM in 2027 - first independent coverage of the Google email notification.

Google sGTM documentation: Signal controls for server-side tags - official signal processing reference.


FAQ Schema

Q: Does this change affect Google Analytics 4 tags in server-side GTM? A: No. Google Analytics 4 tags in sGTM are explicitly excluded from the January 11, 2027 change. GA4 tags will continue to redact IP addresses as before. Only Google Ads, Display & Video 360, Search Ads 360, and Campaign Manager 360 tags are affected by the new default behavior.

Q: What happens if an agency does nothing before January 11, 2027? A: If container-wide IP redaction is currently enabled and no tag-level opt-outs are added before January 11, the four affected Google ad tags (Google Ads, DV360, SA360, CM360) will automatically begin receiving full visitor IP addresses from that date. The container-wide redaction setting will no longer apply to those specific tags. Agencies with client privacy agreements referencing IP anonymization in sGTM must act before that date.

Q: Do third-party tags in server-side GTM need to be updated? A: No. Third-party tags in sGTM retain their own signal controls and are not affected by Google's January 11 change. Only the four Google-owned ad product tags are covered by the new default behavior.

Q: How many days do agencies have to make the sGTM changes before the deadline? A: Google announced the change on November 2, 2026, giving agencies approximately 70 days before the January 11, 2027 cutover. The recommended window to test opt-out configurations in sGTM preview mode is before January 10, leaving one buffer day before the change takes effect globally.

Q: Will this change improve Google Ads campaign performance? A: Google's stated rationale is improving measurement accuracy and personalisation, which includes more accurate geo-signal for bid adjustments and better cross-device attribution. Where those modeling improvements affect campaign performance, they would appear as incremental gains in Google's own optimization signals, not as a guaranteed percentage improvement, since actual impact depends on the proportion of sessions where full IP geo-data changes the bid model's behavior.

Jaya Muvania

SEO and growth

SEO and growth at Hellyeah. Writes about how AI changes the way people find and evaluate products.

Your next campaign, handled.

Hellyeah takes care of strategy, creative, and optimization.