How to Track Analytics for Your Indie SaaS Without Drowning in Data

I build IndieBob, so this is a post about analytics written by someone whose product includes an analytics page — and I want to be straight about what that page can and cannot tell you, because at forty visitors a day most analytics advice is written for a scale you do not have.

The problem is not that you lack data. It is that a general-purpose tool hands a solo developer the same fifty numbers it hands a marketing department, and at small volumes most of those numbers are noise wearing the costume of a signal.

Why small numbers behave differently

If you get forty visitors a day and your conversion rate is 2%, you are expecting roughly one signup a day. Two on Tuesday and none on Wednesday is not a trend — it is coin flips. But a dashboard will happily draw that as a 100% drop, in red, with an arrow.

This is the actual failure mode. Not "too many metrics" in the abstract, but that day-to-day movement in small numbers is mostly randomness, and a human staring at randomness will always find a story in it. You will change your pricing page because of six visitors.

Two consequences worth taking seriously:

• Look weekly, not daily. At this scale a week is the shortest window with any signal in it, and month-over-month is better still.
• Prefer counts you can name. "Four people signed up, and three of them came from that one post" is a fact you can act on. "Bounce rate is 61%" at forty visitors is not.

The three questions worth answering

Rather than a list of metrics, the useful frame at this stage is three questions in a chain. Each one is only worth asking if the one before it has an answer.

1. Is anyone arriving, and where from? Pageviews, visitors and sessions, and — the part that matters — which pages and which referrers. Not the total; the breakdown. One post out of ten usually does most of the work, and knowing which one tells you what to write next.

2. Does anything they read lead to a signup? A page can be your most-read and convert nobody, which is useful news, not bad news: it means the traffic is real and the page is wrong.

3. Does any of it lead to money? Signups are a proxy. The chain only closes when you can see which page produced a customer.

What IndieBob actually shows you

Plainly, so you can judge whether it answers those three.

Traffic. A first-party tracker you install with a small SDK snippet and a project key: pageviews, visitors, sessions, bounce rate, visit duration and pages per session, plus top pages, referrers and countries. It is your own data on your own project, not a sample.

Revenue. Connect Stripe and IndieBob syncs your products, then shows MRR, customers and transactions on a revenue page. This is where "did it make money" stops being a guess.

Attribution — the part I would actually use. Per page: views to signups to revenue. Per campaign: clicks to signups to revenue to ROI, over 7, 30 or 90 days. That is question three answered directly, and it is the reason the analytics and the revenue data live in the same place rather than in two tools you reconcile by hand.

What it does not do

An earlier version of this post claimed several things that are not true of my own product, so let me be precise about the absences.

• There are no alerts and no thresholds. You cannot ask IndieBob to notify you when a number moves. Nothing emails you. You look, or you do not.
• It does not hide metrics based on your traffic. Bounce rate is on the dashboard whether you have forty visitors or forty thousand — the judgement about whether to trust it at your scale is yours, and this post is the closest thing to help I can offer. There is no preset, no starter pack, and no logic that decides which numbers you are ready for.
• It does not track feature adoption or in-app behaviour. It sees what happens on pages you have the tracker on. "What percentage of users triggered the core action in week one" is a product-analytics question and IndieBob is not a product-analytics tool.
• Stripe is the revenue integration. Not Paddle, not Lemon Squeezy, not app store payouts.

If you need alerting on a churn signal, you need a different tool, and I would rather you learn that here than after installing mine.

Setting it up

Two things, and the second one is optional until you have something to charge for.

1. Add the tracker. Create the project, take the SDK key, put the snippet on your site. Traffic starts landing under the project immediately, next to the posts you publish from IndieBob.
2. Connect Stripe when you have revenue, so the attribution chain can reach all the way to money.

Then leave it alone for a week. Genuinely — the most common mistake is checking a new dashboard six times on day one, when there is not yet enough data for any of it to mean anything.

When to stop looking and start acting

A useful test: if you cannot say what you would do differently based on a number, you do not need to look at that number this week.

At forty visitors a day the honest answer is that almost every week the action is the same — write the next post, aimed at the same kind of reader as the one post that is working. Analytics at this stage is not there to generate a weekly decision. It is there to catch the two or three moments a quarter when something genuinely changes: a post that takes off, a referrer you did not know about, a page that gets traffic and converts nobody.

Those are worth catching. The rest is coin flips, and reading them closely costs you the afternoon you could have spent writing.

Start at indiebob.com — the free plan covers one project, which is all you need to answer question one.