Simple Analytics: How to Choose a Cookie-Free Tool That Fits

A freelancer works on a laptop, seen from behind, at a sunny wooden desk with a coffee mug, a plant and a second closed laptop.

Simple analytics means a small, cookie-free tool that answers five questions: how many people visited, where they came from, which pages they read, what is happening right now, and how this compares with last month. Feature count matters less than how the tool is priced and who it is built for. A tool that bills by pageviews suits one busy site. A tool that bills by sites or offers a shared board suits someone running ten small ones.

TL;DR:

  • Simple analytics should cover visitors, sources, top pages, live traffic, and period comparison. Treat anything beyond that as an optional add-on.
  • "Cookieless" and "no consent required" are different claims. EU law is about accessing the device, not about cookies by name.
  • Pricing usually meters pageviews, sites, or features. Pick the meter that matches how your portfolio actually grows.
  • Before you buy, check what happens when you exceed a limit. Hard stops, silent sampling, and automatic upgrades cost very different amounts.
  • If you run several sites on different platforms, a single multi-site board saves more time than any individual report.
REPLASTATS

Running several small sites?

See visitors, sources, top pages and live traffic for every site on one screen, with no cookies or consent banner.

Visit →

Table of Contents

What "Simple Analytics" Should Mean, and What It Shouldn't

"Simple" gets used as a marketing word, so it helps to pin it down. A simple analytics tool shows the traffic numbers that change your decisions, and it makes you give up nothing to get them. That means no consent banner damaging your bounce rate, no 40-minute setup, and no report builder you have to learn before you can see last week's visitors.

Simple does not mean stripped. A tool that shows a single visitor count and nothing else is not simple. It is incomplete. The test is whether you can open the dashboard and answer "what changed, and why?" in under a minute, without clicking into a sub-report.

Simple also does not mean cheap. Some of the most expensive mistakes in this category come from tools that look minimal on the surface but meter usage in ways that punish growth or punish running many sites. Most of this guide is about that pricing side, because it is where buyers get caught.

The Five Numbers a Simple Analytics Dashboard Must Show

If a tool can't show all five of these on its main screen, keep looking.

  • Unique visitors. This is the headline count. It should be estimated without persistent identifiers, which means it will be slightly less precise about returning visitors across days than a cookie-based tool. For most decisions, that trade-off doesn't matter.
  • Traffic sources. Search, social, referrals, direct, and campaign tags (UTM parameters). This is the number that tells you which effort is paying off.
  • Top pages. Ranked by visitors, with entry pages visible. If a two-year-old blog post brings in a third of your traffic, you should see that in five seconds.
  • Live traffic. A real-time count of who is on the site now. You need it on launch days, after a newsletter goes out, and when you're checking whether a tracking script still fires after a theme update.
  • Period comparison. This week against last week, and this month against the same month last year. A number with no comparison is trivia.

Everything else is an add-on you should pay for only if you will use it: session replays, heatmaps, funnels, goal tracking, revenue attribution. Replays and heatmaps are the most useful of these for small sites, because they show why a page underperforms rather than just that it does. If you want a method for reading these numbers without getting lost, our guide on how to analyze website traffic without drowning in dashboards walks through a weekly routine.

Two people talk earnestly across a café table over cups of coffee, one explaining with open hands while the other listens.

Many tools in this category advertise "no cookie banner needed." That claim is often defensible, but it rests on more than the absence of cookies, and you should understand why.

The rule that triggers consent in the EU is Article 5(3) of the ePrivacy Directive. It covers storing information on, or accessing information from, a user's device. It doesn't mention cookies by name. The European Data Protection Board made this explicit in its Guidelines 2/2023 on the technical scope of Article 5(3), which say the rule can reach tracking pixels, local storage, and other techniques that access the device.

Article 5(3) of the ePrivacy Directive never says "cookie." It regulates storing or accessing information on a user's device, and that is the test a "cookieless" tool has to pass.

In practice, a cookie-free analytics tool earns its "no banner" claim through a combination of design choices:

  • No persistent identifiers. It sets no cookies, writes nothing to local storage, and does no device fingerprinting.
  • Short-lived, non-reversible hashing. If it counts unique visitors, it uses a salt that rotates daily, so nothing links a person across days.
  • Aggregate-only reporting. No individual profiles, and no sharing with ad networks.

Data protection law still applies separately. The GDPR governs any personal data you process, including IP addresses, even briefly. National regulators also differ. France's CNIL has published conditions under which audience-measurement tools can be exempt from consent, and those conditions are strict.

Our position is that a well-built cookieless tool removes the banner for typical site analytics. You should still read each vendor's data processing documentation, and that includes ours. If you add features that identify individuals, such as logged-in user IDs or CRM syncing, the analysis changes.

How Simple Analytics Pricing Actually Works

Nearly every privacy-friendly analytics tool prices on one of four meters. The meter matters more than the headline monthly price, because it decides what you'll pay in a year's time.

Pricing meter What you pay for Best fit The trap
Monthly pageviews Total traffic across all sites One or two high-traffic sites A single viral post can push you into a higher tier for a full billing cycle
Number of sites Each domain you track Freelancers and agencies with many small sites Low-traffic hobby sites cost as much as busy client sites
Feature tier History length, replays, heatmaps, team seats Owners who know which add-ons they need You can be pushed into a tier for one feature you rarely use
Flat or free tier A fixed bundle, often one site Testing, personal sites Short data retention, or no export, so you lose history when you leave

