Umami Analytics + Revenue: Connect Privacy-First Traffic to Business Results

Self-Hosted Analytics, Self-Owned Insights

Umami is the go-to analytics tool for developers who want full control. It's open-source, self-hosted, privacy-focused, and lightweight. No cookies, no tracking scripts phoning home to third parties, no GDPR consent banners needed.

But like all standalone analytics tools, Umami answers "what's happening on my site" without connecting it to "what's happening in my business." You can see that traffic from Hacker News spiked last Tuesday, but did those visitors become paying customers? Umami can't tell you that - revenue lives in Stripe.

By overlaying Umami traffic data with Stripe revenue in TotalKPI, you bridge that gap while keeping your analytics stack fully self-hosted and privacy-respecting.

Why Umami Users Care About This

Umami's user base skews toward indie hackers, solo developers, and small SaaS teams. If that's you, you probably:

• Run a lean operation where every marketing dollar matters
• Don't have a data team to build custom dashboards in Metabase or Grafana
• Want actionable insight, not vanity metrics
• Care about owning your data stack end-to-end

Overlaying Umami with revenue gives you the "does this traffic actually make money?" answer without adding complexity to your stack.

What the Overlay Shows

Visitor Count vs Revenue

The most basic and most useful overlay. Plot Umami's daily unique visitors against Stripe's daily revenue. A strong positive correlation means your traffic growth translates to revenue growth. A weak correlation means you're attracting visitors who don't convert - time to investigate why.

Referral Sources vs Conversions

Umami tracks referral sources cleanly. Export or pull traffic data per referrer and overlay each with revenue:

• Organic search traffic vs revenue - Is your SEO driving business?
• Hacker News / Reddit referrals vs revenue - Do viral spikes convert or just bounce?
• Direct traffic vs revenue - Are returning visitors your best customers?
• Newsletter referrals vs revenue - Is your content marketing working?

Most indie hackers discover that viral traffic spikes (HN, Reddit, Product Hunt) have weak revenue correlation, while steady organic search traffic has strong correlation. That's a strategic insight worth knowing.

Page Performance

Track traffic to specific pages - your landing page, pricing page, docs, or blog posts - and overlay each with revenue. Pages that correlate with revenue are your conversion drivers. Pages with high traffic but no revenue correlation might need better CTAs or conversion paths.

Event Tracking

Umami supports custom event tracking. If you track events like "clicked signup button" or "started trial," overlay these event counts with Stripe revenue. This gives you a self-hosted, privacy-respecting conversion funnel analysis.

Setting Up Umami

Via API

Umami exposes a REST API on your self-hosted instance. In TotalKPI:

1. Create an API data source
2. Set the endpoint to your Umami instance's API (e.g., https://your-umami.com/api/websites/{id}/stats)
3. Add your Umami API token in the Authorization header
4. Configure query parameters for the date range and metric type
5. Set JSONPath to extract the value (pageviews, visitors, etc.)
6. Set polling to daily

Since you host Umami yourself, there are no API rate limits to worry about beyond your own server capacity.

Via CSV

Umami's dashboard lets you export data. Download your traffic data for the period you want to analyze and import it into TotalKPI as a CSV data source.

Via Direct Database Query

Since you self-host Umami, you have direct access to its database (typically PostgreSQL or MySQL). You could set up an n8n workflow that queries Umami's database directly, aggregates the metrics you want, and pushes them to TotalKPI via webhook. This is the most flexible approach for power users.

Setting Up Stripe

Connect Stripe via API for live MRR, new customer, or revenue data. Or export historical Stripe data as CSV for the initial analysis.

The Self-Hosted Stack Advantage

One thing that makes the Umami + TotalKPI combination appealing for privacy-conscious developers: you control the entire data pipeline.

• Umami runs on your server - traffic data never leaves your infrastructure
• TotalKPI receives aggregated metrics only - no individual user data, no PII
• Stripe data is pulled via your own API keys

No third-party analytics company has access to your users' browsing behavior. The data that flows to TotalKPI is just numbers: "142 visitors today," "3 new customers," "$1,200 in revenue." Fully aggregate, fully privacy-compliant.

Practical Analysis for Indie Hackers

Here's a concrete workflow for a solo SaaS founder using Umami:

Weekly Review (10 minutes)

1. Open your TotalKPI dashboard
2. Check the Umami visitors vs Stripe revenue overlay - is the correlation holding?
3. Check per-source overlays - any referral source gaining or losing effectiveness?
4. Note any divergences to investigate

Monthly Deep Dive (30 minutes)

1. Review correlation coefficients for all your traffic-revenue overlays
2. Rank your traffic sources by revenue correlation, not just traffic volume
3. Check if any blog posts or landing pages have gained or lost revenue correlation
4. Adjust your content and marketing strategy based on what's actually driving revenue

After Launches (same day)

1. Add a date annotation marking the launch
2. Watch the traffic spike in Umami over the following days
3. Watch whether the spike translates to a revenue bump 1-3 weeks later
4. Compare this launch's conversion pattern to previous launches

Get Started

Start a free trial and connect your self-hosted Umami instance alongside your Stripe data. See which of your traffic actually converts - with full ownership of your analytics stack.

Or explore the demo to see combined charts in action.