The General Data Protection Regulation continues to shape how websites collect and process user data across the European Union and beyond. Supervisory authorities are paying close attention to cookie banners, so getting cookie consent right is no longer optional: it is a business basic.
This guide covers what you need to know about cookie consent, from the legal requirements to practical implementation.
What GDPR Requires for Cookies
Under the GDPR and the ePrivacy Directive, websites must obtain informed, freely given consent before placing non-essential cookies on a user's device. This applies to any technology that stores or accesses information on the end user's device, including cookies, local storage, and tracking pixels (see EDPB Guidelines 2/2023 in the sources).
Who supervises cookies depends on the country. In Slovakia it is the Regulatory Authority for Electronic Communications and Postal Services, in the Czech Republic the Office for Personal Data Protection (ÚOOÚ). In most other member states the data protection authority does.
The key principles are straightforward:
- Prior consent is required before setting any non-essential cookies
- Necessary cookies (session management, security, load balancing) are exempt from consent requirements
- Consent must be informed: users need to know what they are agreeing to
- Consent must be freely given: pre-ticked boxes and cookie walls do not produce valid consent
- Withdrawal must be as easy as giving consent: users must be able to change their preferences at any time
Understanding Cookie Categories
Most consent management platforms organize cookies into standardized categories. Understanding these categories is essential for proper implementation.
Strictly Necessary Cookies
These cookies are essential for the website to function. They include session identifiers, authentication tokens, shopping cart data, and security cookies. These do not require consent but should still be disclosed in your cookie policy.
Analytics Cookies
Analytics cookies collect data about how visitors use your website: page views, session duration, traffic sources, and similar metrics. These require consent before being set, even when the data is anonymized or aggregated.
Marketing and Advertising Cookies
These cookies track users across websites to build profiles and deliver targeted advertising. They include retargeting pixels, conversion tracking, and social media integration cookies. These require consent and are subject to the strictest scrutiny from regulators.
Functional or Preference Cookies
Cookies that remember user preferences like language settings, display preferences, or region selection. While these improve user experience, they still require consent if they are not strictly necessary for the service requested by the user.
What Makes Consent Valid
The GDPR sets a high bar for valid consent. The EDPB explains the requirements in its Guidelines 05/2020:
Informed: Before giving consent, users must be told who is collecting their data, what cookies are being set, their purpose, and how long they persist. This information must be presented in clear, plain language.
Freely given: Consent cannot be bundled with acceptance of terms of service. Cookie walls that block access to content unless all cookies are accepted generally do not produce freely given consent. Users must have a genuine choice.
Specific: Consent must be granular. Users should be able to accept analytics cookies while rejecting marketing cookies. A single "accept all" option without alternatives is not enough.
Unambiguous: Consent requires a clear affirmative action. Scrolling, continuing to browse, or pre-checked checkboxes do not constitute valid consent. The user must actively click or toggle to indicate agreement.
Documented: You must be able to demonstrate that consent was obtained. This means storing consent records with timestamps, the version of the consent text shown, and the specific choices the user made.
Common Consent Mistakes to Avoid
Even well-intentioned implementations frequently fall short. Here are the most common issues:
Loading tracking scripts before consent. If your analytics or advertising tags fire on page load before the visitor has made a choice, your setup does not follow the prior-consent rule. Scripts must be held back until the user makes an active choice.
Making "reject" harder than "accept." If your banner has a prominent "Accept All" button but requires users to navigate through settings menus to reject cookies, regulators treat this as a problem. The EDPB cookie banner taskforce report addresses exactly this. Both options should be equally accessible.
Ignoring consent signals on subsequent pages. Consent applies to the entire browsing session and future visits. Your implementation must check stored consent preferences on every page load and respect those choices consistently.
Not providing a way to withdraw consent. Users must be able to change their cookie preferences at any time, typically through a persistent link in the footer or a floating widget. This mechanism must actually work: changing preferences should immediately stop non-consented tracking.
Vague cookie descriptions. Listing cookies as "used to improve your experience" without explaining what data is collected and by whom does not satisfy the informed consent requirement.
Cookie Banner Best Practices
An effective consent banner balances clear rules with user experience. Here is what works in practice:
Layer your information. The first layer should be a concise banner with clear accept/reject options and a link to detailed cookie settings. The second layer provides granular controls by category. A third layer (your cookie policy) gives complete technical details.
Use plain language. Avoid legal jargon. Instead of "We process personal data using tracking technologies pursuant to Article 6(1)(a) GDPR," try "We use cookies to understand how you use our site and to show relevant ads. You can choose which types to allow."
Respect the user's choice immediately. When a user clicks "reject" or customizes their preferences, the change should take effect instantly. Do not set cookies first and remove them later.
Test across devices. Your consent mechanism must work on mobile, tablet, and desktop. A banner that obscures the entire screen on mobile or has tiny touch targets is a usability problem and a consent-quality problem.
Keep records. Store a consent log that includes the timestamp, user identifier (anonymized), the version of your consent text, and the specific choices made. This is your proof of consent if a regulator asks.
How Supervisory Authorities Approach Cookie Banners
The EDPB summarized the common position of European supervisory authorities in its cookie banner taskforce report (18 January 2023). Several points are worth noting:
Reject as easy as accept. A missing or hidden reject option on the first layer of the banner is treated as a shortcoming.
Coordinated approach. The taskforce exists so that authorities in different member states read the rules consistently. Consistency across all your European domains matters.
Scrutiny of consent management platforms. Regulators are not just looking at whether you have a banner: they look at whether non-essential scripts really wait for the visitor's choice and whether cookies are categorized correctly.
Focus on misleading design. Deceptive designs in consent interfaces, such as colour or size that steers the visitor towards "accept", are a recurring theme in the authorities' positions.
Implementation Checklist
Use this checklist to audit your current cookie consent setup:
- All non-essential cookies are held back until consent is obtained
- The consent banner offers clear accept and reject options at the same level
- Cookie categories are accurately described with specific purposes
- Granular consent controls allow per-category choices
- Consent preferences are stored and respected across sessions
- A mechanism to withdraw consent is always accessible
- Consent records include timestamps and the specific choices made
- The banner functions correctly on all device types
- Third-party scripts respect consent signals via Consent Mode or equivalent
- Your cookie policy is up to date and matches your actual cookie usage
Getting Started with Conseto
Conseto helps you set cookie consent up properly from day one: a banner with reject on the first screen, Consent Mode v2 and a record of every decision. Conseto holds its own measurement, the Meta pixel, GA4 and GTM until consent; it does not block other third-party scripts, those stay with you. The free check shows what your site stores before consent. It is a technical check, not legal advice. Try Conseto free at conseto.io.
Sources
- EDPB, Guidelines 05/2020 on consent under Regulation 2016/679
- EDPB, Report of the work undertaken by the Cookie Banner Taskforce (18 January 2023)
- EDPB, Guidelines 2/2023 on the technical scope of Art. 5(3) of the ePrivacy Directive
- Slovakia: Act No. 452/2021 Coll. on electronic communications, text in force from 1 March 2026, and the Regulatory Authority's statement on obtaining consent (12 November 2025)
- Czech Republic: ÚOOÚ order ref. UOOU-02482/22-9 on cookies without consent