Cookieless analytics: measure people, not automation
Analytics that lives in your pages counts the bots that run its script as visitors, and never sees the rest. Klacos analyses visits in front of your site, bots included: your human audience is measured on its own, without cookies, and recognised bots drop out of your figures. Your decisions finally rest on people.
Your analytics only sees part of your traffic
An analytics tool installed in your pages only counts visitors that run its script. That’s where two errors creep in, pulling in opposite directions.
Bots that never load the script stay invisible: they read your pages, load your server and fill in your forms without showing up anywhere. Those that load it like a browser become visitors: spikes from countries you don’t sell to, one-second visits, a bounce rate that moves for no reason.
The cost never shows up in a report: budget moved to the source that seems to work, an article judged popular because a bot read it, a campaign tuned on visitors who don’t exist.
Our guide to bot traffic in your analytics explains where these fake visitors come from and how to spot them.
What you measure, without cookies
- Visitors, visits, page views, bounce rate, visit duration and engaged time, the time a visitor is actually active on the page.
- Entry and exit pages, referrers and campaigns, and visits that arrive from a chat assistant.
- Returning visitors over 30 days, with nothing stored on their device.
- Countries and regions, devices, browsers, operating systems and languages.
- Outbound links, downloads, missing pages, and your own events, such as a purchase or a sign-up, which become goals and funnels.
- Filters you can combine, comparison with the previous period or last year, and a real-time view.
Nothing is stored in the browser
No cookies, no storage
The analytics script writes nothing to the browser and computes no device fingerprint.
Under 2 KB
1,961 bytes compressed, served from your own domain, under the path you choose.
The share you cannot see
Ad blockers, browsers without JavaScript: you know what share of your pages analytics couldn’t see, instead of guessing.
A returning visitor is recognised on the server, from their address and browser, with a key renewed every 30 days. That isn’t anonymous data: what it means for your own compliance depends on how you use it, and it’s worth going through with you before you go live.
Your figures don’t stay locked in the console: exports, an API and sharing with a client are among the other analytics capabilities.
Questions about cookieless analytics
Do I need a consent banner?
The script stores nothing in the browser. The answer still depends on your use and on the rules that apply to you, so we will not give it on your behalf.
Are Do Not Track and Global Privacy Control respected?
It is a per-site setting. By default these signals are ignored; you can choose to honour them.
Is my single-page app measured?
Yes. Page changes without a reload count as page views, including when only the URL fragment changes.
Can I leave out my own visits?
Yes. Addresses, hostnames and paths can be excluded from measurement, site by site.
Do you see visits from AI assistants?
Yes. Visits that arrive from a chat assistant get a source of their own, alongside your other referrers.
Can I measure without putting the proxy in front of my site?
Yes, with the script alone, for a site you cannot put anything in front of. You then lose sight of bots that never run it: it is in front of the site that Klacos sees the full picture.
Compare your human audience with what your current tool reports
Request early access, or tell us about your current analytics and what it counts that it shouldn’t. The service behind the measurement sits in front of your site without changing it, and speeds up your pages along the way.