Google to activate IP-based ad personalization in Europe on August 3
Google will activate IP-based ad measurement and personalization in the EEA, UK, and Switzerland starting August 3, 2026, leveraging privacy-enhancing technologies like Trusted Execution Environments. To remain compliant, programmatic publishers must update their IAB Europe Transparency and Consent Framework disclosures to support Feature 3, or risk having their ad requests restricted or dropped.
Key Takeaways
- EEA, UK, and Switzerland publishers must update TCF disclosures to include Feature 3 for device identification by August 3.
- Data processing relies on non-cookie signals including on-device processing and secure multi-party computation (MPC).
- Google AdSense strings failing to correctly disclose Feature 3 risk restricted ad delivery or dropped requests.
- The rollout follows a June 1 launch of optional full IP address sharing for programmatic bid requests.
Why It Matters
This represents a strategic move to restore granular measurement and targeting signals in Europe's strict regulatory environment without relying on third-party cookies. By framing IP addresses as a data stream protected by hardware-level enclaves (TEEs), Google is attempting to bypass the measurement 'noise' that has plagued other Privacy Sandbox APIs. For the streaming and ad-tech ecosystem, this marks the operationalization of IP-based tracking as a primary B2B identifier, particularly critical for Connected TV (CTV) environments where cookies were never native. Success depends on whether European regulators accept TEE-based isolation as a sufficient privacy gate under GDPR. Watch for IAB Europe to report on Feature 3 adoption rates among mid-market publishers before the August deadline.
Additional Context
The August 2026 activation follows a period of intense regulatory and structural transition for Google's advertising business in Europe. In March 2026, the mandatory deadline for IAB Europe's Transparency and Consent Framework (TCF) v2.3 passed, requiring Consent Management Platforms (CMPs) to include a mandatory 'disclosedVendors' segment in TC strings. This version specifically aimed to resolve ambiguity regarding vendor disclosures, a direct response to Belgian Data Protection Authority rulings. Per IAB Europe in December 2025, any string generated after March 1, 2026, without this segment is considered invalid for ad processing.
Simultaneously, Google restructured its primary consent interface. On June 15, 2026, Google Analytics transitioned to using Consent Mode as the sole authority for advertising data flows, effectively stripping the 'Google Signals' toggle of its power to independently block data sharing. According to reporting from digital analysts in April 2026, this change consolidated disparate privacy settings under a single binary choice within Google Ads: granted or denied. This consolidation ensures that if a user grants consent, Google uses all available identifiers—including the encrypted IP addresses now being deployed—for cross-site tracking.
Regulators remain skeptical of this trajectory. The UK's Information Commissioner's Office (ICO) previously labeled Google's decision to permit IP-based fingerprinting as "irresponsible" in December 2024. More recently, on May 18, 2026, the ICO advised the UK government that tracking profiling users across services should remain strictly consent-based, appearing to draw a line against automated device identification. Meanwhile, in the U.S., a federal judge approved an RTB privacy settlement in March 2026, forcing Google to implement an 'RTB Control' that strips identifiers and obscures IP addresses for users who opt out, creating a divergence in how IP signals are handled across global jurisdictions.
Read full article at ppc.land
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source