How to track your analytics as a solo founder

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

The analytics stack a solo founder actually needs is smaller than the tool market wants you to believe: one product-analytics tool to see what people do, one traffic source to see who arrives, and search data to see how they find you. Pick one of each, make it the single source of truth per product, and ignore the rest until a real question forces your hand. This guide walks the specific tools worth using in 2026, what each is genuinely for, and when to reach for it.

Disclosure: SoleOS, which publishes this guide, makes a dashboard that reads from these tools — so we're not neutral. The advice is meant to hold whether or not you ever plug them into us.

The three questions analytics should answer

Before installing anything, know what you're buying answers to. For a solo founder, useful analytics answers exactly three things:

1. Who is arriving, and from where? — traffic + acquisition.
2. What do they do once here, and where do they drop? — product behavior.
3. How are people finding me in search? — organic discovery.

Almost every tool below maps to one of those. If a tool doesn't clearly answer one of the three for your product, you don't need it yet.

Product analytics: PostHog is the sensible default

For "what do users actually do," PostHog is the pragmatic pick for most indie products. It combines event analytics, funnels, session context, and feature flags in one tool with a usable free tier, so you can instrument the two or three events that matter (signup, activation, the core action, purchase) without wiring up a data warehouse.

How to use it well: don't track 50 events. Track the handful on your activation path and one "aha" event, then build a single funnel from landing → signup → aha → paid. That funnel tells you where money leaks. Everything else is noise until that funnel is healthy.

When you don't need it: a brand-new landing page with no product yet. Until people can do something, product analytics has nothing to measure — traffic + search are enough.

Traffic: GA4, PostHog, or a privacy-first tool — pick one per product

For "who's arriving," you have three reasonable options, and the important rule is to pick one source of truth per product so your numbers never contradict each other:

• Google Analytics 4 — free, universal, and the data most other tools and clients expect. The cost is complexity and a privacy-heavy setup. Good default if you want the widest compatibility.
• PostHog — if you're already using it for product analytics, its pageview data doubles as your traffic source, so you avoid running two tools. Often the cleanest choice for a product-led app.
• Plausible or Umami — privacy-first, lightweight, no cookie banner, simple numbers. Umami is open-source and self-hostable; Plausible is hosted (its API is on the business tier). Ideal if you're GA4-averse or care about a light, private footprint.

The mistake to avoid: running GA4 and PostHog and Plausible and then wondering why three "visitor" numbers disagree. They disagree because they count differently (bots, sampling, de-duplication). Choose one per product and compare like with like.

Search: Google Search Console (and Bing) — free and non-negotiable

For "how do people find me," Google Search Console is free, official, and the only place you see real query data — the exact searches that surface your pages, your click-through rate, and your average position. Bing Webmaster Tools is the same idea for the Bing/ChatGPT-adjacent surface and takes one click to import from Search Console.

How to use it: watch impressions and clicks by query weekly. Rising impressions with low clicks means you're ranking for something but your title/description isn't earning the click — a fast, free fix. This is also where you catch a long-tail page starting to rank, which tells you what to write next.

Mobile: app analytics is a different animal

If you ship a mobile app, "traffic" becomes installs and in-app events, not pageviews. Product behavior comes from a mobile analytics tool (PostHog has a mobile mode for app events), and install/download counts come from App Store Connect and Google Play. Subscription revenue is usually cleaner through RevenueCat than the raw store reports. Don't try to force mobile into a web-analytics shape; measure installs, daily active users, and the in-app funnel instead.

Don't track everything — the four numbers that matter

Instrumentation is not insight. For a solo founder, the weekly scorecard is four numbers, per product:

• Visitors (are people arriving?)
• Signups (are they converting?)
• Active users (are they sticking?)
• Revenue / MRR (is any of it working?)

Vanity metrics — raw pageviews, total registered users, social followers — feel good and change nothing. If a number wouldn't change a decision, stop watching it.

Seeing analytics next to revenue

The catch is that this stack scatters the moment you run more than one product: PostHog in one tab, Search Console in another, GA4 in a third, store dashboards in a fourth — and none of it sits next to the revenue it's supposed to explain. Traffic without revenue is a vanity chart; revenue without traffic hides where growth comes from.

That's the seam SoleOS is built for: it reads traffic (PostHog/GA4), search (Search Console/Bing), and product signals into one portfolio view alongside Stripe and RevenueCat revenue — see exactly what it connects to and reads, or the metrics dictionary for how each number is defined so you never compare two things measured differently. Honestly, if you run one product and live happily in PostHog, you don't need us — the pain (and the value) starts when the tabs multiply.

Frequently asked questions

Do I need GA4 if I already use PostHog?

Usually no. If PostHog is already capturing pageviews for your product, it can be your single traffic source and you avoid running two overlapping tools. Keep GA4 only if you specifically need its ecosystem compatibility (ad platforms, clients who expect it).

What's the most privacy-friendly analytics setup?

Plausible or Umami for traffic (no cookies, no banner; Umami is open-source and self-hostable), plus Search Console for search. You lose some depth versus GA4/PostHog, but for a simple site it's a clean, private, cookie-banner-free footprint.

How many analytics tools should a solo founder run?

Aim for one product-analytics tool, one traffic source, and Search Console — and keep the traffic source consistent per product. More tools mostly buy you contradicting numbers, not more insight.

What analytics matter before I have revenue?

Traffic and search. Until people can buy, product analytics has little to measure and MRR is zero — so focus on whether the right people are arriving (Search Console queries) and whether the landing page converts them to a signup.

Why don't my visitor counts match across tools?

Different tools count differently: bot filtering, sampling, session de-duplication, and time windows all vary. That's why the rule is one source of truth per product — comparing GA4's number to PostHog's is comparing two definitions, not two truths.