Rybbit for SaaS

See the funnel. Then watch the sessions inside it.

Signup funnels, retention cohorts, user profiles, and error tracking on the same dashboard as your traffic: the product-analytics surface without the enterprise setup project.

7-day free trial. Cancel anytime.

One connected surface

Web analytics and product analytics were never two products.

The question is always the same shape: this campaign brought these visitors, who became these trials, who did or didn't stick. Splitting that across two tools is where the answer gets lost.

The usual stack is GA4 for marketing plus a product-analytics suite for the app: two scripts, two event schemas, two logins, and an integration that quietly drifts. Rybbit covers the whole path (first visit to retained account) in one schema, so answering “which channel brings users who stick?” takes one filter. If you're weighing the heavier route, see how Rybbit compares to PostHog and Google Analytics.

There's also the banner problem. Cookie-based analytics inside a product means a consent prompt in your own app and a tracking gap wherever users decline. Rybbit is cookieless and collects no personal data by default, so it's GDPR and CCPA compliant without consent UI. Your onboarding flow stays clean, and the numbers cover everyone. How Rybbit handles privacy.

The first hour

From script tag to signup funnel, before standup ends.

Product analytics tools fail at the instrumentation-plan stage: the meeting happens, the spreadsheet gets made, the events never ship. Rybbit inverts it: autocapture first, naming later.

Steps:

1. Install the script
   One tag in your app and marketing site. Autocapture starts recording pageviews, clicks, form submits, and errors immediately.

2. Identify your users
   Pass your own user IDs for logged-in users, and sessions, events, and errors roll up into per-user profiles.

3. Name the moments
   Add custom events for the steps that define activation, from the browser or server-side with the Node SDK.

4. Build the funnel
   Assemble signup and activation funnels from pages and events in a few clicks, and set goals for the conversions that matter.

Funnels

Find the step that loses trials.

Build a funnel from page paths or custom events in a few clicks (pricing page to trial to activation to paid) and see exactly where the numbers fall off. Then open the sessions that dropped.

• Visited /pricing: 6,720
• Started trial: 1,804
• Invited a teammate: 1,102
• Upgraded to paid: 918

End-to-end conversion: 13.7%

Retention

Know if this month's users stick better than last month's.

Retention cohorts show how each week's new users keep coming back: the first number a SaaS should watch, and usually the last one a web-analytics tool offers.

Ship and measure

Roll it out to 10%. Then prove it worked.

The measure-ship-measure loop usually spans three tools. In Rybbit, the flag that gates the feature and the funnel that judges it live on the same dashboard.

Feature flags

Gate features, roll out gradually, serve remote config, and target variants, without a separate flags vendor or another SDK in the bundle.

Experiments

Run A/B tests on flag variants and measure conversion lift against the goals you already track. No exporting events to a separate testing platform to find out who won.

The ticket says "it doesn't work"

Pull up the user's profile, see their sessions and the error that fired, and watch the replay on Pro. Support conversations get shorter when you can see what the customer saw.

Events from the backend too

Name the product moments that matter with custom events from the browser, or send them server-side with the Node SDK when the moment doesn't happen in a click.

The release-day watch

Errors and web vitals sit next to traffic, so a deploy that breaks a form or slows a page shows up in the same place you're already looking, not in a separate monitoring tab.

Ask your analytics, in your editor

The MCP server puts your analytics in reach of your AI assistant. Ask “what changed in signups this week?” from the same place you write code, and get answers backed by the real numbers.

Your product data, on your terms.

Rybbit is 100% open source under AGPL v3, with API access and data export on every plan. Start on cloud and self-host later, or the other way around, and the funnels, cohorts, and profiles come with you. For a product team, that means the analytics layer is a dependency you can read, patch, and pin.

SaaS questions, answered plainly.

Is Rybbit web analytics or product analytics?

Do I need an instrumentation plan before I see anything?

Can I tie sessions to actual user accounts?

Does Rybbit do feature flags and A/B tests?

Can I see what an individual user experienced?

Which plan do SaaS teams usually need?

Does the tracking script need a cookie banner in our app?

We're on Plausible or Umami. Do we lose our history?

Can we pull the data into our own systems?

Can we self-host it?

Product analytics without the onboarding project.

Funnels, retention, profiles, and replays, all running the afternoon you install the script.