Cookie Consent Explained
When you need cookie consent banners and when you can legally skip them. A clear guide to the ePrivacy Directive and GDPR cookie requirements.
You need cookie consent for non-essential cookies that track users, store preferences not required for the service, or enable advertising.
You don't need consent for strictly necessary cookies required for your website to function. Analytics that stores nothing on the visitor's device, or that falls under a national audience-measurement exemption, may also be exempt. The rules cover localStorage as well as cookies.
Consent Requirements
- Google Analytics
- Facebook Pixel
- Advertising cookies
- Social media tracking
- Retargeting pixels
- User behavior tracking
- A/B testing with cookies
- Persistent login cookies (debated)
- Session cookies (shopping cart)
- Authentication cookies
- Language preference cookies
- Cookie consent choice storage
- Load balancing cookies
- Analytics that stores nothing on the device (or is covered by a national exemption)
- Security cookies
Understanding Cookie Laws
The ePrivacy Directive (Cookie Law)
The ePrivacy Directive (2002/58/EC, amended 2009) requires informed consent before storing or accessing information on a user's device. This includes cookies, localStorage, and similar technologies.
The key exception: you don't need consent for cookies that are "strictly necessary" for providing a service the user explicitly requested.
What "Strictly Necessary" Means
A cookie is strictly necessary when the website cannot function without it. Examples include:
- Shopping cart cookies (users can't check out without them)
- Authentication cookies (users can't stay logged in)
- Security cookies (CSRF protection)
- Load balancing cookies (site literally won't work)
Why Analytics Usually Requires Consent
Traditional analytics tools like Google Analytics set cookies to:
- Identify returning visitors
- Track user journeys across sessions
- Build visitor profiles
- Enable cross-site tracking
None of these are "strictly necessary" for your website to function. Users can browse your site perfectly fine without being tracked. Therefore, consent is required.
Where Privacy-First Analytics Fits
The ePrivacy Directive covers storing or reading anything on the visitor's device, not just cookies, so localStorage and similar technologies count too. Some regulators (for example France's CNIL) exempt narrowly scoped, first-party audience measurement; others don't.
Here's exactly what Invoker does, so you can assess it for your jurisdiction:
- In Privacy mode (the default), stores nothing on the visitor's device: no cookies, no localStorage, no fingerprinting
- Recognises a visitor for one day with a server-side hash of site, IP and user agent, keyed with a salt that is deleted every day
- No third-party cookies, no ads, no cross-site tracking
- Visitor IP addresses are never stored, and Do Not Track support is a per-site option
- Optional Enhanced mode stores a random, per-site visitor ID and a 30-minute session ID in localStorage, for returning visitors
Because no identifier is stored on or read from the device, Privacy mode is designed so you don't need a cookie banner for Invoker. Enhanced mode stores an ID, so treat it like a cookie: in the EU and UK, load the script only after consent. This isn't legal advice; see our cookie policy and privacy policy.
The Real-World Impact of Cookie Banners
Cookie consent banners aren't just a legal requirement—they hurt your business:
- 30-50% opt-out rate: Many users reject cookies, leaving gaps in your data
- User friction: Banners annoy users and hurt UX
- Bounce rate increase: Some users leave rather than deal with banners
- Implementation complexity: Proper consent management is technically challenging
- Ongoing compliance: Regulations change, requiring updates
Best Practices
To minimize cookie consent requirements:
- Audit your cookies: Know exactly what cookies your site sets
- Remove unnecessary tracking: Do you really need Facebook Pixel?
- Use privacy-first analytics: Switch to first-party tools with no third-party cookies or ad profiles
- Implement proper consent: If you must use cookies, do it right
- Document everything: Keep records of what you collect and why