Google says ad tags in server-side Google Tag Manager will accept full IP addresses, while Analytics tags stay redacted, Search Engine Journal reported on November 3. The change affects how advertisers collect and route data through their own servers, and it draws a clear line between advertising measurement, where a full IP address has a defined use, and analytics, where redaction remains the default. For advertisers running server-side tagging, it is a configuration detail with privacy implications worth understanding.
Server-side Tag Manager moves tag execution from the visitor's browser to a server the advertiser controls. Instead of many third-party tags loading on a page, a single container sends data to the advertiser's server, which then forwards it to vendors such as Google Ads and Google Analytics. That gives the advertiser more control over what data leaves their infrastructure, reduces page weight, and makes it easier to enforce data rules in one place rather than across many browser tags.
The IP address question sits at the heart of that control. An IP address can identify a device's network location, and in some jurisdictions it counts as personal data. Google has redacted IP addresses in Analytics by default, and server-side Analytics tags continue that practice. Ad tags are treated differently, because advertising measurement, fraud prevention, and conversion attribution have historically used IP addresses as part of their signals. The November update makes that distinction explicit for server-side setups.
Under the change, ad tags in server-side Tag Manager will accept full IP addresses, while Analytics tags remain redacted. That does not mean every advertiser must send full IP addresses, and it does not mean Google will use them for purposes beyond the advertising products they support. It means the server-side container will no longer strip or redact the address for ad tags in the way it does for Analytics tags. Advertisers still control what their server sends, and they remain responsible for complying with privacy law and with their own policies.
The distinction is useful because it prevents a common confusion. An advertiser that sees a full IP address flowing to an ad tag might assume Analytics is also receiving it, or that redaction has been switched off everywhere. It has not. The two product families keep different defaults, and a server-side setup must be audited product by product. A single toggle does not describe the whole data flow, and anyone auditing a server-side container should check each tag's behaviour separately.
First, review your server-side container's tag configuration and confirm which tags receive a full IP address and which receive a redacted one. Second, check your privacy policy and consent setup: if you tell users that IP addresses are redacted, make sure that statement still matches what your ad tags actually send. Third, consider whether you need the full address at all. Many advertisers can achieve their measurement goals without it, and sending less personal data is usually the safer choice, even when sending more is permitted.
Fourth, remember jurisdiction. IP addresses are treated as personal data under laws such as the GDPR, and a change in what Google accepts does not change what a regulator expects. If you operate in the European Union or in a US state with a privacy law, the legal basis for sending a full IP address to an ad tag must be documented, and consent or another lawful basis must cover it. A platform feature is not a legal opinion, and it does not replace a privacy review.
The direct SEO impact is small, because this is an advertising measurement change, not a ranking change. The indirect relevance is in data quality and trust. Server-side tagging is increasingly how serious advertisers manage measurement, and a clean, well-documented server-side setup produces more reliable conversion data. That data, in turn, informs which pages, campaigns, and content deserve investment. A site that measures well can defend its marketing spend; a site that measures badly cannot, whatever its rankings say.
For link builders, the lesson is about the pages that conversions land on. If an advertiser changes its tagging and its conversion data shifts, landing page performance may appear to change even when the page has not. Before blaming a page, a link, or a campaign for a performance change, check whether a tagging change, such as this one, altered what was measured. Measurement changes masquerade as performance changes more often than most teams admit.
Sources: Search Engine Journal, November 3, 2026.
Linkbaits helps you create content that earns citations and backlinks. Start with the free tools and build your first linkable asset this week.
Start free trial