About
Ripples Metrics (ripples.sh) is a web and product analytics tool that shows founders of subscription products where their users come from, which ones pay, which ones stay and what each one cost, by joining traffic, search, ad spend, revenue and retention on one screen.
It is made by a small team in Cyprus that runs more than a dozen products of its own and built Ripples to measure them. The numbers in what eight products' analytics look like come from it.
Ripples records every visit from one script tag, or from the iOS, PHP and Python SDKs, and sorts it into a channel and source. Every visitor is scored for signs of automation, and crawlers and automated browsers never reach the counts. You get a channel list you can trust enough to move budget on.
Connect Stripe, Paddle, Polar or Lemon Squeezy and each payment is credited to the person who made it and to the channel that first brought them. Stripe history is imported when you connect, so the numbers go back further than the install. You see revenue and MRR by channel and source, not only signups.
Spend comes in from the Google Ads API and is set against what the customers each channel brought have actually paid since. The result is a payback period per channel: the number of days until it returned what it cost. Spend on other ad platforms can be entered by hand.
Retention cohorts are split by the channel that brought each customer. That shows whether a channel brings people who stay, which is the half of payback a day-one ROAS figure cannot see.
Search terms from Google Search Console and Bing Webmaster Tools arrive per landing page, next to the signups each page produced. Search volume, competition and cost per click are added for the terms you already rank for, so you can tell which pages are worth writing more of.
New visitors, active users, signups and revenue for every product side by side, each against its previous period. It is the view Ripples was built around, and the Portfolio plan covers up to ten products.
An MCP server gives AI assistants the same numbers the dashboard shows, so you can ask which channel paid back last month without opening a browser. It reads the same data as the dashboard, so the two never disagree.
More on the AI side is on the MCP server page.
Plausible and Fathom handle many sites well, but each site is its own traffic dashboard and the number you compare across them is visitors. Ripples was built by a team running more than a dozen products, so its home screen is the comparison itself: visitors, active users, signups and revenue for every product at once. The question it answers first is which product needs you today.
Plausible rotates the identifier it counts visitors with every 24 hours, by design, so a visit on the 1st and a payment on the 30th cannot be tied to the same person. Ripples keeps one record per person and joins the anonymous visitor, the signup and the billing customer into it, through checkout metadata, the email you identify them with, or the customer ID. That is what lets a payment in month three be credited to the ad that brought someone in month one.
Umami and Plausible learn about revenue only when your own code sends an event carrying it, and neither reads ad spend. DataFast, the closest tool to Ripples, imports Meta Ads spend but not Google Ads, and PostHog has revenue and ad spend in separate products that are not joined. Ripples reads payments from your billing provider and spend from the Google Ads API, and joins them into a payback period per channel.
In Google Analytics the same channel can show different numbers depending on whether a report is session-scoped, user-scoped or run through the attribution model. Ripples writes the channel and source that first brought each person onto every event as it arrives, and every report reads that one stamp. Signups, revenue, retention and payback for a channel always describe the same people.
Google Analytics drops traffic from its list of known bots and does not show how much it removed. Ripples scores every visitor for automation and datacenter origin, always removes crawlers and automated browsers, and leaves suspect visitors as a switch you control, with its effect printed beside it. On a small product a few dozen automated visits can be a tenth of the month, which is where this matters most.
PostHog and Mixpanel start from events you plan and reports you build, which is the right trade when someone’s job is data. Ripples ships a fixed set of reports that work from one script tag and a billing connection, with no event taxonomy to design. Running more than a dozen products, that is the only kind of analytics the team behind Ripples could keep set up on all of them.
Each tool is compared in full, with prices and what it does better, on the comparison pages.
It is not built for ecommerce stores, for teams with a data analyst, or for companies that need SSO or SOC 2. What we don't do lists what to use instead.
Ripples Metrics is made by a small product team based in Cyprus. The same people build and run more than a dozen web and iOS products of their own, among them a car running-cost tracker, a Cyprus citizenship exam course, an App Store research tool and an email verification service.
Each of those products had its own analytics, its own billing dashboard and sometimes its own Google Ads account, and working out which ones deserved more time meant reconciling them in a spreadsheet by hand. Ripples started in March 2026 as the internal tool that replaced that spreadsheet, and became a product once it was the first tab the team opened every morning.
The team is engineers and marketing, with no sales staff, so questions to [email protected] are answered by the people who write the code. Follow the work on X (@RipplesMetrics), LinkedIn and GitHub.
Paste one script tag into your site’s head, or add the iOS, PHP or Python SDK, and visits show up as they happen. Then connect billing (Stripe takes a restricted API key and imports your payment history), and optionally Google Ads, Google Search Console and Bing Webmaster Tools.
Signup is self-serve: no credit card, no sales call, no onboarding session. Plans are month to month or yearly, and you can cancel any time.
Email [email protected]. It goes to the people who build Ripples rather than a ticket desk, and Portfolio customers are answered first.
In the dashboard, in a weekly brief written in plain language, and in Claude, Claude Code or Cursor through the MCP server.
Step-by-step setup is in the installation guide, and plans are on pricing.
The words are shared by several unrelated things. Ripples Metrics is none of these:
Ripples Metrics (ripples.sh) is a web and product analytics tool for founders of subscription products. It joins traffic, search, Google Ads spend, revenue and retention on the person, so it can show which channels bring customers who pay and stay, and how long each channel takes to pay back.
A small product team based in Cyprus that runs more than a dozen web and iOS products of its own. Ripples started in 2026 as the tool the team built to measure those products.
No. RipplesMetrics is the data journalism desk of the Nigerian publisher Ripples Nigeria, and Ripple is the payments company behind XRP. Ripples Metrics is an analytics product at ripples.sh with no connection to either.
It is free until your product reaches $1K MRR, as long as billing is connected. After that, Growth is $29 a month for one product and Portfolio is $49 a month for up to ten, and yearly billing takes two months off.
Google Analytics and Plausible measure visits and conversions on your site. Ripples reads revenue from your billing provider and spend from Google Ads, credits both to the channel that first brought each person, and reports payback and retention by channel.
It has no session replay, heatmaps, feature flags, SQL access or self-hosting, and it is not built for ecommerce stores. The page on what Ripples does not do lists each one with the tool we would use instead.
Email [email protected]. It reaches the team that builds the product, and Portfolio customers are answered first.