Cookie banners and GDPR on your website: what is required in 2026?
Almost every website pops up a cookie window, and most of them work badly: you can only accept, or rejecting is hidden behind “Settings”. This article sums up when you need a cookie banner at all, what it must do, and which mistakes to avoid. This is general information, not legal advice.
Ferenc KulcsárUpdated: 1 November 2026Reading time: about 4 min
In short: what is required?
- Only necessary cookies? Basket, login, language: no consent needed, but information is.
- Analytics or advertising? Google Analytics, Meta Pixel, remarketing: prior consent needed.
- Rejecting just as easy The “Reject” button in the same place, just as prominent.
- Consent first, code second Tracking code may only load after acceptance.
Which rule requires what?
Two sets of rules apply to cookies. The EU ePrivacy Directive, transposed in Hungary by the Electronic Communications Act, states that information may only be stored on or read from a visitor’s device with their consent, unless this is strictly necessary for the service to work. The GDPR then defines what valid consent is: freely given, informed, unambiguous, and as easy to withdraw as to give.
The same applies not only to cookies but to every similar technique: the browser’s local storage, tracking pixels and fingerprint-based identification.
When is consent needed, and when not?
No consent needed (but information is)
- Remembering the basket contents, the login and the language choice.
- Security and spam protection cookies needed for the site to work.
- The cookie banner’s own cookie that remembers your choice.
Prior consent needed
- Visitor analytics (for example Google Analytics), unless fully anonymous.
- Advertising and remarketing code: Meta Pixel, Google Ads, TikTok Pixel.
- Embedded external content that tracks itself, such as YouTube videos or Google Maps (“click to load” is a good compromise for these).
- Chat widgets and other external services, if they set cookies.
What does a compliant cookie banner look like?
- Accept and reject are equal: both buttons are on the first layer, the same size and equally prominent.
- No pre-ticked boxes for analytics or advertising cookies.
- Choice by category: necessary, analytics, marketing.
- Code only loads after acceptance, not when the window appears.
- It can be changed later: a link or icon in the footer lets the visitor withdraw consent.
- Clear information: what each cookie is for, who sets it, and how long it lasts. This is the cookie policy.
- Consent can be proven: the system records who consented to what and when.
The most common mistakes
- Only an “Accept” button, or rejecting buried deep in the settings.
- “By continuing to browse, you accept”: this is not valid consent.
- Google Analytics loads before the window, and the cookie banner is just decoration.
- Cookie wall: the content is only visible after accepting.
- An outdated policy that does not list the tools actually in use.
What is Google Consent Mode?
If you run Google Ads and measure their results on your website, since 2024 Google has required in the European Economic Area that the cookie banner also passes the visitor’s choice on to Google. This is called Consent Mode v2. Without it, ad measurement and building remarketing audiences are restricted. Most well-known consent management tools support it, but it has to be set up.
A simpler route: no cookies
Not every website needs a cookie banner. If there is no tracking code, no advertising pixel and no tracking embed, there is nothing to ask consent for, and visitors are not bothered by a pop-up. This site works that way: it uses no cookies or advertising code, and measures visitor numbers anonymously without cookies, so there is no cookie banner, only a short cookie policy.
If you want to measure visitor numbers, there are cookie-free, anonymous analytics tools too. If you advertise, consent management cannot be avoided, but set up well, it does not spoil the visitor experience.
Frequently asked questions
Do I need a cookie banner if I only use Google Analytics?
Yes. With the usual setup, Google Analytics requires consent and may only load after acceptance. It must also be listed in the cookie policy.
Does a simple brochure website need a cookie banner?
If it only uses cookies needed for it to work, no consent window is needed, but information is. If there is any analytics or advertising code on it, then yes.
What happens if my cookie banner is not compliant?
The data protection authority (in Hungary, the NAIH) can open an investigation and impose a fine. The more common risk is having to fix it after a complaint, so it is worth preventing.
Does an online shop need a cookie banner?
No consent is needed for the basket and login, but online shops almost always use analytics and advertising code as well, and those do need it.
