📊 Analytics
33 appsTraffic counts, product funnels, subscription metrics and link attribution are distinct measurement problems. The large inventory combines all of them. Start with the question you want to answer, then choose the smallest event model that can answer it.
How to choose
Compare event definitions, retention, export and consent requirements. A dashboard should distinguish missing data from zero activity, and your test should include duplicate and delayed events.
Build or buy: where the scope changes
- 7 focused build
- 13 partial replacement
- 13 consider alternatives
A small first-party event pipeline is feasible. Identity resolution, high-volume ingestion and defensible revenue attribution need explicit modeling and ongoing operations.
Existing implementation guides
- Plausible implementation guide — Add a small JS tracker, collect pageviews/events, aggregate by path/referrer/country/device, and show a dashboard.
- Mixpanel implementation guide — Collect a small transparent stream of privacy-conscious first-party events, build funnels and retention views locally, answer a small set of product questions, and retain raw data under the owner's control.
Explore the recorded alternatives
These comparisons cover specific workflows; they do not imply feature parity with every app in this category.
- PostHog — compared in the catalogue with Lucky Orange, Crazy Egg, Mouseflow.
- Umami — compared in the catalogue with Matomo Cloud, Simple Analytics, Umami Cloud.
- GoatCounter — compared in the catalogue with Simple Analytics, Umami Cloud, Fathom Analytics.
- Plausible alternatives
- Mixpanel alternatives
- Amplitude alternatives
Related categories
Category guidance reviewed against the existing catalogue. Counts and verdicts come from the listed app records; product capabilities, prices and setup requirements retain the dates and sources on each guide. These are scoped assessments, not claims of hands-on vendor testing.