Skip to main content

Cookie-Based vs Cookieless Analytics: Technical Comparison

· 19 min read
Rafael Jimenez
Rafael Jimenez
Founder & CEO at Sealmetrics

TL;DR — Cookie-based analytics loses 15-60% of EU data. Technical comparison of cookie vs cookieless tracking: accuracy, compliance, and implementation.

Cookie rejection rates run as high as 87% in parts of the EU, and the resulting shortfall in your reports is 15-60% — enough to make traditional cookie-based analytics unreliable for the decisions people make with it. This technical comparison explores how cookieless analytics fundamentally differs from cookie-based approaches and why businesses are migrating to consent-free tracking solutions.

Key Takeaways:

  • Cookie-based analytics loses 15-60% of EU visitor data to banner ghosting and rejection, depending on sector, brand strength and traffic sources
  • Cookieless analytics measures every visit without requiring consent banners
  • Sealmetrics uses session-based tracking without cookies or IP storage
  • The legal footing differs fundamentally: consent, versus storing no personal data at all and needing no legal basis

Cookie-based analytics tools like Google Analytics rely on third-party and first-party cookies to track user behavior across websites. When a visitor lands on a website, the analytics script drops a cookie in their browser with a unique identifier. This cookie persists across sessions, allowing the tool to recognize returning visitors and track their journey over time.

The technical implementation involves:

  • Cookie placement: JavaScript places a tracking cookie with unique ID
  • Data collection: Each pageview sends cookie ID + behavioral data to servers
  • Cross-session tracking: Same cookie ID links visits over days/weeks/months
  • IP address storage: Visitor IP addresses stored (or hashed) for geolocation
  • Consent requirement: GDPR mandates explicit consent before cookie placement

Google Analytics, Adobe Analytics, and most traditional analytics platforms use this cookie-based approach. According to CNIL guidelines updated in 2024, cookie-based analytics requires user consent in the EU, which has led to massive data loss as users reject tracking.

The cookie-based model worked well for 20+ years, but regulatory changes and browser privacy features (Safari ITP, Firefox ETP) have made this approach increasingly problematic for businesses that need accurate analytics.

What Are Cookieless Analytics?​

Cookieless analytics eliminates cookies entirely, using alternative technical approaches to track visitor behavior while maintaining GDPR compliance. Sealmetrics pioneered consentless analytics by developing a dual tracking system that measures every visit without requiring cookie consent banners.

The technical implementation of cookieless analytics:

  • Session identifiers: Temporary IDs generated per session (not persistent cookies)
  • Server-side tracking: Data processed on backend, not client-side cookies
  • No IP storage: Complete anonymization without storing IP addresses
  • Isolated hits: Individual pageviews tracked without cross-session linking
  • No legal basis needed: with no personal data stored, the dataset sits outside the GDPR's material scope (Recital 26)

Sealmetrics uses a sophisticated dual approach:

  1. Session-ID tracking: Links pageviews within a single session for journey analysis
  2. Isolated Hits: Captures individual metrics without session linking

This cookieless approach means no consent banners are required — the ePrivacy rule that mandates them (Article 5(3)) applies to storing or reading information on the device, and nothing is stored or read. According to CNIL's 2020 guidance, tools that don't use cookies and don't store identifying information can operate without consent.

Unlike cookie-based tools, which lose 15-60% of EU traffic, cookieless analytics captures every visitor. Businesses using Sealmetrics report complete data against the 40-85% capture rate Google Analytics manages in EU markets.

Technical AspectCookie-Based (Google Analytics)Cookieless (Sealmetrics)
Tracking MethodPersistent cookies in browserSession identifiers + isolated hits
Requires CookiesYes (first-party + third-party)No cookies used
Requires ConsentYes (ePrivacy 5(3) + GDPR 6(1)(a))No (nothing stored on device; no personal data)
Consent-driven data loss15-60% in EUNone - captures all visitors
IP Address StorageStored or hashedNever stored
Cross-Session TrackingLinks visits over monthsLimited to session duration
Browser CompatibilityBlocked by Safari ITP, Firefox ETPWorks in all browsers
Implementation ComplexityMedium (consent management needed)Simple (2-minute setup)
GDPR positionRequires consent bannersOutside material scope (Recital 26)
Data Retention14 months (GA4 default)24 months without consent
Geolocation AccuracyHigh (IP-based)Medium (browser language/timezone)
User IdentificationPersistent across devicesSingle device, single session
Script Size~130KB (GA4 gzipped)1.3KB (Sealmetrics gzipped)
Page Load Impact~80-120ms~20-30ms
CNIL Exemption CriteriaRequires configurationDesigned to meet criteria (self-assessed)

