Rybbit Analytics Review: The Open-Source GA4 Challenger
An open-source analytics project doesn’t usually hit 10,000 GitHub stars in under a year. Rybbit did exactly that,…

The internet runs on cookie consent banners. You’ve clicked “Accept All” a thousand times without reading a word, and so has everyone who visits your site. But before you drop a banner on yours, there’s a more useful question to ask: do you actually need one?
Whether a cookie consent banner is legally required depends on three concrete factors — where your visitors are located, whether your tools store cookies on their devices, and whether those tools process data that can identify individuals. Get the analysis right and you might discover you don’t need a banner at all. Get it wrong and you’re exposed to fines of up to 4% of annual global turnover under GDPR Article 83.
This post works through the legal basis, a plain-English decision flowchart, a quick-reference table by tool and region, and the cookieless route that removes the requirement entirely. For the separate technical question of how GA4 and GTM handle consent signals once you’ve made this decision, see Google Consent Mode v2: the GA4 and GTM technical guide.
Most people call this “GDPR” and stop there. That’s imprecise and matters in practice, because two separate pieces of legislation cover different triggers — and understanding the split tells you exactly when consent is required.
The ePrivacy Directive (Directive 2002/58/EC, often called the “Cookie Law”) is the regulation that directly requires consent before you store or access information on a user’s device. Article 5(3) of the Directive is the operative clause: accessing a terminal device — a phone, laptop, browser — without prior informed consent is prohibited, with a narrow exception for technically necessary operations. Consequently, if your analytics tool drops a cookie, the ePrivacy Directive is the rule that requires the banner, not GDPR.
The GDPR then applies on top when that cookie data, or any other collected data, constitutes personal data — identifiers that could directly or indirectly identify a natural person. Under GDPR Article 6, processing personal data requires a lawful basis. For most analytics purposes, that basis is consent. The CJEU’s Planet49 ruling (Case C-673/17) reinforced this in 2019, holding that pre-ticked consent checkboxes are not valid and that cookie consent must be a genuine, active choice.
Together they create a two-part test. Does the tool write or read cookies on the device? Does it process data that can identify an individual — IP addresses, persistent device identifiers, cross-session tracking? If either answer is yes for EU/EEA visitors, you need consent before the tool activates.
The clearest way to map this is by tool and geography. The table below covers the most common analytics setups.
| Tool / Setup | Cookies Set? | Personal Data Processed? | Banner Required (EU/EEA)? | Notes |
|---|---|---|---|---|
| Google Analytics 4 | Yes (_ga, _ga_*) |
Yes — IP, device ID, cross-site | Yes | Data processed by Google in US; GDPR data transfer rules also apply |
| Matomo (cloud, default config) | Yes (first-party) | Yes — IP address, session ID | Yes | Self-hosted cookieless mode changes this — see below |
| Matomo (self-hosted, cookieless + IP anonymization) | No | No — with full anonymization | Usually no | Requires explicit configuration; verify with your DPA |
| Plausible Analytics | No | No | No | Aggregate stats only; no persistent identifiers |
| Fathom Analytics | No | No | No | EU isolation option available for data residency |
| Simple Analytics | No | No | No | Dutch company, servers in EU |
| Embedded YouTube videos | Yes (YouTube tracking) | Yes | Yes | Use youtube-nocookie.com embed to reduce this |
| Facebook Pixel / ad retargeting | Yes | Yes | Yes | Marketing cookies; highest enforcement risk |
| Strictly necessary cookies only (login, cart, CSRF) | Yes | Minimal | No | Exempt under ePrivacy Directive Art 5(3) — session management, security |
Geography matters as much as tool choice. The ePrivacy Directive applies across the EU/EEA. The UK retained equivalent rules post-Brexit via PECR (Privacy and Electronic Communications Regulations). California’s CCPA introduces opt-out rights (not opt-in consent) for residents. Brazil’s LGPD follows consent-based rules closer to GDPR. If your audience is US-only and you have no EU/EEA visitors at all, the ePrivacy consent requirement doesn’t apply — though US state-level privacy law is evolving rapidly.
Run through this sequence before you make any technology or CMP decisions.

