<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.consentease.io/"/><title>Consent API on ConsentEase Status</title><link>https://status.consentease.io/affected/consent-api/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-08-07T00:00:00+00:00</lastBuildDate><updated>2026-08-07T00:00:00+00:00</updated><atom:link href="https://status.consentease.io/affected/consent-api/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] Google Signals Consolidation (June 2026)</title><link>https://status.consentease.io/issues/2026-08-07-google-signals-consolidation/</link><pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate><guid>https://status.consentease.io/issues/2026-08-07-google-signals-consolidation/</guid><category>2026-08-07</category><description>Google consolidated Consent Mode as the single authority for Ads data collection (effective June 15, 2026). Google Signals no longer controls ad_storage behavior.
ConsentEase status: Already compliant. All four Consent Mode v2 parameters (ad_storage, analytics_storage, ad_user_data, ad_personalization) were correctly implemented before this change took effect. No product changes required.</description><content type="html">&lt;p>Google consolidated Consent Mode as the single authority for Ads data collection (effective June 15, 2026). Google Signals no longer controls ad_storage behavior.&lt;/p>
&lt;p>&lt;strong>ConsentEase status:&lt;/strong> Already compliant. All four Consent Mode v2 parameters (ad_storage, analytics_storage, ad_user_data, ad_personalization) were correctly implemented before this change took effect. No product changes required.&lt;/p></content></item></channel></rss>