Customisation
Colours, CSS, logo and RTL
Cookie consent banner
Ask first. Keep the answer.
Kukie.io asks your visitors before your site uses cookies that are not essential, with Accept all and Reject all side by side. It applies each answer at once and keeps a dated record.
Watch the walkthrough
How the banner works, step by step.
Follow a visitor from the first page load to a stored answer, then see the settings you control in Banner Editor and on WordPress.
2 minutes, narrated, with captions in the player. The sites and rules in it are examples.
Read the transcript
- 0:00 Analytics, ads and chat widgets all want to set cookies the moment a page loads. Your visitors deserve a choice first.
- 0:08 This is the Kukie.io consent banner. You add one line of script to your site, and it does the rest on every visit.
- 0:16 Before the banner even appears, known trackers are held back. Google Analytics, the Meta Pixel and Hotjar wait for an answer.
- 0:24 Then the banner asks. Accept all and Reject all sit side by side, at the same size, so saying no is as easy as saying yes.
- 0:33 Manage preferences opens the categories. Essential cookies are always on. Everything else starts switched off.
- 0:40 Open a category to see each cookie, who sets it, and how long it lasts.
- 0:45 Here, the visitor allows analytics, leaves marketing off, and saves.
- 0:49 The answer takes effect at once. Google Analytics and Hotjar start, and the Meta Pixel stays blocked. Every choice is stored with a consent ID you can look up later.
- 1:00 A small button stays in the corner, so visitors can change their mind, or withdraw, at any time.
- 1:07 The banner works from the keyboard, too. Focus stays inside until the visitor chooses, and Escape steps back from the preferences.
- 1:15 With Auto-Translation on, it speaks more than 70 languages, right to left included. And it can switch to a dark palette when the visitor's device is in dark mode.
- 1:26 You decide how it looks in the Banner Editor. Pick one of four layouts, set your colours, or let the banner take them from your website. Every change shows in a live preview.
- 1:36 On WordPress, you don't even need the script. Install the free Kukie.io plugin, connect your site, and the banner is live. Its Consent banner page keeps the main settings inside WordPress.
- 1:49 The Kukie.io cookie banner is included on every plan, including Free. Ask first. Keep the answer.
Why it matters
Regulators start with the banner.
Most complaints about a website start with something anyone can screenshot: a banner that only offers Accept, one that sets tracking cookies before anyone chooses, or no banner at all.
-
Tracking before consent
No banner at all
Analytics and advertising cookies are set on the first page load, before the visitor has agreed to anything. It is the most common finding in cookie enforcement actions, and anyone with a browser can check it.
-
Unequal choice
A banner that only accepts
If refusing takes 3 clicks and accepting takes one, regulators in several EU countries have held that the consent is not freely given. The cookies were then set without a valid legal basis, banner or no banner.
-
Ignored refusal
A banner that does not block
It looks fine, which is what makes it expensive. The banner appears, the visitor selects Reject all and the tags fire anyway, because nothing was connected to the answer. Your browser's developer tools show it.
How it works
From the first visit to a stored record.
You add one line of script to your site. The steps below then run on every visit, with no further work from you.
-
Step 1: Trackers are held back
Before the banner shows, Kukie.io recognises known tracking scripts as they are added to the page and holds them until there is an answer. A tag written into your HTML is held reliably only when you mark it with its category.
-
Step 2: The visitor decides
The banner appears in your site's language. With Auto-Translation on, it follows the page language, then the browser's, when that language is ticked. Accept all and Reject all sit side by side. Manage preferences opens the categories, and within them each service.
-
Step 3: The answer takes effect
Allowed scripts run at once and refused ones stay blocked. Consent signals go out to the tools you connect, and the choice is stored with a consent ID you can look up later.
Layouts
Four layouts, the same controls.
The layouts differ in how much of the page they cover and how hard they are to ignore. All 4 carry the same buttons and the same preferences.
| Layout | Where it sits | Suits |
|---|---|---|
| Popup | Centred over the page | Sites where an explicit decision matters more than an uninterrupted first view |
| Top bar | Full width, across the top of the page | Content and publishing sites that want the notice read first, while most of the article stays visible |
| Bottom bar | Full width, across the bottom of the page | Sites that want the notice visible without touching the top of the page |
| Floating | A card in a corner you choose | Marketing sites and product pages where the hero image is the point |
Any layout can dim the page behind it with a background overlay, and the page then waits for the visitor's answer. The overlay is on for new sites; switch it off on the Behaviour tab in Banner Editor to keep the page usable while the banner is open.
You can switch between all 4 in Banner Editor and check each one in a live preview before anything reaches your visitors. The button order is yours to set too, on the banner and in the preferences.
On the page
What your visitors see.
Most people choose once on the first layer. The detail below is for the visitors who open the preferences, and for the regulator who may one day ask what they offered.
- Accept all and Reject all, side by side. Same size, same level, on the first layer. It is the default, not a setting you have to find.
- Categories, then individual services. A visitor can allow analytics but refuse marketing, or go further and allow one analytics tool while refusing another. Nothing is ticked in advance.
- A way back. An optional re-open button sits in a corner of every page, so consent can be changed or withdrawn later. That is a requirement, not an extra.
- One choice across your subdomains. When you turn on subdomain sharing, consent given on your main site carries across every subdomain of the same domain, so a visitor is not asked again at the shop or the help centre.
Languages
The banner speaks 70+ languages.
With Auto-Translation on, the banner reads the page language, then the browser's, and shows its built-in translation when you have ticked that language, right-to-left layouts for Arabic and Hebrew included. Wording you write yourself appears in the languages you write it in, and with Auto-Translation on, only in those ticked.
Eight of the built-in translations, shown as the banner shows them.
Built in
The details a banner is judged on.
The parts visitors rarely notice and regulators always do. All of them come with the banner, on every plan.
Keyboards and screen readers
Focus moves into the banner when it opens and stays there until the visitor chooses. Every control works from the keyboard, each one shows a visible outline, and a screen reader is told what the banner is and when a choice was saved. The banner is designed against WCAG 2.2 AA.
How long an answer lasts
From 1 to 730 days, set in each region rule. A new rule starts at 365, and the banner asks again when the period runs out.
Asking again after a change
Each region rule can ask again when you add or remove a cookie category, so an earlier answer is not taken as an answer about a category it never saw. After any other change, Renew user consents in Site Settings asks every visitor again.
One answer across subdomains
Turn on subdomain sharing and consent given on your main site carries to the shop and the help centre, so a visitor is not asked twice.
Browser privacy signals
Choose to respect Global Privacy Control and Do Not Track, and a browser that sends one starts from a refusal.
Consent signals
One answer, passed to every tool that asks.
Ad and analytics platforms increasingly ask for a consent signal before they accept European traffic. Kukie.io sends each one the visitor's answer, in the format that platform reads, once you turn it on.
-
Google Consent Mode v2
Ad storage, analytics storage, ad user data and ad personalisation, updated the moment the visitor chooses.
-
Google Tag Manager
A consent event in the data layer, so tags you fire from a container can wait for it.
-
Microsoft UET Consent Mode
The ad storage signal Microsoft Advertising reads.
-
Microsoft ClarityOn the Pro, Agency and Unlimited plans
The consent call Clarity needs before it sets cookies.
-
Matomo
Tracking and cookies held, then released when the visitor agrees.
-
Amazon Consent SignalOn the Agency and Unlimited plans
The consent fields Amazon Ads reads for European traffic.
After the first answer
A way back, and a record of every answer.
Consent is not a one-off. Visitors can change their mind at any time, and each answer they give, including a withdrawal, is stored the same way.
The re-open button
Changing your mind takes one click
An optional button in one of 4 corners, as an icon, a pill or a tab, reopens the preferences on every page. Withdrawing is as easy as agreeing, which is what regulators expect.
The record
Every answer, dated and findable
Each choice is stored with a consent ID you can look up later, with the date, the country and the page it was given on, and the log can be exported. Read more about consent analytics and records.
In your dashboard
The decisions stay yours.
Kukie.io does the mechanical work on every visit. What the banner says, what counts as what, where it shows and how it looks are settings you own.
- You choose the words
- The heading, body and button labels, in the languages you choose. With Auto-Translation on, the built-in text covers each language ticked under Enabled Languages, and your own wording replaces it where you wrote some.
- You choose what counts as what
- Each cookie and script sits in a category. A scan proposes the categories, and you have the final say.
- You choose where it shows
- Pages that should show no banner, such as your privacy policy, go on the Disabled Pages list. Script blocking still applies there.
- You choose the look
- Layout, colours, button order and corner radius, previewed live in Banner Editor before anything reaches your visitors.
When it matters most
Where a good banner saves the most work.
Every site that uses cookies that are not essential needs one. These are the situations where getting it right early saves the most work later.
Visitors in more than one country
EU visitors have to opt in, visitors in California have to be able to opt out, and some places ask only for notice. One banner can follow a different rule for each region.
You run advertising
Ad platforms increasingly ask for a consent signal before they accept European traffic. The banner passes the visitor's answer on to the ones you connect.
You embed other people's content
A YouTube player or a map is a third-party tracker with pictures. iFrame blocking holds those back, rather than the banner alone.
Somebody else will inherit the site
A banner nobody can explain is a liability. Stored consent records and a written cookie policy let the next person answer questions without digging.
Questions about the cookie banner
Does my website need a cookie consent banner?
Yes, if your site sets any cookie that is not strictly necessary to deliver the page, such as analytics, advertising, embedded video, live chat or A/B testing. In the EU, the UK and a growing number of other places you need to ask before those cookies are set. A site that sets only its own session and security cookies generally does not. To find out which group you are in, scan the site and look at what loads.
What has to be on a cookie consent banner?
What you are asking for, who is asking, what the cookies are used for and a real choice. Under the GDPR that choice has to be as easy to refuse as to give, which in practice means a reject option next to the accept option rather than behind a settings screen. Regulators also expect the banner to name the categories of cookies in use and to link to a fuller cookie policy.
Do I need a reject button as well as an accept button?
In the EU, yes in practice. The French regulator CNIL and several of its counterparts have taken enforcement action over banners where accepting took one click and refusing took several, on the basis that consent obtained that way is not freely given. Kukie.io shows Accept all and Reject all side by side on the first layer, at the same size, by default.
What happens to my analytics when someone rejects cookies?
You stop receiving cookie-based measurement from that visitor, so session counts fall. How far depends on your audience and how the banner is written. If you use Google Analytics or Google Ads, Google Consent Mode v2 lets Google keep receiving cookieless signals from visitors who declined, which it uses to model some of the missing conversions. Kukie.io sends those signals once you turn on Google Consent Mode v2 for the site.
How long does consent last before I have to ask again?
You set it in each region rule, from 1 to 730 days; a new rule starts at 365. Kukie.io keeps the visitor's choice for that period and asks again once it expires. Many EU site owners settle on 6 to 12 months, the range several supervisory authorities have pointed to as reasonable, but the right answer for your site is a decision for whoever owns your privacy compliance.
Can visitors change their mind after they have accepted?
Yes, and they must be able to. Kukie.io can show a small re-open button on every page, in one of 4 corners and 3 styles, so a visitor can reopen the preferences and change or withdraw consent at any time. Withdrawing is recorded the same way as agreeing.
Put a consent banner on your site.
The banner is included on every plan, including Free. Add one line of script and it is live, with no card needed to start.
Related features
The banner is one part of the consent flow. These are the pieces it works with most closely.
-
-
Accessibility
Designed against WCAG 2.2 AA
-
Geo-targeting
A banner rule for each region
More on cookie banners
Background reading on consent, refusal and what a banner has to offer.
-
What is a cookie banner, and what must it include?
A cookie banner asks for consent before non-essential cookies are set, and the EU expects Accept all and Reject all at equal weight on the f...
-
Opt-In vs Opt-Out: What They Mean and How to Comply
Opt-in consent requires users to take a clear action before data collection begins. Opt-out assumes consent by default unless the user activ...
-
What happens when you reject all cookies on a website
Clicking Reject all keeps the strictly necessary cookies a site needs, so pages, logins and baskets still work, while analytics, advertising...
-
Essential vs non-essential cookies, and which ones need consent
Strictly necessary cookies for a login, a basket or a chosen language need no consent, while analytics and advertising cookies do. A cookie...
Disclaimer
Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.