_ga, Matomo session IDs), preference cookies, and all marketing/advertising cookies all require prior consent. If yes — banner required. No exceptions.The flowchart makes one thing clear: the fastest and cleanest path to eliminating the banner requirement is eliminating the cookies, not optimizing the banner itself. That’s where the cookieless route comes in.
Cookie-free analytics tools have matured to the point where most websites can get everything they need without setting a single tracking cookie. I’ve tested most of the main options, and the data they provide is genuinely sufficient for content sites, SaaS marketing pages, and small business sites.
Tools like Plausible Analytics and Fathom track visitors using a daily rotating hash derived from the IP address and user agent — a method that produces aggregate statistics without storing persistent identifiers across sessions. No cookie is written. No personal data is retained. Both the ePrivacy Directive and GDPR Article 4‘s definition of personal data are cleanly avoided.
In practical terms, cookie-free tools provide:
What they don’t offer is cross-session user journey tracking, remarketing audience building, or individual user-level path analysis. For e-commerce businesses running product retargeting or advanced attribution models, that gap is real. However, for the majority of sites — publishers, portfolios, service businesses, SaaS landing pages — the absence of those features rarely affects actual decisions. If you’re exploring the broader landscape of privacy-respecting tools, the EU vs. US analytics deep dive covers the field in detail.
If you do need a consent banner — because you run GA4, advertising pixels, or embedded third-party content — you should go in with eyes open about what it costs in data quality.
Consent banner opt-in rates vary significantly by market and banner design. In my experience, a meaningful share of visitors decline consent — and rates run lower in privacy-conscious European markets and on mobile. That means a meaningful proportion of your visitors are systematically absent from your analytics.
| Metric | Cookie-Free Analytics | GA4 with Consent Banner (typical) |
|---|---|---|
| Visitor measurement coverage | ~100% | Partial — opt-in dependent |
| Traffic source accuracy | High, consistent | Skewed — privacy users underrepresented |
| Conversion tracking completeness | Full (for events you define) | Partial — opt-in dependent |
| Page load impact | Minimal (lightweight script) | Banner rendering + script delay |
| Ongoing compliance overhead | None | CMP maintenance, consent records, audits |
The visitors who decline consent aren’t a random sample either. Tech-savvy users, European audiences, and users on privacy-focused browsers like Firefox or Brave decline at significantly higher rates. That creates a systematic bias — the exact audience segment that often matters most for B2B and tech products is the one most underrepresented in your data. This is worth factoring into the tool decision before you commit.
If cookie-based analytics or advertising is unavoidable for your site, the banner you implement must meet the GDPR consent standard. Under GDPR Article 7 and the EDPB’s guidance on consent, valid consent must be freely given, specific, informed, and unambiguous. In practical terms:
For Consent Management Platform options, CookieYes offers a solid free tier for smaller sites, while Usercentrics is better suited to sites running GA4 alongside Google Ads. The technical signal flow from your CMP into GA4 — how Consent Mode v2 works and what it actually sends — is a separate implementation topic covered in the Google Consent Mode v2 guide.
The right answer varies depending on what you actually need from analytics. Based on the sites I’ve worked with, here’s how I’d approach it:
Personal blogs and portfolios. Use Plausible or Fathom. You get pageviews, traffic sources, and popular pages without any legal overhead. There’s nothing in GA4’s feature set that a blog or portfolio site genuinely uses that would justify the banner complexity. The first-party data strategy guide covers the broader picture if you’re thinking about this at a site architecture level.
Small business websites. Cookie-free analytics is the default recommendation. If you run Google Ads, both Plausible and Fathom now offer conversion event tracking that feeds into Google Ads without requiring GA4. Add GA4 only if you have a specific need — multi-touch attribution modeling, audience lists for remarketing — that you can’t meet otherwise.
Content publishers and media sites. The hybrid approach works well: cookie-free analytics as your baseline traffic measurement for editorial decisions, GA4 with consent for the ad-tech layer. This gives you accurate total traffic numbers from the cookieless tool while GA4 serves consented users for monetization reporting.
E-commerce stores. GA4 is hard to avoid if you need product-level conversion funnels and Google Ads integration. Invest in a well-configured CMP, implement Consent Mode v2 for modeled coverage of non-consenting users, and optimize banner design for your audience. Running a cookieless tool alongside gives you an unconstrained traffic baseline to sense-check your consented data.
SaaS and web applications. Separate the marketing site from the app. The marketing site can run cookie-free analytics cleanly. Inside the authenticated app, consent rates are typically much higher — users have already accepted your terms and trust your product, so an in-app consent request for analytics is reasonable and less friction-heavy.
A cookie consent banner is a legal requirement when your site sets non-essential cookies or processes personal data from EU/EEA visitors. It’s not triggered by the existence of a website — it’s triggered by specific technology choices. Change the technology and you change the legal requirement.
The practical upshot: for the majority of content sites and service businesses, switching to cookieless analytics removes the banner requirement entirely, improves data completeness to near-100%, and eliminates ongoing compliance overhead. The tools that support this approach — Plausible, Fathom, Simple Analytics — are mature, reasonably priced, and cover the use cases that actually drive decisions for most sites.
For sites where cookie-based tracking is genuinely necessary, the banner is unavoidable — but it requires proper implementation. Valid consent under GDPR means active opt-in, no dark patterns, cookie blocking before consent, and stored records. That’s the legal floor, and European DPAs are actively enforcing it.