Frequently asked questions
Has Google finally removed third-party cookies from Chrome?
No. In July 2024, Google announced it would not remove third-party cookies from Chrome. Instead, Chrome introduces an interface allowing users to choose whether they want to be tracked across the web. Third-party cookies therefore remain available in Chrome, but other browsers (Firefox, Safari, Brave) block them by default. GDPR consent obligations apply in all cases.
Does Google's Topics API require GDPR consent?
Yes, according to European data protection authorities (including CNIL). The Topics API processes browsing data to generate interest categories, which constitutes personal data processing under GDPR. In practice, if you use Google Ads, this consent is captured via Google Consent Mode v2 — when the user rejects marketing cookies, rejection signals are transmitted to Google which disables the Topics API for that user.
What is the Protected Audience API (formerly FLEDGE)?
The Protected Audience API (formerly FLEDGE) is a Privacy Sandbox API enabling remarketing without exposing user data to third-party servers. Instead of storing your audience membership on an ad server, Chrome locally stores interest groups in the browser. When visiting a partner site, an auction runs locally in Chrome to select relevant advertising. GDPR consent is required for its activation.
My site uses Google Ads — do I absolutely need to implement Consent Mode v2?
Yes, if you target European users. Since March 2024, Google requires advertisers using Google Ads in Europe to implement Consent Mode v2 via a certified CMP. Without it, you lose conversion data, targeting becomes less precise, and your ROAS decreases. Additionally, technically you are not compliant with Google Ads terms of service. FlowConsent automatically implements Consent Mode v2 Advanced upon installation.
How to verify that Consent Mode v2 is correctly configured on my site?
Several methods: 1) Google Tag Assistant (Chrome extension): in Debug mode, verify consent_update events are sent with correct parameters (analytics_storage, ad_storage, etc.). 2) GA4 > Admin > Consent Overview: shows consent rate by signal. 3) Browser console: look for gtag('consent', 'update', {...}) calls in network logs. 4) Test by refusing all cookies and verify consent parameters switch to 'denied'. FlowConsent includes a built-in debug mode to facilitate these checks.