Migrate from Google Analytics 4 to Rybbit: Step-by-Step Guide

When Rybbit is the right destination

Teams who want Plausible-class simplicity but with a more polished dashboard and slightly richer event model. Rybbit launched 2024, MIT-licensed, growing fast. Self-host or Cloud (currently free for early users).

Risk: it’s young. Feature parity vs Plausible / Matomo is partial. API stability is not yet guaranteed for production migrations.

Pre-migration checklist

1. Verify production-readiness. Check Rybbit GitHub issues + recent releases. As of mid-2026, it’s stable for non-critical sites.
2. Decide hosting. Cloud (early-user free tier) vs self-host (Docker-compose, Postgres + ClickHouse).
3. Inventory custom events. Rybbit supports custom events with properties.
4. Plan migration of historical data. Rybbit has no GA4 importer — start fresh.

Step-by-step

1. Install (Day 1)

<br />
<script src="https://app.rybbit.io/api/script.js" data-site-id="123" defer></script><br />

2. Map events (Day 1-2)

<br />
// GA4<br />
gtag(‘event’, ‘purchase’, { transaction_id: ‘T_123’, value: 99, currency: ‘EUR’ });</p>
<p>// Rybbit equivalent<br />
window.rybbit.event(‘purchase’, { transaction_id: ‘T_123’, value: 99, currency: ‘EUR’ });<br />

3. Self-host (optional, Day 2-3)

<br />
git clone https://github.com/rybbit-io/rybbit<br />
cd rybbit<br />
docker compose up -d<br />

4. Dual-tag + validate (Days 3-14)

Compare with Parallel-Run Validator. Expected deltas similar to Plausible (Rybbit uses similar bot-filtering approach).

5. Cutover (Day 15)

Common gotchas

• API stability — Rybbit API may change between minor versions. Pin self-host to specific Docker tag, not `latest`.
• Smaller community — Fewer Stack Overflow answers, smaller ecosystem of integrations.
• Documentation gaps — Some advanced features (custom dashboards, multi-org) underdocumented as of 2026-Q2.