How to Test If a Cookie Banner Actually Blocks Tracking
Updated · Technical information, not legal advice
Short answer
Open the site in a clean private window with DevTools on the Network tab, and check three moments: before any choice, right after clicking Reject, and after reloading. If requests to google-analytics.com/g/collect, facebook.com/tr or other trackers appear before consent or after Reject, the banner is not blocking tracking. EU regulators expect no non-essential trackers without consent, and refusing to be as easy as accepting.
Many sites have a cookie banner that looks correct but does nothing. Tags load on the first page view, or the Reject button closes the banner while the analytics and ad pixels keep running. For an agency, this is easy to miss and easy to test.
This guide explains what the rules expect in practice and gives you a repeatable manual test you can run with any browser. It is not legal advice. For a specific client situation, check with a lawyer.
What EU rules require in practice
Consent before non-essential storage or access
Article 5(3) of the ePrivacy Directive says that storing information on a user's device, or reading information already stored there, is only allowed with consent or when it is strictly necessary for specific purposes. Each Member State applies this through its own national law.
The rule is not limited to cookies. In its Guidelines 2/2023 (adopted on 7 October 2024), the EDPB explains that tracking pixels and tracking links also fall under Article 5(3). So "we don't set cookies" is not a complete answer if a pixel still sends identifiers.
Rejecting must be a real option
The EDPB Cookie Banner Taskforce report, adopted on 17 January 2023, records the shared positions of EU data protection authorities. Key points:
- A vast majority of authorities considered that a banner with no reject option on a layer that has an accept button is an infringement.
- Pre-ticked boxes do not produce valid consent.
- A "refuse" option hidden as a plain link inside a paragraph, without enough visual weight, does not produce valid consent.
- Withdrawing consent must be as easy as giving it.
- Legitimate interest cannot be the legal basis for placing or reading cookies under Article 5(3).
The French regulator CNIL lists "impossibility to refuse cookies as easily as to accept them" among the infringements it sanctioned between 2020 and 2022.
The three moments to test
A banner can fail at three different points. Test each one separately.
- Before any choice. The visitor lands on the page and ignores the banner. Nothing non-essential should load yet.
- After Reject. The visitor clicks Reject (or "Refuse all"). Nothing non-essential should fire as a result, and nothing should keep firing on the same page.
- After reload. The visitor reloads or opens another page. The refusal must be remembered, and trackers must stay off.
The third moment catches a common bug: the choice is stored, but tags are set to fire on page load before the consent tool has read the stored choice.
Manual method with browser DevTools
Setup
- Use a private or incognito window so there are no stored cookies or previous choices.
- Disable ad blockers and privacy extensions in that window. They hide the very requests you are looking for.
- Open DevTools (F12) before loading the site. Go to the Network tab and tick "Preserve log" so requests survive reloads.
Moment 1: before any choice
Load the page and do not touch the banner. In the Network filter box, try these one at a time:
collect: catches Google Analytics 4 hits. Google's own troubleshooting guide says to look for requests togoogle-analytics.com/g/collectoranalytics.google.com/g/collect. Click a request and open the Payload tab to see its parameters.facebook.com/tr: catches the Meta pixel. Meta's developer docs show the request format ashttps://www.facebook.com/tr?id={pixel-id}&ev={standard-event}, for exampleev=PageView.- Other common names:
doubleclick,googleadservices,hotjar,clarity,tiktok,linkedin.
Then open Application (Chrome) or Storage (Firefox), and check Cookies for the site. Look for analytics and ad cookies such as _ga, _gid or _fbp. Also check third-party domains listed there.
Moment 2: after Reject
Clear the Network log, click Reject, and wait a few seconds. Watch for new tracking requests. Scroll and click around a little, since some tags fire on interaction.
Check the cookie list again. Ad and analytics cookies that were already set before the click should not keep being read or refreshed.
Moment 3: after reload
Reload the page with the log preserved. Then visit one or two other pages. Any tracker request here means the refusal is not applied on later page views.
Reading Google Consent Mode signals
If the site uses Google Consent Mode, Google tags may still send requests after a refusal. Whether that is a problem depends on how it is set up.
Basic vs advanced mode
Google describes two implementations:
- Basic: Google tags are blocked until the user interacts with the banner. If the user does not consent, no data is sent to Google.
- Advanced: Google tags load when the page opens. While consent is denied, they send "measurements without cookies" (often called cookieless pings). Google says these can include a timestamp, user agent, referrer, consent state and a random number generated on each page load.
The gcs parameter
On a GA4 collect request, look for a gcs parameter in the Payload tab. Google does not explain this value in its consent mode guides, but consent tool vendors document a common reading: G1 followed by one digit for ad_storage and one for analytics_storage, where 1 means granted and 0 means denied.
G100: both deniedG101: analytics granted, ads deniedG111: both granted
Treat this as a debugging aid, not proof of compliance.
The grey area
Cookieless pings in advanced mode are debated. Google presents them as measurements without cookies. On the other side, the EDPB reads Article 5(3) broadly to include pixels and tracking links, not just cookies. If a client uses advanced mode, document that choice and get legal input on it. Basic mode is the more cautious option.
Common failure patterns
- Tags hard-coded outside the consent tool. A GA snippet or Meta pixel pasted into the theme header, a plugin, or a page builder setting. The banner never controls it.
- Google Tag Manager tags with no consent checks. GTM tags have Consent Settings. With "Require additional consent for tag to fire", the tag fires only if all listed consent types are granted. Tags left on "Not set" with an "All Pages" trigger will fire regardless.
- Reject only hides the banner. The click closes the banner but does not send a denied signal or block anything.
- Wrong category. Analytics or ad cookies labelled as "strictly necessary". The EDPB report flags this practice.
- Consent read too late. Tags fire on page load before the consent tool loads the stored choice, so moment 3 fails.
Enforcement examples
Fines in this area are real, and several cases match the failure patterns above. All are CNIL decisions in France.
- Google, December 2020. The CNIL fined Google LLC and Google Ireland a total of 100 million euros (decision of 7 December 2020). According to the Conseil d'Etat, which upheld it on 28 January 2022, seven cookies were installed automatically on arrival, four of them for advertising, and the refusal mechanism was defective.
- Google, Facebook and Amazon, 2020 to 2022. In its review of cookie sanctions from 2020 to 2022, the CNIL lists fines of 250 million euros in total for Google (including the 2020 decision above), 60 million for Facebook and 35 million for Amazon, with "impossibility to refuse cookies as easily as to accept them" among the breaches.
- SHEIN, September 2025. On 1 September 2025 the CNIL fined Infinite Styles Services Co. Limited (SHEIN's Irish subsidiary) 150 million euros. Advertising cookies were placed as soon as users arrived. After users clicked "Refuse all", new cookies were still placed and existing ones were still read.
- Google, September 2025. On 1 September 2025 the CNIL fined Google a total of 325 million euros, partly because consent to advertising cookies during Google account creation was not valid.
FAQ
Is a banner enough if it has Accept and Reject buttons?
No. The buttons must actually control what loads. You confirm that only by watching network requests and cookies.
Do I need to test every page?
Test the homepage plus one or two key templates, such as a product page and a checkout or form page. Different templates often load different tags.
Is GA4 with Consent Mode always compliant?
Not automatically. Basic mode blocks tags until consent. Advanced mode sends cookieless pings, which are debated. Get legal advice for the client's case.
What about server-side tagging?
Requests may go to the client's own domain instead of google-analytics.com, so filter by the client's tagging subdomain as well. The consent rules still apply.
FixComply's free cookie banner checker automates these three checks (before any choice, after Reject, after reload) and records which tracking requests fire at each step.
Sources
- EDPB, Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive (v2, adopted 7 October 2024)
- EDPB, Report of the work undertaken by the Cookie Banner Taskforce (adopted 17 January 2023)
- CNIL, Evolution of practices on the Web regarding cookies
- CNIL, Cookies placed without consent: SHEIN fined 150 million euros
- EDPB national news, French SA: Cookies and advertisements inserted between emails: GOOGLE fined 325 000 000 EUR
- Conseil d'Etat, Advertising cookies: Google fined 100 million euros
- Google, Consent mode overview
- Google, Verify and troubleshoot your Google Analytics setup
- Google Tag Manager Help, consent settings
- Meta for Developers, Meta Pixel advanced
- Secure Privacy, How to test Google Consent Mode is working
- Cloudflare, Zaraz Google Consent Mode (consent string format)
Check a site now, free
Run the same checks automatically: a real browser, evidence for every finding, no signup.
Open the free checker