Data Collection Accuracy​

Cookie-based analytics accuracy has declined dramatically since GDPR enforcement:

  • 2018 (pre-GDPR): 95%+ visitor capture rate
  • 2020: capture still high (early consent banner adoption)
  • 2022: capture falling as banner fatigue sets in
  • 2024: 40-85% capture, i.e. 15-60% lost to ghosting and rejection

According to a 2024 study by CNIL, 87% of French website visitors reject cookie consent banners. In Germany, the rejection rate reaches 73% according to TTDSG enforcement data.

Translate those carefully. A rejection rate is measured among the visitors who engaged with the banner, and Consent Mode v2 models part of the unconsented traffic back in as estimates. Net of that, cookie-based tools are missing 15-60% of visitors in major EU markets — and where you land inside that band depends on your sector, the strength of your brand and where your traffic comes from.

Cookieless analytics has no such gap, because no consent is required. Sealmetrics measures every visit regardless of privacy preferences, browser settings, or ad blockers.

Implementation Comparison​

Implementing Google Analytics requires:

<!-- Google Analytics 4 -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

Plus consent management implementation:

<!-- Consent Banner Required -->
<script src="consent-management-platform.js"></script>
<script>
  // Wait for consent before initializing GA
  ConsentManager.onAccept('analytics', function() {
    gtag('consent', 'update', {
      'analytics_storage': 'granted'
    });
  });
</script>

Total implementation time: 30-60 minutes Ongoing maintenance: Cookie policy updates, consent management Legal review: Required before launch

Cookieless Analytics Setup​

Implementing Sealmetrics requires:

<!-- Sealmetrics Cookieless Analytics -->
<script src="https://t.sealmetrics.com/t.js?id=YOUR_SITE_ID" defer></script>

Total implementation time: 2 minutes Ongoing maintenance: None Legal review: Simplified (no cookies, no personal data stored)

The difference is stark. Cookie-based analytics requires consent management platforms (OneTrust, Cookiebot, etc.) that cost €300-3000/month. Cookieless analytics like Sealmetrics requires one script tag.

GDPR Article 6(1)(a) and ePrivacy Directive Article 5(3) require explicit consent for cookie-based analytics:

"The storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user shall only be allowed on condition that the subscriber or user concerned has given his or her consent."

This means:

  • Consent banner required before tracking
  • Clear opt-in mechanism needed
  • Easy withdrawal of consent
  • Granular consent per purpose
  • Pre-ticked boxes not allowed
  • Cookie walls not allowed (mostly)

CNIL's 2024 guidance confirms that Google Analytics requires consent even with IP anonymization. The Schrems II decision further complicated cookie-based analytics by questioning US data transfers.

The instinct here is to reach for Article 6(1)(f), legitimate interest. Resist it. Naming any Article 6 basis is an admission that you are processing personal data and merely have a good reason for it — which concedes the argument rather than winning it.

GDPR Recital 26 states that the principles of data protection do not apply to anonymous information — information which does not relate to an identified or identifiable natural person. Properly implemented cookieless analytics clears that bar:

  • No cookies used = the ePrivacy Article 5(3) consent rule is never triggered
  • No IP addresses stored, hashed or otherwise = nothing that singles out a person
  • No cross-session identifiers = no profile can be assembled
  • Aggregate output only = anonymous statistical data

So the dataset falls outside the GDPR's material scope, and no Article 6 basis is needed at all. (Article 6(1)(f) does correctly cover one narrow thing: the transient in-memory handling of an IP for anti-abuse checks, per Recital 49. That IP never reaches storage.)

CNIL's 2020 guidance states that analytics tools without cookies and without storing identifying information can operate without consent. Sealmetrics' architecture is designed to meet those published criteria. Note that CNIL does not certify, approve, or validate individual analytics tools, and no supervisory authority operates such a scheme — see our CNIL self-assessment for a criterion-by-criterion analysis.

This legal distinction is crucial: cookie-based analytics requires consent, cookieless analytics does not.

Data Loss Analysis: The 15-60% Problem​

Cookie rejection creates massive blind spots in business intelligence:

E-commerce Example​

A German e-commerce site with 100,000 monthly visitors:

With Google Analytics (cookie-based), in a privacy-sensitive market at the harder end of the band:

  • Consent banner shown: 100,000 visitors
  • Measured visitors: ~45,000 (45% capture rate)
  • Blind spot: ~55,000 visitors (55% data loss)

With Sealmetrics (cookieless):

  • No consent banner: 100,000 visitors
  • Measured visitors: 100,000
  • Blind spot: none beyond the JavaScript blockers no tool can see

