Google's IP-Based Ad Measurement Hits the EEA on 3 August. Your Consent Mode Setup Is on the Clock.
From 3 August 2026, Google will use IP addresses for ad measurement and personalisation across the EEA, UK, and Switzerland. IP addresses are classified as personal data under GDPR and UK GDPR, which means valid user consent is now a legal requirement before those signals can be used. If your Consent Mode implementation is incomplete or misconfigured, you risk serving personalised ads without a lawful basis. That is a compliance exposure, not a technical edge case.
What Changed
Google has always received IP addresses to route traffic and serve ads. That part is not new. What changes from August is the purpose: Google will now use those addresses to identify devices for measurement and personalisation, not just for technical delivery.
That shift in purpose is legally significant. Under GDPR and UK GDPR, using personal data for a new purpose requires either a fresh legal basis or explicit user consent. Google cannot rely on legitimate interest for ad personalisation in these regions, so consent becomes the only viable route.
To formalise this, Google is registering under the IAB Europe Transparency and Consent Framework, the industry-standard mechanism that ties consent signals to downstream ad technology vendors.
When It Takes Effect
The rollout date is on or shortly after 3 August 2026. Google has not published a phased schedule, so advertisers should treat the 3rd as a hard deadline rather than an estimated window.
The regions in scope are the EEA (all 30 member states), the United Kingdom, and Switzerland. If you run Google Ads campaigns targeting any of those territories, this applies to you regardless of where your business is incorporated.
How It Works, and Why Consent Mode Is Your Control Lever
Google's Consent Mode works by reading consent signals from your CMP (consent management platform) and adjusting how Google tags behave in response. When a user declines personalisation, the tag fires in a restricted mode, IP data is not used for personalisation, and modelled conversions fill the measurement gap instead of raw signals.
Without a correctly configured Consent Mode v2 implementation, Google's tags have no reliable way to distinguish consented from non-consented users. The practical result: IP-based personalisation may fire for everyone by default once August arrives, irrespective of what your cookie banner says.
The table below maps the consent states to the behaviour advertisers should expect after the change.
| User Consent State | IP Used for Personalisation | Conversion Measurement | Remarketing Eligible |
|---|---|---|---|
| Consent granted | Yes | Observed + modelled | Yes |
| Consent denied | No | Modelled only | No |
| No Consent Mode signal (misconfigured or absent) | Undefined, high compliance risk | Unreliable | Undefined |
What Growth and In-House Teams Should Do Before 3 August
Start with a Consent Mode v2 audit. Confirm that both ad_storage and ad_personalization parameters are firing correctly on every page where Google tags are present, and that your CMP is passing the right signals to Google Tag Manager or your direct tag implementation.
Check your CMP's vendor list. If Google is not listed as a vendor requiring consent under the IAB TCF, the framework signal will not reach Google's systems correctly, and the IAB registration Google is completing becomes irrelevant to your setup.
If you're also reviewing how consent and data quality affect your wider measurement picture, the piece on how Google Analytics unified paid and organic conversions in the Data API is worth reading alongside this one. De-duplicated, consent-compliant data is the foundation both changes require.
For teams using GA4 alongside Google Ads, Google's Ask Advisor feature in GA4 can help you interrogate consent-mode modelling gaps more quickly than manual reporting, particularly if you're trying to assess measurement loss before the deadline.
The Concrete Action
Run a tag audit this week. Confirm Consent Mode v2 is live and passing both parameters. Verify your CMP vendor list includes Google under the IAB TCF. Brief your legal or compliance team on the August date so sign-off does not become the bottleneck. You can read the full original report on the Google IP address ad personalisation change at PPC News Feed.
The deadline is fixed. The audit is not complicated. What will cost you is leaving it until August.
Tags