Basic analytics in Kukie.io counts the choices your visitors make. It cannot tell you how often the banner was shown and left unanswered, because the banner says nothing until someone clicks. Advanced analytics closes that gap. It counts what your banner does on every page load, so the Analytics page can show banner displays, the share of displays that get an answer, the button and the layer behind each choice, and how many page loads already carry a stored choice.
Advanced analytics is included on the Unlimited plan (the pricing page compares the plans), and it is off for every site until an owner or admin turns it on in Site Settings. Counting starts from that moment. The side-by-side comparison of Basic and Advanced analytics lists what each one covers.
Four new tabs on the Analytics page
The Analytics page now opens on an Overview tab, which is Basic analytics exactly as before: total consents, the accept, reject and custom rates, the trend, category acceptance and the top countries. Every plan keeps it. Advanced analytics adds four tabs beside it.
- 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. A row with fewer than 10 displays is left out.
- Coverage
- What the banner did on each page load, the share of page loads with a stored choice, and, in opt-out regions such as US states, the visitors that Global Privacy Control or Do Not Track opted out automatically.
Owners and admins can export every tab as one CSV file for the date range they pick, ready for a client report.
The figures that change how you read a banner
The interaction rate is the number of first choices divided by banner displays, and the ignore rate is what is left. A banner that is answered on 70% of displays and one answered on 30% can show the same acceptance split in Basic analytics, yet they are very different banners. The second one leaves most visitors browsing with only essential cookies, which is a fine outcome for privacy and a surprise for anyone reading the analytics tool afterwards.
Choices by layer show whether people decide on the first layer, open the preferences panel or meet a cookie wall. Choices by button separate Close from Reject all: Basic analytics records Close as a refusal, because that is what it does for the visitor, but a high Close count says something different about your banner than a high Reject all count.
First choices are kept apart from returning visitors. A visitor who comes back and switches everything off shows up as a withdrawal, counted on its own, instead of disappearing into the totals.
Coverage answers a question that tends to come up after a redesign: on what share of page loads did a stored choice already exist? Low coverage on a site with loyal visitors usually points at consent that expires early or a domain setting that splits the cookie.
Every figure counts page loads and choices, not people. One visitor who opens five pages before answering adds five banner displays, and the page says so.
Counts, never records
Advanced analytics needs one thing Basic analytics does not: a small request on each page load, sent by a separate script of about 2 KB that is added to your banner script only while the feature is on. What happens to each piece of data is set out below.
| Data | What happens to it |
|---|---|
| What the banner did | Shown, a stored choice restored, hidden by the consent model or not shown on a disabled page, plus the consent model and the banner language. Added to daily counts. |
| IP address | Used to find the country and region, then discarded. It never reaches the counts, not even as a hash. A hash used to limit misuse expires within a minute. |
| Browser user agent | Reduced to a device type and a browser family, then discarded. |
| Page address, referrer, cookies | Not sent. The request carries no cookie and no referrer. |
| Visitor identifier | None, of any kind. |
| The consent record | Unchanged. Where a choice was made and with which button are counted, not added to the record. |
Counts are kept per site and per day, one breakdown at a time, so a figure reads "Germany: 412 displays" or "mobile: 1,020 displays" and never combines country, browser and device into a group small enough to point at someone. Requests from bots and from Kukie.io's own scanner are not counted. The daily totals are kept for the site's consent retention period and deleted with its consent records. On a very busy site Kukie.io may count a share of page loads and weight the totals to match. The Data Processing Agreement describes all of this in Annex I, item 6, and no new sub-processor is involved.
Check the rule that applies to your site first
The page-load request is sent before a visitor makes a choice, including a visitor who will go on to refuse. The EDPB Guidelines 2/2023 on the technical scope of Article 5(3) of the ePrivacy Directive, adopted in October 2024, read the rule broadly enough to cover requests a page tells the browser to send, with or without a cookie.
Some supervisory authorities allow narrow audience measurement without consent under conditions. The CNIL's conditions, for example, are measurement limited to your own site, anonymous statistics only, no tracking across sites and no sharing, with visitors informed (see the CNIL's page on measuring the audience of websites and apps). Other authorities expect consent first. As of October 2026 there is no single EU answer, so read the guidance of the authority that applies to your site before you turn Advanced analytics on, and leave it off where you are unsure. The Help Centre article on Advanced analytics includes a paragraph you can adapt for your privacy notice and the opt-out link to add next to it.
Visitors whose browser sends Global Privacy Control or Do Not Track are not counted, except in opt-out regions such as US states. There the signal is a request not to sell or share personal data, which this counting is not, so visitors are counted as usual, and a page load on which your banner applied the signal is counted as an automatic opt-out. Any visitor can also opt out with a link you add to your privacy notice, and is then not counted.
How to turn it on
- Open the site in your dashboard and go to Site Settings.
- Open the Advanced analytics tab and turn on Collect advanced analytics.
- Read the notice that appears and select the checkbox to confirm it.
- Select Save Settings.
The Analytics page shows "Collecting since" with the date, and earlier days in a date range show no Advanced figures. Browsers keep the previous copy of your banner script for up to a day, so the first day reads lower than the days after it. Turning it off stops counting straight away. The figures already counted stay until the site's retention period removes them.
If you are working on the banner itself, the guide to improving consent rates without dark patterns and the consent rate benchmarks are good companions to the new figures. For everything else the banner does, see the full feature list.
Questions about Advanced analytics
Does Advanced analytics add anything to the consent record?
No. Each consent record holds the same fields with Advanced analytics on or off. Where a choice was made, which button was used, the consent model and the banner language are added to daily counts and then discarded.
Does it slow my site down?
The page-load request comes 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.
Why can a rate say "incomplete"?
Some ad blockers stop the request that counts a banner display but let the visitor's choice through. When more first choices than displays are counted, the page says measurement is incomplete and caps every rate at 100%.
Who can turn it on?
Organisation owners and admins, and admins of the site, one site at a time, after confirming a short notice. Editors can read the figures. On a plan without Advanced analytics the tabs show which plan includes it.
Turn it on where the banner matters most
Start with the site that gets the most traffic: a week of displays and choices there says more about your banner than a month on a quiet one. Basic analytics stays on every plan, Free included, and Advanced analytics adds its four tabs beside it wherever you turn it on.