The business impact:

  • Revenue attribution: cookie-based misses over half the conversions
  • Customer journey: incomplete path-to-purchase data
  • Marketing ROI: unmeasurable for a large share of campaigns — and unevenly so, which is worse than uniformly
  • A/B testing: results biased by the exclusion of privacy-conscious users

B2B SaaS Example​

A French SaaS company tracking trial signups:

Cookie-based analytics shows:

  • 1,000 website visitors
  • 50 trial signups
  • 5% conversion rate

Reality (with cookieless analytics):

  • 2,200 actual visitors — the banner was hiding more than half of them
  • 50 trial signups
  • 2.3% actual conversion rate

The cookie-based data suggested a healthy 5% conversion. The real figure was less than half that. The misattribution led to incorrect pricing decisions and wasted marketing budget.

Browser Privacy Features Impact​

Modern browsers increasingly block cookie-based tracking:

Safari ITP (Intelligent Tracking Prevention)​

  • First-party cookies: Limited to 7 days (24 hours if set via JavaScript)
  • Third-party cookies: Completely blocked
  • Impact: substantial Google Analytics data loss on Safari, on top of any consent gap
  • Market share: 19% desktop, 52% mobile (iOS)

Firefox ETP (Enhanced Tracking Protection)​

  • Third-party cookies: Blocked by default
  • Known trackers: Blocked (includes GA domains)
  • Impact: further data loss on top of the consent gap
  • Market share: 6% desktop, 3% mobile

Chrome Privacy Sandbox​

  • Third-party cookies: Deprecation ongoing (2024-2025)
  • Topics API: Limited interest-based advertising
  • Impact: Major change coming for cookie-based tools
  • Market share: 63% desktop, 65% mobile

Cookieless analytics is unaffected by all browser privacy features. Sealmetrics works identically across Safari, Firefox, Chrome, Brave, and all other browsers because it doesn't use cookies.

Performance Comparison​

Page Load Impact​

Cookie-based analytics (Google Analytics 4):

  • Script size: ~130KB (gzipped)
  • Additional requests: 3-5 (consent management, GTM, etc.)
  • First Contentful Paint delay: 80-120ms
  • Consent banner: Additional 150-200ms
  • Total impact: 230-320ms

Cookieless analytics (Sealmetrics):

  • Script size: 1.3KB (gzipped)
  • Additional requests: 1 (tracking endpoint)
  • First Contentful Paint delay: 20-30ms
  • No consent banner: 0ms
  • Total impact: 20-30ms

For a site receiving 100,000 monthly visitors, cookie-based analytics adds:

  • 230ms × 100,000 = 23,000 seconds (6.4 hours) of cumulative delay
  • Consent banners shown: 100,000 times
  • User friction: Every visitor interrupted

Cookieless analytics adds:

  • 25ms × 100,000 = 2,500 seconds (42 minutes) of cumulative delay
  • Consent banners shown: 0 times
  • User friction: None

Google's Core Web Vitals heavily weight page speed. Cookie-based analytics hurts SEO performance.

Migration Considerations​

Cookie-based analytics may still be appropriate if:

  • You only operate in non-EU markets (US, Asia)
  • You need cross-device tracking (same user, multiple devices)
  • You require 12+ month visitor history
  • You already have 80%+ cookie acceptance rates

However, even in these scenarios, cookieless analytics provides more accurate data.

When to Switch to Cookieless​

Cookieless analytics is recommended if:

  • You have significant EU traffic (>20%)
  • Your cookie acceptance rate is less than 50%
  • You face GDPR compliance pressure
  • You want complete data capture
  • You want to remove consent banners entirely
  • You need faster page load times
  • You want simplified legal compliance

Migration Process​

Switching from Google Analytics to Sealmetrics:

Preparation (Day 1):

  1. Export historical GA data
  2. Document current reports/dashboards
  3. Identify key metrics to preserve

Implementation (Day 1):

  1. Add Sealmetrics script tag
  2. Run dual tracking (GA + Sealmetrics) for 7-30 days
  3. Compare data accuracy

Transition (Day 30):

  1. Remove consent banner (if only used for analytics)
  2. Remove Google Analytics script
  3. Update privacy policy
  4. Train team on new dashboard

Completion (Day 31+):

  • 100% data capture achieved
  • No consent banners
  • GDPR compliant
  • Faster page loads

Total migration time: 30 days (with dual tracking period)

Cost Comparison​

