How to Compare Cookieless Website Tracking Tools
Why cookieless is a category, not one product
Cookieless tracking usually means the tool does not set cookies in the visitor's browser. That does not mean every tool works the same way. Some use a short-lived anonymous identifier, some rely on server logs, some use first-party endpoints, and some still try to identify visitors by device fingerprinting. If you run a small site, the important question is not whether a tool is cookieless, but whether it gives you useful data without creating privacy work.
Four broad approaches
- Client-side script trackers: A small script runs on each page and sends pageview, referrer, browser, and screen information to a hosted service. Setup is usually one tag. You can add custom events with extra attributes. The script can be blocked by some ad blockers, and bot traffic needs filtering.
- Server log analyzers: These parse your web server's access logs. No script is required, so they see requests from visitors who block JavaScript. They require separating HTML pages from image and asset requests, and they often lack page-level custom events unless you add server-side logging.
- First-party endpoint or edge collection: Your own domain or worker receives tracking requests. This can reduce third-party blocking and keep data in one place, but it adds infrastructure and maintenance.
- Fingerprinting-based tools: Some tools avoid cookies but combine browser version, language, screen size, and other signals into a stable identifier. This is a different privacy trade-off from a daily anonymous id. If privacy is the reason you moved away from cookies, fingerprinting may not be the direction you want.
Decide what you actually need
Before comparing, write down five things:
- Pages and sources you need
- Whether you need custom events like signups or downloads
- Whether you need funnels
- Whether you need bot filtering or spike alerts
- Whether you want a coding agent to read the data for you
A visitor count alone is easier to find than a cookieless tracker with funnels, campaign links, and agent access.
Evaluation criteria
- Identifier lifetime. Does the tool remember someone across days? A tool that resets the identifier daily gives useful pageview counts but does not build a long-term profile. This is often the simplest privacy position.
- Data collected. Does it store full IP addresses, user agents, or other device details? Does it allow you to disable collection of anything you do not need?
- Cookies and storage. Check the browser developer tools after installing. If you see cookies or local storage entries, the tool is not as cookieless as the marketing page claims.
- Bot handling. A good tool should filter or label obvious bots, because a small site's logs can be mostly crawlers. Ask how the tool handles known bots, headless browsers, and traffic spikes.
- Export and retention. Can you get your data out? How long is raw data kept? These matter if you ever want to compare year-over-year traffic or move tools.
- Agent or API access. If you already use a coding agent, a read-only MCP server or API can save time. Instead of exporting a CSV, you can ask the agent for a funnel or a traffic drop report.
- Setup and maintenance. A hosted script may take one tag; a server log setup may require shipping logs and updating parsers. Choose the level you can maintain.
Test on a small site
Set up a trial on a site that gets a small amount of real traffic. For each candidate:
- Load a page and inspect the network and storage tabs.
- Visit from a second browser or private window.
- Click a test button or trigger a custom event.
- Wait a day and check whether the daily visitor counts behave as expected.
- Ask the dashboard or agent a question you actually need answered, such as "which page lost the most traffic last week?"
Where small sites get stuck
One common mistake is comparing only the dashboard. The dashboard may look similar across tools, but the underlying data model is what determines whether you can answer a question later. A tool that only shows pageviews cannot tell you where people dropped out of a signup funnel. A tool that stores a stable fingerprint may give you repeat visitor counts, but at a privacy cost you may not want.
Another mistake is assuming "cookieless" means "no personal data." The script still sends network information such as IP addresses and user agents. A privacy-friendly tool should minimize what it stores, not just avoid cookies. Check the tool's documentation and, if you are unsure about your legal position, get advice for your jurisdiction.
Putting it together
A practical shortlist for a small site might look like this:
- If you want the least setup and page-level funnels, try a hosted cookieless script tracker.
- If you already collect server logs and mostly care about raw traffic, a log analyzer may be enough.
- If you have engineering time and want full control over data flow, a first-party endpoint may fit.
- If you are evaluating a tool that claims to identify users without cookies, ask whether it uses fingerprinting and how long the identifier lasts.
When you compare a hosted script tracker, check that it sets no cookies, supports custom events and funnels, and has a way for your coding agent to read the data. measuremy.site is one option in that category; the setup is a single script tag and the MCP server connects to Claude Code, Cursor, or Codex.
The best cookieless tracking solution is the one you can install correctly, keep for a full season, and actually use to make changes. Compare the data model and the setup cost before the dashboard, and you will be less likely to switch again in six months.
See it on your own site
measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.
Start free trial See the live demoAdd measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt
Free tools
- Analytics tag checker: Which analytics and pixels a site runs, plus duplicate and broken tags.
- Free UTM link builder: Add utm_source, medium and campaign to any link.
- Website traffic checker: A site's popularity rank and estimated monthly visits.
More from the blog
- How to calculate your website conversion rate, and what to compare it to
- Is my A/B test result significant? A plain-English guide with a worked example
- What is bounce rate, how is it calculated, and is yours a problem?
- How to add a visitor counter to your website or GitHub README
- How much traffic does a website get? How to estimate any site's visits
- How to track QR code scans: count them, and see which poster worked
- How to see how many people clicked your link (without a paid shortener)
- How to check if your Google Analytics 4 tag is installed (and only counting once)
- Why GA4 shows your campaign traffic as Unassigned (and how to fix the links)
- Does your redirect keep your UTM tags? How to check before a campaign goes out
- How I built a self-hosted analytics MCP server on Cloudflare Workers and D1
- UTM tracking explained: what the parameters mean and how to use them
- Conversion funnel analysis for small sites: a practical guide
- Sudden drop in website traffic? A checklist for finding the cause
- What is an MCP server? A plain-English guide for people who run websites
- Vanity Metrics vs Useful Metrics: What to Track
- Why Your Analytics Numbers Differ Between Tools
- When GA4 Is Too Much for a Small Website
- How to keep historical data when switching analytics tools
- How to give an AI agent read-only access to your analytics
- Why developers are connecting agents to production data
- How to recover from a sudden traffic drop
- Website analytics for indie hackers: what to watch and what to ignore
- Direct Traffic Explained: Why So Much Is Unknown
- Why a high bounce rate is not always bad
- High bounce rate: 8 causes and practical fixes
- How to Set Up Traffic Alerts for Sudden Drops
- How to Track Traffic From a Podcast
- How to measure the return on a paid ad campaign
- How to use analytics to decide what to write next
- How the Model Context Protocol Works
- Track File Downloads Without Guesswork
- Adding analytics to a Next.js app without slowing it down
- Core Web Vitals and Traffic: Is There a Link?
- Analytics After Cookies: What Actually Changes
- GDPR and website analytics: a practical guide for small sites
- How to Compare Website Analytics Tools by Privacy
- GA4 Events Explained for Beginners
- How to measure a newsletter send with UTM links
- How to track Hacker News traffic
- Adding Analytics to a Framer Site
- How to ask your coding agent about your analytics
- What Is Bounce Rate and How Is It Calculated?
- A practical website analytics retention policy
- Map your site's funnel from first visit to signup
- What Is a Good Bounce Rate?
- How to automate a weekly traffic report
- A Practical Privacy-Friendly Analytics Checklist
- Adding an MCP server to Claude Code
- How long should you keep analytics data?
- How to Build a Small MCP Server That Actually Helps
- How to Find the Biggest Drop Off in a Funnel
- What Is the Urchin Tracking Module?
- What Microsoft MCP servers actually do
- UTM parameters for email newsletters
- Track Button Clicks Without Google Tag Manager
- How to track the results of a social media post without cookies
- How to track traffic from a GitHub README
- How to measure a product launch without guessing