Website & Development
Is a cookie banner mandatory in Belgium? The DPA rules explained
Copy for AI
The banner itself isn’t mandatory in Belgium; valid consent for non-essential cookies is.
The moment your website sets cookies that aren’t strictly necessary (analytics, marketing, tracking), the law requires you to ask for consent beforehand.
The verdict: a cookie banner in Belgium is the only workable way to collect that consent. The real obligation sits in the consent behind it, not in the banner.
Below: where the rules come from, what the Data Protection Authority (DPA) expects, and how to keep your banner compliant and conversion-friendly.
Is a cookie banner legally mandatory in Belgium?
No, but the consent for non-essential cookies is.
Where the rule comes from
The legal basis used to be article 129 of the Electronic Communications Act (ECA).
Today it’s article 10/2 of the Data Protection Act of 30 July 2018. The DPA’s own cookie checklist refers to it.
It transposes the European ePrivacy directive. It works together with the GDPR for the meaning of consent.
What valid consent means
For every cookie that isn’t strictly necessary, the visitor must give consent beforehand. That consent has to be:
- free: no pressure, no wall
- specific: per purpose
- informed: clear about what happens
- active: a click, not silence
When you need no banner
If you only use strictly necessary cookies, you need neither consent nor a banner.
For example, a cookie that remembers a shopping cart or a logged-in session.
But most B2B websites run analytics, embed videos or use advertising pixels. Those do fall under the consent requirement.
Watch out: “strictly necessary” is read narrowly. A cookie that mainly serves you, such as statistics for yourself, doesn’t count as necessary.
What exactly does the DPA require from your cookie banner?
Refusing must be as easy as accepting. That’s the core of the DPA’s approach.
In 2023 the DPA published a cookie checklist that bundles its expectations.
It stresses that the list isn’t exhaustive and adds no new obligations.
Here are the five points that matter most for your banner:
1. An equivalent reject button
There must be a “reject all” button at the same level as “accept all”, in the first layer of the banner. It must be equally visible and equally accessible.
Watch out: a banner with only “accept” and a hidden “settings” link doesn’t comply.
The EDPB’s cookie banner taskforce agreed on this too. In its report adopted on 17 January 2023, “a vast majority” of authorities called a missing reject option an infringement.
2. No pre-ticked boxes
Consent must be an active choice. Categories ticked by default don’t produce valid consent.
The same taskforce quoted GDPR recital 32: “Silence, pre-ticked boxes or inactivity should not therefore constitute consent.”
3. No deceptive design
You may not steer the choice with colour, font size or placement. Those tricks are called dark patterns.
For example, a bright green accept button next to a grey, barely legible reject button.
4. Consent per purpose
The visitor must be able to choose per category, such as analytics and marketing. That choice can sit in the second layer at the latest, not just all or nothing.
5. Easy withdrawal
Consent must be as easy to withdraw as it was to give.
In practice this means a permanent, visible element, such as a fixed icon or link. It lets your visitor adjust their choice later.
Here’s how that should look on a live site:
Publish a clear cookie policy
The DPA also expects a clear cookie policy. It explains which cookies you set, for what purpose and for how long.
That policy is your proof of transparency. It should be findable from every page, just like your privacy policy.
Keep proof of consent
Under the GDPR you must be able to demonstrate that the consent was valid (article 7(1)).
So you record when and for what a visitor consented. That gives you a trail in case of an inspection or a complaint.
The DPA checklist adds two concrete points:
- Versions: keep earlier versions of your banner and cookie policy, dated.
- Retention: store cookie preferences only for a limited time. 6 months is seen as reasonable in principle.
A good consent management tool handles much of this.
Retaining that record stays your responsibility as data controller.
Which cookies need consent?
Everything that isn’t strictly necessary for your site to function.
The distinction decides whether you ask for consent, so classify your cookies carefully:
| Type | Examples | Consent needed? |
|---|---|---|
| Strictly necessary | Session cookies, language choice, security, load balancing | No |
| Analytics | Google Analytics and similar tools | Yes |
| Marketing | Remarketing pixels, ad tags | Yes |
| Embeds and testing | Social media embeds, video players that collect data, A/B testing tools | Yes |
The first row serves the visitor. The other rows serve you.
”It’s anonymous” doesn’t count
A common mistake is loading analytics “because it’s anonymous”.
As soon as the tool sets or reads cookies that aren’t strictly necessary, the consent requirement applies.
So those scripts may only fire after the visitor accepts, not before. Our guide to Google Analytics and the GDPR covers that setup.
Watch out: a banner that shows but loads the tracking in the meantime isn’t compliant.
Consent Mode helps, but doesn’t replace consent
Google’s Consent Mode v2 adjusts tags to the visitor’s choice. It doesn’t remove the need to ask.
How do you keep your cookie banner compliant and conversion-friendly?
Honest choices, fast loading and a clear path to your forms. A correct banner and a well-performing website aren’t mutually exclusive.
Three principles do the work.
Make the choice calm rather than aggressive
A banner that blocks the whole page with a shouty overlay hurts your compliance and your first impression.
A neat banner with two equivalent buttons looks more professional. It builds more trust on your B2B website.
In B2B nobody buys from a site that immediately feels like a trick.
Watch your loading speed
Many cookie tools inject heavy scripts. Some let the banner “jump” over your content while the page loads.
That costs you points on Core Web Vitals and pushes your bounce rate up.
Tip: choose a lightweight solution, load the banner without layout shift and defer non-essential scripts until after consent.
Keep the banner out of your conversion path
Your real goal is leads, not clicks on “accept”.
Make sure your main call-to-action and your forms stay visible, even with the banner open.
Anyone who wants to optimise their forms gains nothing if the banner covers the input field on mobile.
For example, say your contact form sits at the bottom of a landing page. On a phone, a full-width banner can hide the submit button completely.
Respect beats force
Our experience ties in with the thesis behind our web design: steer on real results and on trust, not on vanity tactics.
A banner that respects visitors performs better in the long run than one that forces consent.
Build choices matter too: see our B2B website guide.
How do you set up a compliant cookie banner, step by step?
In six steps, from inventory to a test in a private window.
- Inventory: list every cookie and script your site loads, with a scanner.
- Classify: sort each one into strictly necessary or consent required.
- Configure: set up your consent tool with “accept all” and “reject all” side by side.
- Block: hold back analytics and marketing tags until consent, for example via Google Tag Manager.
- Withdraw: add a fixed icon or footer link that reopens the banner.
- Log and test: record consent, then check in a private window that nothing fires early.
Rule of thumb: repeat steps 1 and 6 after every redesign and every new marketing tool.
Our checklist for a GDPR-compliant website covers the other privacy pages you need.
What if you don’t put your cookie banner in order?
You risk a DPA fine and you lose trust with the leads you want to win.
The legal risk
The DPA actively monitors and can impose fines for violations.
Cookie walls that block access for anyone who refuses fall explicitly under this. The DPA checklist bases that on the EDPB guidelines on consent.
Whoever refuses a cookie that requires consent must still be able to keep using your site.
Deceptive banners and loading tracking before consent are classic stumbling blocks too.
The commercial risk
A non-compliant banner undermines trust.
In a long B2B sales cycle, trust often decides.
Four checks you can do today
Run through these on your own site:
- Is “reject all” as prominent as “accept all”?
- Do your analytics and marketing scripts only fire after consent?
- Can a visitor adjust their choice later on?
- Is your cookie policy findable on every page?
Three times “no” means there’s work to be done.
Our free cookie scanner shows whether your scripts really wait for consent.
Prefer to do it by hand? Check cookies on your website in five minutes.
Frequently asked questions
Do I need a cookie banner if I only use Google Analytics?
Yes. Google Analytics sets cookies that aren’t strictly necessary, so you need consent before it loads, and a banner is the practical way to ask.
Is a cookie wall allowed in Belgium?
No. The DPA says a visitor who refuses non-essential cookies must still be able to use your site.
How long can I store a visitor’s cookie choice?
Only for a limited time. The DPA checklist sees 6 months as reasonable in principle, after which you ask again.
So is a cookie banner mandatory in Belgium?
Not literally, but valid consent for non-essential cookies certainly is, and a banner is the practical way to get it.
The DPA expects an equivalent reject button, no pre-ticked boxes, no deceptive design, choice per purpose and easy withdrawal. A cookie wall isn’t allowed.
A fair, fast and calm banner is compliant and strengthens the trust your leads rely on.
Wondering whether your site is built compliant and conversion-focused? Contact us and we’ll run the four checks above on your site with you.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.