Advanced analytics counts what your cookie banner does on every page load: how often it is shown and answered, which button and which layer is used, and how many pages already carry a stored choice. Use it to see whether a change to your banner made a difference, and where visitors leave the banner unanswered.
Advanced analytics is included on the Unlimited plan. See the pricing page for what each plan includes. It is off for every site until an organisation owner or admin turns it on.
Basic and Advanced analytics
The Analytics page of every site opens on the Overview tab. That is Basic analytics, on every plan: the consents your banner recorded, the accept, reject and custom rates, the trend, category acceptance and the top countries. It counts choices, so it cannot tell you how often the banner was shown and left unanswered.
Advanced analytics adds four tabs to the same page:
- Interactions: banner displays, the interaction, ignore, accept and consent rates with the change on the previous period, a daily chart that marks each new banner version, choices by layer and by button, and returning visitors.
- Categories: the opt-in rate of each optional category, day by day, and of each service on sites that ask for consent per service.
- Audience: banner displays, the interaction rate and the share of Accept all by country, region, device type, browser, banner language and consent model.
- Coverage: what the banner did on each page load, the share of page loads that already carry a stored choice, and, in opt-out regions such as US states, automatic opt-outs from Global Privacy Control and Do Not Track.
Every figure counts page loads and choices, not people. One visitor who opens five pages before answering adds five banner displays.
Before you turn it on
With Advanced analytics on, your banner sends Kukie.io one small request on every page load, before the visitor makes a choice. Data protection authorities read requests like this differently, so check what applies to your site first. This section is guidance, not legal advice.
- Some authorities allow narrow audience measurement without consent, under conditions. In October 2026 these include France (CNIL), Spain (AEPD), Italy (Garante), the Netherlands and, since February 2026, the United Kingdom. The conditions usually include anonymous statistics for your own site only, telling visitors about it and giving them a simple way to object.
- Others expect consent first. Germany's authorities decide case by case, and the guidance in Belgium and Austria treats analytics as needing consent.
- The rules are changing. The EU is discussing a change that would allow this kind of measurement without consent in every member state, but it is not law yet.
Where your authority expects consent, or you are unsure, leave Advanced analytics off. Basic analytics, which counts only the choices visitors make, keeps working.
If you turn it on:
- Add the paragraph below to your privacy or cookie notice.
- Add an opt-out link to the same notice. See Let visitors opt out.
- List Kukie.io as a processor in your records of processing, under the existing Data Processing Agreement.
You can adapt this paragraph for your own notice:
Banner statistics. This website uses Kukie.io to show its cookie banner. To understand how the banner performs, the banner sends Kukie.io a short anonymous message each time a page loads, saying whether the banner was shown and, when you make a choice, which option you used. The message contains no cookie, no identifier and no page address. Kukie.io uses your IP address to find your country and region and to protect its service from misuse, and your browser details only to tell what type of device and which browser you use, then discards them. Only daily totals are kept, for [how long this site keeps consent records]. We use these totals only to improve our cookie banner. You can opt out at any time with the link below. Visits from browsers that send Global Privacy Control or Do Not Track are not counted, except in regions where this site uses the opt-out model, such as US states.
When you turn Advanced analytics on, the dashboard asks you to confirm that checking whether your visitors must consent, and telling them about it, is your responsibility. Kukie.io records who confirmed it and when.
Turn it on
- Open the site in your dashboard and go to Site Settings.
- Open the Advanced analytics tab.
- Turn on Collect advanced analytics.
- Read the notice that appears and select the checkbox to confirm it.
- Select Save Settings.
You can also turn it on from any of the four Advanced tabs on the Analytics page, which show the same switch and notice until it is on. Organisation owners and admins, and admins of the site, can change it. Editors can read the figures.
Turning it on updates your site's banner script. Browsers keep the previous copy for up to a day, and a visitor whose browser still holds it is not counted until the browser fetches the new one. So the first day reads lower than the days after it.
Choices are counted from your consent log. If consent logging is off for the site (Site Settings > Consent), Advanced analytics counts banner displays but no choices, and the page says so.
Turn it off
Turn off Collect advanced analytics in the same place and select Save Settings. Counting stops straight away. The figures already counted stay until your consent retention period removes them.
If your plan changes to one without Advanced analytics, counting stops and the Advanced tabs show which plan includes it. The switch stays on, so counting starts again if you move back to a plan that includes it. To prevent that, turn it off on the Advanced analytics tab of Site Settings, which shows it as paused. If the site moves to another organisation, the switch is turned off there, because the receiving organisation decides whether to collect, and confirms the notice again when it turns it on.
When the figures start
The Advanced tabs show Collecting since and the date you turned it on. Nothing is counted before that date, so a date range that starts earlier shows no figures for the earlier days. The change on the previous period is shown only when that period started after the collecting-since date, because a period that was not fully counted cannot be compared.
Today's figures are live: counts reach the page within seconds, with no overnight step.
What the figures mean
| Figure | What it counts |
|---|---|
| Page load | One page on which your banner script ran. Pages listed under Disabled Pages on the Banner Editor's Behaviour tab are counted apart and are not page loads. |
| Banner displays | Page loads on which the first layer of the banner or the cookie wall was shown. |
| First choice | A choice by a visitor who had no stored choice. A notice that closes on its own, by its timer or when the visitor scrolls, is not a choice: it counts towards the ignore rate. |
| Interaction rate | First choices divided by banner displays. |
| Ignore rate | 100% minus the interaction rate: displays that ended without a choice. |
| Accept rate | The share of first choices made with Accept all. |
| Consent rate | First choices that allow at least one optional category, divided by banner displays. |
| Opt-in rate | For a category or a service: the share of all choices in the date range that allow it. |
| Coverage | Page loads on which a stored choice already existed, divided by all page loads. |
| Automatic opt-out | In an opt-out region, a page load on which the visitor's Global Privacy Control or Do Not Track signal opted them out, because the site respects that signal. Everywhere else a visitor who sends the signal is not counted at all. |
| Withdrawal | A returning visitor's choice that allows no optional category. |
On the Audience tab each row also shows an Accept all share: Accept all choices divided by all choices from that row, changed choices included. A row with fewer than 10 banner displays is left out, and the table says how many were.
Advanced analytics counts the Close button on its own. Basic analytics records Close as Reject all, which is what it does for the visitor, so the two tabs can differ for that button.
Why a rate says "incomplete"
Some ad blockers stop the small request that counts a banner display but let the visitor's choice through. On a site with many such visitors, more first choices than banner displays can be counted. When that happens the page says that measurement is incomplete and caps every rate at 100%. The counts themselves are still right. Only the rates that divide by banner displays read high.
What is collected and what is not
When Advanced analytics is on, your banner script sends one small request on each page load, saying only what the banner did there: shown (as a banner or a cookie wall), a stored choice restored, hidden by the consent model, or not shown on a disabled page. It also says whether a privacy signal opted the visitor out, the consent model and the banner language. When a visitor makes a choice, the request that records it also says where the choice was made, which button was used, the consent model and the banner language.
- The page-load request carries no cookie, no page address, no referrer and no visitor identifier.
- The visitor's IP address is used to find the country and region, then discarded. The browser's user agent is reduced to a device type and a browser family, then discarded. Neither is kept with the counts. A hash of the IP address is held for up to a minute to limit misuse, then expires.
- Only daily counts are kept, one breakdown at a time: "Germany: 412 displays" or "mobile: 1,020 displays", never a combination such as country and browser together.
- Nothing is added to the consent record. Each record holds the same fields with Advanced analytics on or off.
- Requests from known bots and from the Kukie.io scanner are not counted.
- A visitor who uses your opt-out link sends nothing and their choices are not counted. Neither are visitors whose browser sends Global Privacy Control or Do Not Track, except in opt-out regions such as US states.
- The daily counts are kept for the site's consent retention period, then deleted with its consent records.
- On a very busy site Kukie.io may count a share of page loads and weight the counts to match, so the figures stay comparable.
Kukie.io processes this data for you under the Data Processing Agreement, which describes it in Annex I, item 6. Kukie.io uses the counts only to show them to you, never for its own purposes. No new sub-processor is involved.
Let visitors opt out
Add a link or button with the data-cc-analytics-opt-out attribute to your privacy notice. When a visitor selects it, their browser stops sending the page-load request and their choices are no longer counted. The browser keeps the objection until the visitor withdraws it or clears their browser data. A link with data-cc-analytics-opt-in withdraws it.
<a href="#" data-cc-analytics-opt-out>Do not count my visits in the banner statistics</a>
<a href="#" data-cc-analytics-opt-in>Count my visits again</a>Your banner script marks the page with data-kukie-analytics="on" or data-kukie-analytics="off" on the html element, so your own CSS can show which applies:
html[data-kukie-analytics="off"] .counted-note { display: none; }Put the attribute on the link or button itself, not on an element around it. A click on an ordinary link inside a marked element works as usual.
The browser keeps the objection for one address. If your site opens on both example.com and www.example.com, a visitor who opts out on one is still counted on the other, so redirect one address to the other.
The links work only while Advanced analytics is on for the site. While it is off nothing is counted, and the links do nothing.
Export the figures
On any Advanced tab, select Export to download the figures for the date range as one CSV file, a section for each tab. Organisation owners and admins can export. The export on the Overview tab is the Basic analytics export.
Frequently asked questions
Does Advanced analytics slow my site down?
The page-load request is sent from a separate script of about 2 KB that is added to your banner script only while Advanced analytics is on. It sends one request per page load, in the background, and never waits for an answer.
What happens for visitors who send Global Privacy Control or Do Not Track?
They are not counted. Their browser sends no page-load request, and their choices are not counted either. The exception is regions where your site applies the opt-out model, such as US states. There the signal asks a business not to sell or share personal data, which this counting is not, so the page load and any choice are counted. Where your site respects the signal and the visitor has no stored choice, the page load is counted as an automatic opt-out instead of a banner display.
Can my own scripts see what the banner did on a page?
Yes. Every banner, with or without Advanced analytics, fires the cc:banner-state event once per page load. See JavaScript events and consent callbacks.
