Google Will Use UK and EU IP Addresses for Ad Personalization on August 3, 2026. Here's What Advertisers Need to Do.

On August 3, 2026, Google starts using IP addresses for ad personalization across the UK, EU, and Switzerland. What's changing, who it affects, and the consent setup you need before the date.

Google Will Use UK and EU IP Addresses for Ad Personalization on August 3, 2026. Here's What Advertisers Need to Do.

On June 17, Google emailed advertisers that starting August 3, 2026, it will begin using user IP addresses for ad measurement and personalization across the European Economic Area (EEA), the United Kingdom, and Switzerland. IP data that Google has historically used only for network routing will now feed device identification for advertising.

If you run any paid media into those regions, this change matters. It triggers new consent obligations under UK GDPR and EU privacy laws, and the August 3 date is firm.

Here's the short version of what's changing, who it affects, and the work that needs to happen in your accounts before then.

What's actually changing

Until now, IP addresses on Google's ad surfaces in the EEA, UK, and Switzerland were treated as network plumbing. Google used them to route traffic, not to identify devices for advertising. That has been a meaningful distinction under EU and UK data protection law, because IPs that "personally identify a device" are personal data, and processing them for advertising triggers consent rules.

Starting August 3, 2026, Google will reclassify IP data as eligible for ad measurement and personalization. This applies across Google's advertising stack, including Search, Display, YouTube, Performance Max, and Demand Gen.

A few things to understand about the change:

The legal basis is consent, not legitimate interest. That means a user has to opt in through your consent management platform (CMP) for Google to use their IP for personalization. If consent is not granted, Google will continue to use the IP only for network routing.

Some personalization features will not arrive immediately. Google has indicated that additional capabilities will roll out later in 2026 and into 2027, at which point Google says it will also let users on its own properties make a choice about IP-based personalization.

This is a separate change from the Google Ads Consent Mode consolidation that took effect on June 15, 2026, although the two are connected through your ad_storage parameter and CMP setup. Consent Mode v2 is the mechanism that signals user consent to Google. The August 3 change is what Google does with the IP signal once consent is in place.

Who this affects

You should treat this as an action item if any of the following are true:

You run Google Ads campaigns that target the United Kingdom, an EU country, an EEA country, or Switzerland.

You run Google Ads in those regions through Performance Max, Demand Gen, or any campaign type that relies on Google's automated audience expansion.

You manage Google Analytics 4 properties that send data to Google Ads through linked accounts, and any portion of that traffic originates in the affected regions.

You publish content monetized through Google AdSense, Ad Manager, or AdMob that serves to users in the affected regions.

If your campaigns are 100% US-only and your GA4 properties do not receive UK or EU traffic, this change does not directly affect you. But almost any business with a website gets some incidental EEA or UK traffic, so it is worth confirming rather than assuming.

Why this matters: the legal trigger

Under the GDPR and the UK GDPR, IP addresses can qualify as personal data when they identify a specific device or user. The European Data Protection Board and the UK Information Commissioner's Office have both written extensively on this point.

By moving IP from network routing to ad personalization, Google is acknowledging that the new use case requires a stronger legal basis. Consent is the cleanest one. Legitimate interest, the basis some advertisers rely on for less invasive processing, does not apply here in Google's framing.

What this means in practice: if your CMP is not configured to capture and pass consent signals correctly to Google through Consent Mode v2, the August 3 change will not break your campaigns, but you will be processing data that you do not have a clear legal basis for. That is a regulatory risk, not a campaign performance risk.

What advertisers need to do before August 3

The audit list is short but specific. Work through it now rather than the week of August 3.

Confirm Consent Mode v2 is firing on every property that serves EEA, UK, or Swiss traffic. Open Google Tag Assistant or your tag testing tool of choice. Verify that consent_mode_v2 is initialized, that the default consent state is set correctly, and that consent updates fire when a user accepts or rejects through your CMP.

Verify ad_storage is the controlling signal. Since the June 15 consolidation, ad_storage is the single parameter that determines whether Google can use ad data. If you have legacy split-consent settings still in place, ad_storage may not be receiving the signal it should. Older sites built before mid-2024 are the most common offenders.