Most tools combine two of these meters, for example pageviews within feature tiers. Work out which one will grow fastest for you. A blogger whose traffic doubles every year should avoid steep pageview tiers. An agency adding three client sites a quarter should avoid per-site pricing without volume breaks.

Pro Tip: Before you buy, find out exactly what the tool does when you exceed your plan, and get the answer in writing from the docs, not from a sales chat. There are three common behaviors. A hard stop means tracking pauses and you get a gap in your data. Silent sampling means numbers become estimates without a clear label. An automatic upgrade means your card is charged the next tier up. Then check your peak month of pageviews, not your average, and size your plan for that.

If you're moving from a tool you've outgrown on price, our breakdown of finding a cheaper privacy analytics alternative without traps covers data export, retention, and overage terms in more depth.

Script Weight and Where Your Data Lives

Hands slide a server into a rack in a dim data center aisle lit by small green indicator lights.

Two technical details separate genuinely simple tools from tools that only look simple.

The size and loading of the tracking script

Every analytics tool adds JavaScript to your pages. A small, deferred script, meaning one that loads after the page renders, has a negligible effect on load time. A heavy synchronous script can slow your largest content element, which is the thing visitors wait for. Google's web.dev guidance on Largest Contentful Paint sets 2.5 seconds or less as the threshold for a "good" experience. Third-party scripts are a common reason sites miss it.

Look for a published script size in kilobytes and a defer or async attribute in the install snippet. If a vendor doesn't publish its script size, check it yourself in your browser's network tab.

Where the data is stored

On WordPress especially, some analytics plugins write every pageview into your site's own database. That works at first. Over months, the tables grow, backups get slower, and on cheap shared hosting the extra writes can slow down the site you were trying to measure. Tools that send data to a separate server keep your database lean. We cover this problem in detail in our guide to the best WordPress analytics plugin without database bloat.

Which Option We'd Pick for Each Kind of Site Owner

A baker in an apron, a photographer holding a camera and a designer carrying a closed laptop chat together in a shared workspace.

Here is our recommendation, based on how people actually run sites:

  • One personal site or portfolio. Use a free tier from a cookieless tool. Check that it keeps at least a few months of history and lets you export your data. Don't pay for replays until you have enough traffic for patterns to show up.
  • One business site with real traffic. Choose a paid tier with at least 12 months of history so you can compare year over year, plus heatmaps on your key pages. Pageview-based pricing is fine here if the overage behavior is reasonable.
  • A freelancer or small agency with five or more sites across platforms. This is where most simple tools fail. You don't need deeper reports. You need every site on one screen, with one install method that works whether the site runs on WordPress, Shopify, Webflow, or plain HTML. Prioritize a multi-site board over any single feature, and avoid per-site pricing that has no volume break.
  • Anyone who needs funnels, cohort analysis, or ad attribution. A simple tool is the wrong choice. Accept the complexity and the consent banner that comes with a full suite, and don't pay for a simple tool hoping it will grow into one.

The mistake we see most often is choosing a tool for the features you might need someday instead of the five numbers you'll check every Monday.

Replastats is built for the multi-site problem described above. It shows visitors, sources, top pages, and live traffic for every site you run, whatever platform each one uses. It installs with a single 4.7 KB deferred script or a WordPress plugin that shows reports inside wp-admin. It stores data on a separate server rather than in your site's database, and it sets no cookies, so you don't need a consent banner for it. Session replays and heatmaps start on the Starter plan. The Pro and Agency plans add the multi-site board and let you ask Claude questions about your analytics in plain English.

There's a free tier you can start with today. The honest caveat is that it covers a single site. The multi-site board, which is the main reason agencies choose us, requires Pro or Agency. Check the current pricing page and our data processing documentation before you commit, just as you would with any vendor.

Frequently Asked Questions

What is simple analytics?

Simple analytics is a lightweight, usually cookie-free way to measure website traffic. It focuses on a small set of numbers: visitors, traffic sources, top pages, live traffic, and period comparisons. It trades the depth of a full analytics suite for speed, privacy, and a dashboard you can read in under a minute.

Often, but not automatically. EU consent rules under Article 5(3) of the ePrivacy Directive apply to storing or accessing information on a user's device, not just to cookies. A cookieless tool that uses no persistent identifiers and reports only aggregate data typically avoids the banner requirement, but you should confirm how each vendor counts visitors.

How is simple analytics usually priced?

Most privacy-friendly analytics tools charge by monthly pageviews, by number of sites, by feature tier, or by a mix of these. Pageview pricing suits one busy site, while per-site or multi-site plans suit people running many smaller sites. Always check what happens when you exceed your plan's limit.

Will an analytics script slow down my website?

A small script loaded with defer or async has a negligible effect on load time. Heavy or synchronous scripts can delay Largest Contentful Paint, which Google's web.dev guidance says should be 2.5 seconds or less. Check the published script size, or measure it in your browser's network tab.

Are cookieless visitor counts accurate?

They are accurate for pageviews and daily visitors, and close enough for trends and comparisons. Because they avoid persistent identifiers, they can't reliably recognize the same person returning on a different day. For most site owners making content and marketing decisions, that difference doesn't change the conclusion.

Sources