The Complete Guide to Cookie-Free Web Analytics

Cookie-free web analytics tracks your visitors without placing any cookies in their browsers, without storing IP addresses, and without fingerprinting devices. You get pageviews, traffic sources, conversions, and session paths — and your visitors never see a consent banner, because there is nothing requiring their consent.

This guide explains how it works, what data you actually get, and where the trade-offs are.

Why cookies became a problem

Google Analytics and most traditional analytics tools identify visitors with a cookie — a small file stored in the browser. That cookie persists across visits and lets the tool build a profile: this is the same person who visited three weeks ago, clicked this ad, and came back to buy.

That persistence is precisely what the ePrivacy Directive and GDPR regulate. Storing data that can identify a person — even indirectly — requires their informed consent in the EU and EEA. Hence the cookie banners. Hence the consent walls.

The practical result: anywhere from 20 % to 60 % of visitors decline or simply close the banner. Their sessions disappear from your data. You are making decisions on a fraction of your traffic.

How cookie-free analytics works

Instead of a persistent identifier, cookie-free analytics relies on session-scoped signals that do not follow a visitor across days or devices.

When a visitor loads a page, the tracker sends an event — a small JSON payload — to the analytics server. That payload contains:

• the full URL of the current page, including UTM parameters
• the referrer (where the visitor came from)
• the page title
• the screen width (to classify device type)
• the event name (page_view, generate_lead, purchase, etc.)

What it does not contain: an IP address, a cookie, a device fingerprint, or any persistent visitor identifier. The server assigns a short-lived session key that expires at midnight (site timezone). Tomorrow, the same browser is a new visitor.

This approach is sometimes called "stateless" or "server-side privacy" analytics.

What you can and cannot measure

You can measure

• Pageviews and unique sessions — accurately, including visitors who block cookies
• Traffic sources — organic search, paid campaigns (via UTM), social, direct, email
• Referrers — including Telegram links, VK posts, newsletter clicks
• Conversions — form submissions, purchases, button clicks, any custom event
• Page paths and funnels — within a single day
• Device type — mobile, tablet, desktop (from screen width)
• Revenue and lead value — via value and currency parameters, same as GA4

The main trade-off: cross-day attribution

Because there is no persistent visitor ID, you cannot stitch together a journey that spans multiple days. If someone visits on Monday from an organic search, comes back on Friday from a direct URL, and buys — the purchase is attributed to direct, not the original organic source.

For most content sites and small businesses, this is not a significant problem. The majority of conversions happen within a single session or within the same day. For e-commerce with long consideration cycles, it matters more — and that is a real limitation worth knowing upfront.

How it compares to GA4

GA4's biggest advantage is its identity graph: it can attribute a conversion to a campaign that ran weeks ago. Cookie-free analytics trades that for completeness — you see 100 % of sessions, not just the ones that consented.

How to add Gauss to your site

Add one script tag before </body>:

<script defer src="https://collect.gausslab.io/js/gauss.js" data-site="YOUR_SITE_ID"></script>

Page views are tracked automatically. To track a conversion (for example, a form submission):

gauss.track("generate_lead", { form_id: "contact", value: 0 })

Event names follow the GA4 vocabulary: page_view, generate_lead, purchase, add_to_cart, and any custom name you define. If you already have GA4 event tracking, Gauss reads the same gtag() calls via its adapter — no re-tagging needed.

Who cookie-free analytics fits best

• Content sites and blogs where most conversions happen in one session
• SaaS landing pages tracking sign-ups and trials
• Agencies managing multiple client sites under one dashboard
• Any site with EU/EEA traffic that wants to skip the consent banner

It is a worse fit for large e-commerce stores where a visitor researches over weeks and for any use case that depends on cross-device or cross-day stitching.

Summary

Cookie-free analytics works by tracking events without persistent identifiers. You get accurate, complete data — no sampling, no consent drop-off — in exchange for losing cross-day attribution. For most sites, that trade is worth it.

Ready to try it? Start with Gauss →