This task can be performed using Statable
Cookieless web analytics hosted in the EU
Track visitors without cookies
Choose a cookieless web analytics tool that records pageviews and basic visit context without storing an identifier in the browser. Confirm what data it collects, where processing occurs, and whether IP addresses or persistent fingerprints are retained.
Add the provider’s lightweight script to every page, ideally through the site template or tag manager. Publish it, visit several pages, then compare results with server logs and test across routes, devices, and browsers.
Best product for this task
Statable
analytics
Statable is cookieless web analytics for people who want clear numbers without the compliance overhead. No cookies means no consent banner, so you count every visitor instead of only those who click Accept. The tracker is about 2.1 KB, with a 471-byte build. Data is processed in the EU by a Dutch company. Plans start at $9/month for 10,000 pageviews, pooled across unlimited websites rather than charged per site.
What to expect from an ideal product
- Cookieless tracking lets you count every visitor who loads the page, not only those who click Accept.
- Statable processes all data in the EU through a Dutch company, which helps simplify GDPR-related data handling.
- The tracker weighs around 2.1 KB with a 471-byte build, so it adds almost no load to your pages compared to heavier scripts like Google Analytics or Hotjar.
- One plan covers unlimited websites with pooled pageviews starting at $9/month for 10,000 pageviews, so you stop paying per domain as your portfolio grows.
- Without cookies, you skip the legal grey areas around third-party data, cross-site tracking, and cookie consent regulations like ePrivacy, which shrinks your compliance risk considerably.
More about consent checks
Cookieless does not automatically mean exempt from every rule. Document the tracker’s data flow and compare it with your local privacy requirements before removing an existing consent banner.
- Clear cookies and local storage, reload the site, and confirm that no new identifier appears.
- Check that each single-page app route change generates exactly one pageview.
- Use a staging page or known test window so your validation visits are easy to identify.