Confirm your CMP categorizes IP processing under advertising, not strictly necessary. Some CMPs default IP processing to the "strictly necessary" category because it is required for the page to load. That is fine for network routing, but is no longer accurate once the IP is being processed for ad personalization. Talk to your CMP vendor if you are not sure which category applies post-August 3.

Test the rejection path, not just the acceptance path. Most CMP audits check what happens when users click "Accept." Fewer check what happens when users click "Reject" or close the banner. Confirm that Google receives a denied ad_storage signal when a user refuses consent, and that no personalization data flows from that user's session.

Update your privacy policy. If your privacy policy does not currently mention IP-based ad personalization, the August 3 change is a reason to add a line. The policy should describe the categories of data processed for advertising, including IP, and reference the legal basis (consent).

Document the audit. Keep a record of when you tested, what you tested, and what you found. If a regulator ever asks, "what did you do to confirm compliance with the August 3 change," that record is the answer.

How this fits with everything else Google has shipped this year

The August 3 change is part of a broader 2026 pattern. Google has been collapsing fragmented consent controls into a single signal (Consent Mode v2 took effect June 15), extending data retention thresholds (37 months for granular reporting since June 1), and updating its Terms of Service to reflect AI processing of advertiser inputs (effective July 1).

The throughline: Google is consolidating the legal and technical machinery around advertiser data, and shifting more responsibility onto the advertiser to confirm consent and accurate setup. The platform-level defaults will move whether or not you opt in. The account-level configuration is where you have control.

For agencies and in-house teams managing multiple Google Ads accounts, the practical takeaway is that "set it and forget it" Consent Mode setups from 2024 or 2025 are now overdue for a refresh. The June 15 consolidation and the August 3 IP change both stress-test setups that were configured under the old rules.

A practical pre-August 3 checklist

If you run Google Ads with any UK or EU exposure, work through this list before the date:

The work is straightforward when Consent Mode v2 is already in good shape. Finding a problem in July is much cheaper than finding it in October after a regulator letter.

Frequently asked questions

Does this change apply to US advertisers?

Not directly. The change applies to user IPs from the EEA, UK, and Switzerland. If you run US-only campaigns and your GA4 only receives US traffic, the August 3 date does not require action on your part. That said, almost every website receives some EEA or UK traffic, so a quick check is worth doing.

Will my campaigns stop running on August 3 if I do nothing?

No. Campaigns will continue to serve. The risk is regulatory, not operational. Google will continue to use the IP for network routing without consent, but it will only use the IP for personalization where a user has consented through your CMP. If consent is missing across your traffic, you lose the personalization benefit but campaigns do not pause.

Does this affect Google Analytics 4 data?

Indirectly. GA4 already respects the consent signals you send through Consent Mode v2. The August 3 change is about how Google uses the IP signal once it reaches Google's advertising stack, not about what GA4 collects. But if your GA4 sends data to linked Google Ads accounts, the new processing rules apply downstream.

Is this related to fingerprinting?

It is in the same neighborhood. Google quietly removed its ban on fingerprinting for advertisers in December 2024, and the UK Information Commissioner's Office criticized that change at the time. The August 3 IP move is a more limited and explicit version of the same direction: IP data is now part of the device identification picture for ad personalization.

Where can I read Google's official notice?

Google has not published a public help center article as of June 19. The change was communicated to advertisers via email on June 17, with a follow-up expected in the Google Ads notification center. Watch for in-account banners and updates to the Consent Mode v2 documentation.

Bottom line

August 3 is six weeks out. The audit takes a few hours per account if your Consent Mode v2 is already in good shape, longer if it is not. If you have any UK or EU exposure on your accounts, this is a "do it in July" task, not an "I'll get to it in August" task.

The change itself is small in scope: Google is using an existing data point for a new purpose. But the legal and consent implications are not small, and the regulators in both the UK and the EU have shown they are paying attention to how IP is processed for advertising.

---

*Want a second set of eyes on your Consent Mode v2 setup before August 3? Book a call with us.*

Related articles