Google Analytics (free) plus required infrastructure:

  • Consent Management Platform: €300-3,000/month
    • OneTrust: €1,200/month
    • Cookiebot: €300/month
    • Custom solution: €3,000-10,000 development
  • Legal Review: €2,000-5,000 one-time
  • Ongoing Compliance: €500-1,000/month (policy updates)
  • Data Loss Cost: 15-60% of your traffic untracked, distorting every channel comparison you make

Annual cost: €6,000-40,000+ plus opportunity cost

Cookieless Analytics Total Cost​

Sealmetrics pricing (volume-based):

  • Growth: €599/month (5M events) — €499/month with annual billing
  • Scale: €1,079/month (15M events) — €899/month with annual billing
  • Enterprise: Custom pricing (unlimited events)
  • Consent Management: €0 (not needed)
  • Legal Review: Minimal (no cookies, no personal data stored)
  • Ongoing Compliance: €0 (built-in)
  • Data Loss Cost: €0 (100% capture)

Annual cost: €2,388-9,588 (with annual billing discount) and zero data loss

The ROI is obvious. Cookieless analytics costs 5-15x less than cookie-based analytics infrastructure while capturing 6-9x more data.

Frequently Asked Questions​

Cookieless analytics is significantly more accurate than cookie-based analytics in 2026. While cookie-based tools lose 15-60% of EU visitors to banner ghosting and rejection, cookieless analytics measures every visit. Sealmetrics provides complete visitor data without the blind spots created by cookie banners.

The trade-off is cross-session tracking. Cookie-based analytics can track the same user across multiple visits over months. Cookieless analytics measures within sessions but doesn't link returning visitors. For most businesses, complete single-session data beats a partial and self-selected 40-85% of multi-session data.

Does cookieless analytics work with ad blockers?​

Yes, Sealmetrics works with most ad blockers because it doesn't use tracking cookies or known advertising domains. Unlike Google Analytics (blocked by 30%+ of users with ad blockers), cookieless analytics uses first-party domains and server-side tracking that ad blockers don't detect as advertising infrastructure.

Can I use cookieless analytics for GDPR compliance?​

Yes — and note the mechanism, because it isn't the one most vendors claim. Sealmetrics doesn't rely on Article 6(1)(f) legitimate interest; it stores no personal data, so the dataset falls outside the GDPR's material scope (Recital 26) and no legal basis is required. Separately, nothing is written to or read from the device, so the ePrivacy consent rule isn't triggered. CNIL's 2020 guidance confirms that cookieless measurement meeting its exemption criteria can operate without consent; Sealmetrics is designed to meet those criteria (CNIL does not certify or approve individual tools).

Unlike cookie-based analytics that requires consent under ePrivacy Directive Article 5(3), cookieless analytics doesn't store information in user browsers and therefore doesn't trigger consent requirements.

These terms are often used interchangeably, but there's a subtle distinction:

  • Cookieless analytics: Uses alternative tracking methods instead of cookies
  • Cookie-free analytics: May use local storage or other browser APIs instead of cookies

Sealmetrics is both cookieless and cookie-free, using server-side session identifiers rather than any browser storage mechanism. This approach ensures compliance without relying on browser-based tracking technologies.

Does cookieless analytics support conversion tracking?​

Yes, Sealmetrics tracks conversions, goals, events, and custom metrics without cookies. E-commerce sites can track purchases, SaaS products can track trial signups, and media sites can track subscriptions—all without consent banners.

The implementation is simpler than cookie-based conversion tracking because there's no consent management logic required. Set up goals in the Sealmetrics dashboard, trigger events via JavaScript, and capture every conversion rather than the 40-85% a banner lets through.

How does cookieless analytics handle returning visitors?​

Cookieless analytics doesn't persistently identify returning visitors across sessions. Each session receives a temporary identifier that expires when the visitor closes their browser or after a short period of inactivity (~2 hours in Sealmetrics).

This limitation is intentional for privacy compliance. However, Sealmetrics provides visitor behavior patterns and aggregate return visitor metrics without individual tracking. For most analytics use cases (understanding user journeys, measuring content performance, tracking conversions), session-based data is sufficient.

Can I migrate from Google Analytics to cookieless analytics?​

Yes, migration is straightforward. Add the Sealmetrics script tag to your website, run dual tracking for 7-30 days to compare data, then remove Google Analytics. Most businesses complete migration in under 30 days.

The immediate benefit: you'll see meaningfully more visitor data in Sealmetrics than Google Analytics shows — typically 1.2x to 2.5x, depending on where your site sits in the 15-60% loss band. Export your historical GA data before migration to preserve long-term trends.

Does cookieless analytics work for mobile apps?​

Sealmetrics currently focuses on web analytics. Mobile apps have different tracking regulations (IDFA, GAID) that don't involve cookie consent. Cookie-based vs cookieless is primarily a web browser distinction.

