MetricDash
deLoginStart for freeGo to app

Rybbit Dashboard & Reporting for Agencies

Some clients don't want Google Analytics on their site — no cookie banner, no data ending up at Google. Rybbit is the answer: cookieless, privacy-friendly web analytics, fully open source, and a modern alternative to Google Analytics. MetricDash's Rybbit integration pulls sessions, unique users, traffic channels, and top pages right into your client dashboard — next to your ad data from Google Ads and Meta Ads.

You connect per client — not via OAuth, but with a Rybbit API key and the numeric site ID from your tracking snippet. If you run Rybbit self-hosted, you also add your instance's host URL. The data appears automatically in the client view's Website tab and the client portal — in exactly the same, provider-agnostic Website view that Google Analytics, Plausible, and Umami feed too. You can switch analytics providers without changing your workflow.

Rybbit is included in every MetricDash plan, and data sources per client account are unlimited — you pay per client, never per connection. Currently free to use in full during the open alpha.

What the Rybbit integration does

Web analytics without a cookie banner

Rybbit tracks in real time and completely cookieless — no consent banner, and no visitor data ending up at Google. That's the argument for clients who deliberately reject Google Analytics or work under strict GDPR requirements. You still deliver every number that matters in the dashboard — just in a privacy-friendly way.

Traffic channels with the primary source highlighted

Rybbit groups traffic into channels — Direct, Organic Search, Referral, Social — in the same GA4 style you already know. MetricDash highlights the dominant source, so you and your client see at a glance what carries the website. No guessing where visitors come from.

One Website tab for every analytics provider

Rybbit data flows into the same Website tab as Google Analytics, Plausible, or Umami — sessions, users, and channels always named and displayed the same way. If a client switches providers, your view stays identical. You don't learn a new tool, you just swap the source.

Engagement and devices at a glance

Pageviews, bounce rate, and average session duration show how intensively the website is used — not just how many people show up. The device split across desktop, mobile, and tablet sits right beside them, and where Rybbit exposes a daily trend, you see that too. That tells you whether a landing page works on mobile or only on desktop.

Rybbit numbers in the client portal with their own login

Your clients get their own read-only login and see their website numbers live at any time — without you granting access to Rybbit or sending screenshots. Dashboard and client portal show the same data, live from the Website tab.

How the connection works

  1. 1Create an API key in RybbitCreate an API key in your Rybbit account. On Rybbit Cloud (app.rybbit.io) this requires a Standard plan; if you run Rybbit self-hosted, there's no such requirement. Also note the numeric site ID from your tracking snippet.
  2. 2Connect per clientAdd the Rybbit connection to the matching client in MetricDash: paste the API key and site ID, plus the host URL for a self-hosted instance. You can combine as many data sources per client as you like — Rybbit plus Google Ads and Search Console, for example.
  3. 3Use the Website tab in the dashboardSessions, users, traffic channels, top pages, and the device split appear automatically in the client view's Website tab — next to the ad data. Nothing to export, nothing to configure.
  4. 4Unlock the client portalOptionally give your client their own portal login — read-only, with the same Rybbit numbers, live and with none of your agency's internals.

The metrics MetricDash pulls from Rybbit

SessionsUnique usersPageviewsBounce rateAvg. session durationTraffic channelsTop pagesDevices (desktop/mobile/tablet)

FAQ

How do I connect Rybbit to MetricDash?

Rybbit doesn't run via OAuth — you connect per client with an API key. You paste the API key and the numeric site ID from your tracking snippet and assign the connection to the matching client account. For a self-hosted instance, you also add the host URL — and there the site ID is alphanumeric.

What sets Rybbit apart from Google Analytics?

Rybbit is cookieless, open source, and privacy-friendly: no consent banner, and visitor data doesn't end up at Google. You can run Rybbit in the cloud or fully self-hosted in the EU. For clients who reject Google Analytics, that's often the deciding factor — and in the dashboard you still get sessions, users, and channels as usual.

What does the Rybbit integration cost?

On the MetricDash side, nothing extra — Rybbit is included in every plan, from the Free plan up to the Agency plan (from €99/month, as of July 2026). Data sources per client account are unlimited: you pay per client, never per connection. Currently even free to use in full during the open alpha. Just note: for API keys, Rybbit Cloud requires a Standard plan — self-hosting has no such gate.

Can my clients view their own Rybbit numbers?

Yes. Through the client portal, every client gets their own read-only login and sees their sessions, users, and traffic channels themselves at any time — without access to your Rybbit account. The analytics data appears in the dashboard and the client portal; it doesn't yet flow into the automatic report emails.

Can I connect a self-hosted Rybbit instance?

Yes. Alongside Rybbit Cloud, MetricDash supports self-hosted instances: you simply add your instance's host URL in addition to the API key and site ID. Self-hosting also has no plan requirement for API keys — the connection works just like it does with Rybbit Cloud.

Connect Rybbit with MetricDash

Currently in open alpha: every feature free, connect unlimited clients, no credit card required.

Start for free