Skip to content
Get started

Web analytics

Web analytics without cookies, next to everything that explains the numbers

ROOKON counts visitors, sources, pages, campaigns and goals without cookies or device storage, and shows that traffic next to your errors, sessions and conversions. You don’t just see how many people came. You see what happened to them.

Get started Try the live demos

The problem

Traffic numbers alone don’t tell you what to fix

Most analytics tools answer “how many” and stop there. When signups dip, you still open an error tracker, a replay tool and a spreadsheet to find out why. Cookie-based analytics also adds a consent banner, data transfers and a heavy tag to the very pages you are trying to measure.

  • Analytics, errors and replays live in separate tools with numbers that never match
  • Cookie-based tracking needs consent and loses the visitors who decline
  • Heavy tags slow down the pages you are measuring
  • A dashboard shows the drop, but not the cause

Live demo 1 of 2

Explore cookieless analytics

A simulated month of traffic for a fictional SaaS. Switch ranges, filter by source or country, and watch the realtime counter.

  • Click “Google” to filter every chart
  • Open the Events tab
  • Switch to the last 24 hours

rookon · acme-cloud · web analytics

Simulated data

38 visitors nowLive

Bounce rate39.4%▼ 7.3% vs prev.
Avg. visit3m 18s▲ 9.4% vs prev.

Visitors · 30 days

visitors Previous period
visitors over the last 30 days, compared with the previous period
TimevisitorsPrevious period
14 Oct1,2321,209
15 Oct1,4401,156
16 Oct1,4861,249
17 Oct9161,159
18 Oct8511,227
19 Oct1,362936
20 Oct1,585824
21 Oct1,4021,142
22 Oct1,5351,332
23 Oct1,4101,110
24 Oct8561,309
25 Oct9701,256
26 Oct1,255837
27 Oct1,342799
28 Oct1,4151,367
29 Oct1,3781,276
30 Oct1,2731,290
31 Oct1,0051,217
1 Nov1,0371,159
2 Nov1,539885
3 Nov1,151867
4 Nov1,5211,370
5 Nov1,2911,310
6 Nov1,1561,238
7 Nov1,0451,226
8 Nov9311,485
9 Nov1,460825
10 Nov1,514922
11 Nov1,3671,275
12 Nov1,3561,372

Click a row to filter everything above.

Right now

38

visitors in the last 5 minutes

Visitors per minute, last 30 minutes
Timevisitors / min
16:3011
16:3111
16:3213
16:3315
16:3416
16:3513
16:3613
16:3719
16:3812
16:3913
16:4015
16:4111
16:4212
16:4312
16:4412
16:4510
16:469
16:4710
16:489
16:4910
16:5011
16:514
16:526
16:538
16:5410
16:557
16:568
16:5710
16:5810
16:5916
  • /12
  • /pricing7
  • /features4
  • /blog/launch-week3
cookieless

No cookies or device storage. Visitors are counted with a salted hash that rotates daily, so they can’t be followed across days. Raw IP addresses are never stored.

How ROOKON helps

What you get

  • Cookieless by design

    No cookies, no local storage, no fingerprinting. Visitors are counted with a salted hash that rotates daily and can’t be reversed or linked across days. Raw IP addresses are never stored.

  • The numbers that matter

    Visitors, sessions, pageviews, bounce rate and visit duration, with entry and exit pages, sources, UTM campaigns, devices, browsers and countries.

  • Goals and custom events

    Count signups, upgrades or any action with one line of JavaScript, and see conversion rates by source, page and campaign.

  • Real time

    See how many people are on your site right now and which pages they are reading.

  • Connected to the rest of ROOKON

    Go from a traffic or conversion drop straight to the errors, sessions and funnel steps behind it.

  • Light on your pages

    One small script loaded with defer. Single-page apps are tracked automatically through the History API.

Live demo 2 of 2

One line to install

Pick your framework, copy the snippet and simulate the first visit arriving. The key and URL shown are placeholders.

  • Switch to Google Tag Manager
  • Press “Simulate a first visit”

rookon · new project · install

Simulated data

1 · Add the snippet

app/layout.tsx
import Script from "next/script";

export default function RootLayout({ children }) {
  return (
    <html lang="en">
      <body>
        {children}
        <Script src="https://api.rookon.example/t.js" data-key="pk_demo9fK2xQ7mL3vR8tYwB4n" strategy="afterInteractive" />
      </body>
    </html>
  );
}

Client-side navigations are tracked automatically through the History API.

  • no cookies
  • loads with defer
  • respects Do Not Track by default

2 · Verify the installation

Waiting for your first event

Open your site after deploying the snippet. This demo can simulate a first visit.

Simulated. The key and URL above are placeholders. Your workspace shows your own snippet.

From install to insight

  1. 01

    Add one script

    Every page view is sent without cookies; client-side navigation is picked up automatically.

  2. 02

    Define goals

    Choose the events or pages that count as a conversion: signup, upgrade, demo request.

  3. 03

    Read the dashboard

    Filter by source, page, device or country and compare with the previous period.

  4. 04

    Act on what you see

    ROOKON links changes in traffic and conversion to the technical causes it finds, and measures your fix.

FAQ

Common questions

Does ROOKON web analytics use cookies?

No. The tracker stores nothing on the visitor’s device. Visitors are counted on the server with a hash of the request details and a salt that rotates every day; old salts are deleted, so a visitor can’t be followed across days and the hash can’t be turned back into an IP address. Raw IP addresses are never stored.

Do I still need a cookie banner?

That depends on where you operate and on everything else your site loads, so ROOKON can’t decide it for you. The analytics script itself sets no cookies and stores nothing on the device, which many teams use to simplify consent. Check your setup with your data protection officer or counsel.

Can I track custom events and conversions?

Yes. Call rookon('event', 'Signup'), optionally with a few properties, and define goals on events or page paths. Conversion rates then show up in the dashboard and in impact reports for the changes you ship.

Does it work with single-page apps?

Yes. Route changes through the History API (Next.js, React Router, Vue Router and others) are counted as page views without extra code.

How is this different from a standalone analytics tool?

The traffic numbers live next to your errors, session replays and funnels. A drop in conversion can be traced to its cause, and every change you ship is measured against the same data.

Related

Measure your traffic without cookies

Sign up and see your visitors next to the problems they run into.

Get started with ROOKONExplore live demo