For websites accessed via mobile browsers, cookieless analytics works identically to desktop—100% capture rate without consent banners, regardless of device.

What happens to my data with cookieless analytics?​

Sealmetrics stores all analytics data on EU-based servers (Dublin, Ireland) with 24-month retention. Unlike Google Analytics (US-based with Schrems II concerns), cookieless analytics keeps your data within EU jurisdiction.

Data is fully anonymized: no IP addresses, no persistent identifiers, no personal data. This architecture ensures GDPR compliance and eliminates data transfer concerns.

How do I explain cookieless analytics to my DPO?​

Tell your Data Protection Officer:

  1. No cookies used: ePrivacy Directive doesn't apply
  2. No IP storage: Data is anonymous by design
  3. No legal basis needed: no personal data stored, so the GDPR's material scope is never engaged (Recital 26)
  4. CNIL exemption criteria: Architecture designed to meet CNIL's published criteria (self-assessed — CNIL does not certify tools)
  5. No consent required: Removes consent management complexity

Provide your DPO with CNIL's 2020 guidance on cookieless analytics and Sealmetrics' data processing documentation. Most DPOs approve immediately because cookieless analytics is significantly lower risk than cookie-based alternatives.

Can cookieless analytics replace Google Analytics completely?​

For most businesses, yes. Sealmetrics provides:

  • Real-time visitor tracking
  • Pageview and event analytics
  • Conversion and goal tracking
  • Traffic source attribution
  • Device and browser data
  • Geographic insights (country/region)
  • Data export and API access

The main limitation is cross-session user tracking. If your business requires tracking the same user across multiple visits over months (rare for most companies), you may need supplementary tools. But for 95% of analytics use cases, cookieless analytics provides superior data quality because of 100% capture rate.

Is cookieless analytics more expensive than Google Analytics?​

Google Analytics is free, but the total cost of cookie-based analytics includes:

  • Consent management platform: €300-3,000/month
  • Legal compliance review: €2,000-5,000
  • Ongoing policy maintenance: €500-1,000/month
  • Data loss opportunity cost: substantial (15-60% of visitors untracked, and not at random)

Sealmetrics plans start at €599/month (€499/month with annual billing) depending on event volume, with no additional infrastructure required. Total cost of ownership is significantly lower than cookie-based analytics systems when you factor in consent management, legal review, and data loss costs.

How does Sealmetrics differ from other cookieless tools like Plausible or Matomo?​

Key differences:

Sealmetrics: True consentless analytics

  • No cookies
  • No IP storage (competitors store hashed IPs)
  • No consent required
  • 24-month retention without consent
  • Designed to meet CNIL's exemption criteria (self-assessed)

Plausible/Matomo: Cookie-free but still store IPs

  • No cookies (good)
  • Store hashed IP addresses (still personal data)
  • May require consent depending on DPO interpretation
  • 12-month retention typical

Sealmetrics is the only analytics platform that stores zero identifying information, which is what enables genuinely consentless tracking — no legal basis required, rather than a legal basis defended.

Cookieless analytics is the future. Chrome's third-party cookie deprecation (2024-2025), Safari's ITP, Firefox's ETP, and increasing GDPR enforcement make cookie-based analytics increasingly unviable.

By 2026, expect:

  • 90%+ cookie rejection rates in EU
  • Complete third-party cookie elimination
  • Stricter first-party cookie regulations
  • Mainstream adoption of cookieless analytics

Businesses that migrate to cookieless analytics now gain a competitive advantage: complete data capture, while competitors make decisions on the 40-85% their banner happens to let through.

Conclusion: The Case for Cookieless Analytics​

The technical comparison is clear: cookieless analytics provides superior data quality, better legal compliance, faster performance, and lower total cost than cookie-based alternatives.

Cookie-based analytics worked for 20 years, but GDPR, browser privacy features, and user behavior have fundamentally broken the model. Losing 15-60% of your visitor data — unevenly, and skewed toward your most privacy-aware customers — isn't sustainable for businesses that need accurate analytics to make informed decisions.

Sealmetrics pioneered consentless analytics by eliminating both cookies and IP storage, which is what lets it measure every visitor without a consent banner and without needing an Article 6 legal basis at all. This technical approach represents the future of privacy-first analytics.

For businesses operating in EU markets, the migration from cookie-based to cookieless analytics isn't optional—it's essential for competitive survival. Start dual tracking today, compare data accuracy, and see all of your visitors instead of the 40-85% your banner selects for you.

Ready to switch to cookieless analytics? Try Sealmetrics free for 14 days and see 6-9x more visitor data immediately.

Additional Resources​