You want to know how many people visit the site, where they come from and which pages they read. You do not want a cookie banner covering half the screen, or Google Analytics with every consent setting. The answer is a family of tools that measure without cookies. Before choosing, understand what that choice gains and what it stops measuring, because the difference is by design, not quality.
This is how it works with Analytics, from the Operations line (by Ciro Cesar Maciel, who writes this).
How a tool counts without cookies
A cookie exists to recognize the same browser tomorrow. Without it, the tool needs another way to count visits while storing nothing on the visitor's device.
In Analytics, a visit is a hash computed on the server from a secret, the day, the site, the IP and the user-agent. The day is part of it, so the hash changes every day: within a day the same person counts once; tomorrow they are a new visit. Nothing is stored in the browser, and no response from the dashboard or the API carries the IP or the visitor hash. Pageviews are not stored raw either: each load increments daily counters per page, source, country and device.
What you get
- Pageviews, visits, top pages, sources, countries, devices and the time each page was visible.
- Goals and events:
analytics.trackGoal('signup')counts a result with a conversion rate;analytics.trackEvent('cta-click')counts a click. - A one-line install, no tag manager.
- An MCP server so an AI agent can answer "where did traffic come from this week?" with your browser sign-in.
What you give up, by design
Because the hash changes daily: no returning visitors, no unique users per month, no cohorts, retention or multi-session funnels. No identifying people, no session recording, heatmaps or A/B tests. No real-time view, no CSV export, no e-mail reports. Dimension breakdowns cover the last 90 days. If your business depends on knowing who came back, a cookieless tool does not answer that, and no setting changes it.
Install
<script defer src="https://analytics.worker.myoperations.click/tracker.js" data-site="<site id>" data-spa="auto" data-honor-dnt="true" ></script> data-spa="auto" is required for React, Vue, SvelteKit or Next with client-side navigation: without it, an SPA reports the first load and nothing else, which looks like low traffic, not missing configuration. data-honor-dnt="true" respects Do Not Track and Global Privacy Control, lowering the count on purpose. If an agent built the site, paste https://myoperations.click/products/analytics/llms.txt and ask it to install.
So can the banner go?
What Analytics guarantees is technical: no cookie and no persistent identifier in the browser, so there is nothing there to consent to. If your site uses nothing else that sets cookies (ad pixels, chat widgets, third-party video), the technical reason for the banner is gone. Your privacy notice, legal basis and final call under GDPR or Brazil's LGPD remain yours or your lawyer's.
Other cookieless options
Plausible, Fathom, Umami and Simple Analytics also measure without cookies. Analytics uses the same visit definition as Plausible and Fathom: a distinct visitor within a day. Compare by what you need: measuring MCP servers, reading numbers through an agent, self-hosting or ready-made integrations.
Honest notes
- Free for 1 site, no card, no expiry. Paid plans are priced in Brazilian reais.
- Ad blockers can block the script: it loads from the Analytics address, with no first-party proxy.
- Self-declared bots are dropped; a bot pretending to be a browser is counted.
- The Analytics dashboard is in Portuguese for now.