Conclick vs Umami: An Honest Comparison

What Each Tool Is Actually Built For

Umami is an open-source, privacy-first analytics platform. It gives you pageviews, sessions, referrers, bounce rates, and basic event tracking: clean, fast, and free if you host it yourself. It is a direct, honest replacement for Google Analytics for teams that care about privacy and have the technical chops to run a Postgres or MySQL database somewhere.

Conclick is a paid analytics tool for bootstrapped SaaS and ecommerce founders who want to answer a different question: not just "how many people visited" but "which campaigns, pages, and funnels are making me money, and where am I bleeding it." It is cookieless, GDPR/CCPA-friendly, and installs in about two minutes with a lightweight script. The positioning is deliberately narrow: if you do not have a payment processor connected to your product, about half of Conclick's value is unused.

Where Umami Is the Better Choice

I want to be straight about this, because any comparison page that only talks about where the competitor loses is just a sales pitch wearing a disguise.

• Cost: Umami is free if you self-host. If your traffic is low and your time is cheap, that matters.
• Open source: You own the code. You can audit it, fork it, extend it. For regulated industries or privacy-obsessed teams, that transparency is real.
• Self-hosting control: If you already run infrastructure and want analytics data stored entirely on your own servers, Umami delivers that. Conclick is a hosted SaaS; your data lives on Conclick's servers.
• Simplicity: Umami's dashboard is clean and uncrowded. If you do not need revenue attribution, Conclick's additional depth might feel like noise.
• No vendor lock-in: You can move your Umami data anywhere. With any hosted SaaS, including Conclick, there is a dependency on continued service.

If you are a developer who self-hosts as a matter of principle, or you are running a content site where revenue attribution is irrelevant, Umami is a completely reasonable choice and I would not try to talk you out of it.

Revenue Attribution: The Core Difference

Umami has its own Revenue and Attribution reports, so it can already tie revenue back to a UTM campaign or referrer under a first-click or last-click model. The gap is upstream of the report: per their docs as of July 2026 there is no payment-processor connector, so the only money Umami knows about is money you send it yourself as event data. Nothing reconciles against Stripe, which means refunds, failed charges, disputes, and off-session renewals never arrive at all, and the number in the report drifts away from the number in your bank account.

Conclick connects directly to Stripe, Paddle, Polar, Lemon Squeezy, or Dodo. Once that connection is live, every payment gets attributed back to its source. You can see that your Twitter ads drove 200 visitors but zero paying customers, while a single niche newsletter mention drove 18 visitors and four paying customers. That is the number that changes what you do next week.

Heatmaps, Click Maps, and Funnels

Umami shipped click and scroll heatmap reports in version 3.2.0 in June 2026, so the honest gap here is narrower than most comparison pages will tell you: both tools draw heatmaps. Funnels are where the difference is real. Umami's are manual: you define the steps, it counts completions. There is no automatic detection of where users are dropping and no revenue attached to those drop-offs.

Both tools draw their maps over the real page rather than a wireframe, so that is not the line either. Umami's own docs frame dead clicks as something you go and spot by reading the click map; Conclick classifies rage clicks and dead clicks as their own layers, and lets you narrow the whole map to the visitors who actually paid, which is only possible because the revenue arrived from the processor in the first place. That is a difference of degree over Umami's maps, not of kind, and I would rather say so than pretend the feature does not exist upstream. The funnel feature auto-detects your biggest single drop-off and calculates the revenue lost to it based on your real conversion value. That last part matters: knowing that 62% of users abandon step 3 of your checkout is useful. Knowing that step costs you an estimated $4,200/month in lost MRR is actionable.

Setup, Hosting, and Day-to-Day Use

Self-hosting Umami means provisioning a database, deploying the app (Vercel, Railway, Fly.io, or your own server), keeping it updated, and managing backups. That is maybe a couple of hours upfront and occasional maintenance. Not hard, but it is work, and it is work that compounds when something breaks at 2am.

Conclick is a script tag and two minutes. There is no database to manage. Team sharing, public dashboards, and integrations with Google Search Console and GA4 (for historical import) are all handled. The daily digest (a summary of your key metrics with spikes and milestones sent by email, Slack, Discord, or Telegram) runs automatically without configuration beyond connecting the channel.

Pricing

Umami self-hosted: free. Umami Cloud (their managed offering): has a free tier with limited events and paid plans above that.

Conclick: $9/month, or $7/month billed annually. 14-day free trial, no credit card required. There is also a one-time lifetime deal for founders who prefer to avoid recurring costs. Given that a single additional paying customer typically covers the annual cost, the ROI question usually answers itself within the first month if the revenue attribution is working.

The Honest Recommendation

Pick Umami if: you want full control of your data and are comfortable running infrastructure; you are not taking payments yet or revenue attribution is not relevant to your goals; you need something free and are willing to invest the setup time.

Pick Conclick if: you run a SaaS or ecommerce product and want to know which traffic is actually converting to revenue; you want click maps sitting in the same dashboard as the revenue they produced, without integrating a separate tool; you want a daily digest of spikes and milestones without building it yourself; or you just want analytics that are running and useful in under ten minutes.