You know the rate, not the reason
Checkout converts at 2%. You can see which step people leave at, but not what happened on that step.
Plausible is excellent at what it does: a lightweight, cookieless count of visitors, sources and goals. If that’s all you need, stay. This page is for when you need what comes after, such as why people drop off, who it happens to and what changed after a release, without giving up the privacy stance that made you choose Plausible.
Biggest leak: Delivery → Payment (−52%)
Same privacy stance, one question further: 38% of people who left at Delivery hit a form error on the postcode field first.
People pick Plausible because it respects visitors: no cookies, no personal data, no consent banner for analytics. Metrickle’s cookieless mode works the same way.
Visitors are counted on the server with a salted hash of the day, the site, the IP address and the browser, so nobody can be followed from one day to the next. The raw IP address is never stored.
None of these are criticisms of Plausible. They’re questions it was never designed to answer.
Checkout converts at 2%. You can see which step people leave at, but not what happened on that step.
Sign-ups dropped after a deploy and nobody noticed for a week. You want a verdict on key flows after every release.
Your product lives on iOS, Android or Flutter as well as the web, and you want one view of it.
A customer, a procurement form or the European Accessibility Act asks for evidence, and a pageview count isn’t it.
Plausible for traffic, Hotjar for heatmaps, Typeform for surveys, Mixpanel for funnels, and no way to join them.
Activation and retention matter more than visits now, and that means tying events to a signed-in person.
| Plausible | Metrickle | |
|---|---|---|
| Built for | Simple, privacy-friendly web traffic analytics | UX research and conversion: why people drop off, and who for |
| Cookies | None | None in cookieless mode. Standard mode keeps an anonymous id in browser storage for returning visitors and retention |
| Goals and funnels | Goals, custom properties, and funnels and revenue on the Business plan | Goals and funnels with time per step and the biggest leak on every plan, task success rates from Growth |
| Why people leave | Outside its scope | Rage, dead and error clicks, u-turns and form errors. Surveys, heatmaps and replay in standard mode, replay with consent |
| Accessibility | Not measured | Every event carries the device’s accessibility settings, so any funnel can be split by them |
| Releases | Annotations | A verdict on protected flows after every release, and a case with the lost revenue when one breaks |
| Mobile apps | Web-first. Apps can send events through its API | SDKs for iOS, Android, Flutter and React Native, in one portfolio with your websites |
| Open source | Yes, with a self-hosted Community Edition | No. Hosted only |
| Script size | Very small | 11 KB gzipped, deferred |
Plenty of sites should stay on Plausible. Here’s when.
If you need to run analytics on your own servers, or want to read every line, Plausible lets you. Metrickle is hosted only.
Plausible’s script is a fraction of the size, and its single dashboard is easier to read. Metrickle does more, and that has a cost.
Plausible is an EU company with data held in the EU. Metrickle runs on Cloudflare’s network. If EU-only hosting is a requirement, that matters.
Plausible has done one thing well for years. Metrickle is newer, and parts of it, such as native app replay, aren’t built yet.
Counting without storage has the same limits in any tool. A visitor who comes back tomorrow counts as new, so returning visitors and multi-day retention don’t work, and surveys and replay need storage and consent.
Metrickle lets you choose per app. Most teams run their marketing site cookieless, with no banner needed for analytics, and their signed-in product in standard mode, where people have already agreed to terms and retention matters.
Add the Metrickle script tag with data-cookieless next to Plausible’s. Neither interferes with the other.
Visitor counts won’t match exactly: bot filtering and hashing differ between tools. Trends should agree. If they don’t, check both scripts load on every page.
Recreate your Plausible goals as Metrickle goals, then join them into the funnel you couldn’t see before.
Metrickle doesn’t import Plausible data. Export your Plausible stats before you cancel, and keep them for year-on-year comparisons.
Closely, not exactly. Both count visitors with a daily salted hash, but bot filtering and edge cases differ. Run both for a couple of weeks and compare trends rather than exact totals.
In cookieless mode Metrickle stores nothing on the device, so it gives a banner nothing to ask about on its behalf. Whether you need one overall depends on the rest of your site and where you operate. Confirm that with whoever advises you.
No. Metrickle is hosted only. If self-hosting is a requirement, Plausible Community Edition is a good choice.
Yes. They don’t interfere. Some teams keep Plausible on the marketing site and add Metrickle to the product, where funnels, friction and accessibility matter most.
Not today. Export your stats from Plausible before you cancel, and keep them for comparison.
The Free plan covers three apps and 100,000 events a month, with funnels, friction, the accessibility split and one protected flow. Paid plans add volume, replay and heatmaps. See pricing.
Cookieless analytics with funnels, friction and accessibility on top. Free to start, no banner needed for analytics.
Start free