Glossary
Cookie consent
Cookie consent is the permission a site asks for before storing or reading anything on a visitor's device that is not strictly necessary for the service they requested. In the European Union and the United Kingdom this requirement comes from the ePrivacy rules and applies to storage generally, not only to cookies. The failure that matters technically is simple and extremely common: the trackers load before the visitor has answered, which makes the banner decorative.
What is exempt and what is not
Strictly necessary storage is exempt: a session identifier for a logged-in user, the contents of a shopping basket, a load-balancing token, a record of the consent choice itself.
Analytics is not exempt under the rules as written, whatever the common practice. Some regulators accept narrowly configured first-party analytics; the position differs by country.
Advertising, cross-site tracking and personalisation are unambiguously not exempt.
The test is whether the storage is necessary for the service the visitor asked for, not whether it is useful to the site.
What a valid request looks like
Given before the storage happens. Consent obtained after a tracker has already loaded is not consent to that load.
Specific, with separate choices per purpose rather than a single all-or-nothing switch.
Freely given, which regulators have consistently read as requiring refusal to be as easy as acceptance — one click, at the same level of prominence.
Withdrawable, through a mechanism that remains reachable after the banner is gone.
Recorded, so that the site can show what was agreed and when.
The implementation failure that recurs
Scripts placed in the page load as the page loads. A banner rendered alongside them changes nothing about what has already run.
Tag managers configured to fire on page load rather than on a consent event have the same effect, and the configuration is outside the codebase where nobody reviews it.
Third-party embeds — a video player, a map, a social widget — set their own cookies the moment they are inserted, regardless of the banner.
The correct pattern is that non-essential scripts are not in the page at all until consent is recorded, and are injected afterwards.
This is directly observable: load the page, answer nothing, and list what has been stored.
How to check it
Open the page in a clean profile, dismiss nothing, and inspect the cookies and storage. Anything beyond strictly necessary entries is the finding.
Check the network panel for requests to tracking and advertising origins before any interaction.
Check that a refusal is available at the first level of the banner, and that refusing actually prevents the storage rather than only recording a preference.
Check that the choice persists and that a withdrawal mechanism is reachable from the page.
Frequently asked questions
- Does analytics require consent?
- Under the ePrivacy rules as written, yes. Some regulators accept narrowly configured first-party analytics as exempt, and the position differs by country.
- Must refusing be as easy as accepting?
- Regulators have consistently held that consent is not freely given when refusal takes more effort, so a refuse option at the first level is expected.
- Does the rule only cover cookies?
- No. It covers storing or reading information on a device, which includes local storage, session storage and similar mechanisms.
Sources
Related
VeriFixScan crawls a site and applies its checks to every page it reaches, keeping the evidence behind each finding. Scanning one website is free.
Scan a website