Yes, if your site sets or reads a tracker that is not essential for it to work, EU law requires a cookie banner. That covers most websites: standard analytics, an advertising pixel or an embedded YouTube video is enough. The obligation does not depend on the size of the business, its traffic, or whether the site sells anything.
Where does the obligation come from?
It comes from Article 5(3) of the ePrivacy Directive, which every EU country has written into its own law. Storing information on a visitor’s device, or reading it (setting a cookie, reading an identifier), is only allowed with their consent, unless the tracker is strictly necessary for the service they asked for.
The consent itself must meet the GDPR standard: freely given, specific, informed and unambiguous, given by a clear affirmative action. The European Data Protection Board (EDPB), which brings the EU’s data protection authorities together, has detailed these rules, and national regulators enforce them: the CNIL in France, the DPC in Ireland, the AEPD in Spain, the Garante in Italy. In the UK, the ICO applies near-identical rules under PECR.
The law speaks of information stored on or read from the device, not only of cookies: local storage, pixels and identifiers computed from the device (fingerprinting) are covered in the same way, as the EDPB confirmed in its 2023 guidelines.
Which trackers make a banner mandatory?
Any tracker that is not needed for the service the visitor asked for. In practice:
| Tool on your site | Consent required? |
|---|---|
| Google Analytics, Hotjar, most analytics tools | Yes, except in narrow configurations some regulators allow (see exempt cookies) |
| Meta Pixel, Google Ads, TikTok, LinkedIn | Yes |
| Embedded YouTube or Vimeo video | Yes, if it loads before the visitor clicks on it |
| Embedded Google Maps map | Yes, if it loads before the visitor uses it |
| Cart, login, security, chosen language | No |
| The cookie that remembers the banner choice | No |
When is a banner not needed?
If your site only uses exempt trackers, you do not have to ask for consent. Regulators list, among others: remembering the consent choice, authentication, the shopping cart, interface preferences the visitor chose (language, display), load balancing between servers. France’s CNIL also exempts some strictly configured audience measurement tools; not every regulator does.
The ePrivacy rules do not require you to tell visitors about exempt trackers, but regulators recommend it, usually in the cookie policy. If those trackers process personal data, the GDPR’s transparency rules apply anyway. The details are in our guide to cookies exempt from consent.
What must the banner do?
Having a banner is not enough. At Shein, American Express and Condé Nast, trackers fired before the visitor chose or after they rejected, and the CNIL fined them. Regulators look at seven points:
- Nothing fires before the choice. Trackers that need consent wait for a click on “Accept”. This is the first thing regulators check, and the most common failure.
- Rejecting is as easy as accepting. In the EDPB’s cookie banner taskforce, the vast majority of authorities considered a layer with an accept button but no reject option a breach. A “Reject all” button at the same level and with the same look as “Accept all” is the safe choice; a reject hidden behind “Settings”, or a washed-out button, is seen as deceptive.
- Visitors know what they are agreeing to: the purposes (analytics, advertising…), the companies that set trackers, and what their choice changes.
- Boxes are unticked by default in the settings panel.
- Withdrawing consent is as easy as giving it, for example through a “Manage cookies” link that is always available.
- The choice is remembered for a reasonable time, and so is a rejection: the CNIL considers six months generally appropriate, as explained in our guide on how long consent lasts.
- You can prove the consent you collected if asked.
What does a site without a banner risk?
A formal notice, then a fine, if a regulator receives a complaint or runs an audit. For large companies, fines have reached €325 million (Google, fined by the CNIL in September 2025). For small businesses, the CNIL mostly uses a simplified procedure, with fines capped at €20,000 in most cases: in 2025, 67 of its 83 sanctions went through it. We keep a dated table of the CNIL’s cookie fines.
An audit can start from a single complaint by a visitor or an association: a site does not need to be well known to be concerned.
How do you know whether your site needs one?
Look at what your site sets before any click. By hand, it takes three steps:
- Open your site in a private window, to start from scratch, without clicking anything.
- Open the browser’s developer tools, Application tab, then Cookies: everything listed was set without consent.
- Click “Reject all” if there is one, reload the page and look again.
Nodbar runs these tests for you: the scan opens your site like a first-time visitor, records every cookie and every request to a third-party service, then tests the “Reject all” button if there is one.