measuremy.site

Website analytics for indie hackers: what to watch and what to ignore

Sleek laptop showcasing data analytics and graphs on the screen in a bright room.
Photo by Lukas Blazek on Pexels

Start with the question you are trying to answer

Most indie hackers do not need more data. They need faster answers to a few questions: Did anyone find the product? Did they understand it? Did they try it? Where did they leave? A dashboard that shows fifty widgets usually hides those answers under pageview totals and real-time maps.

Before adding more tracking, write down the one decision you are trying to make this week. That might be whether a landing page change helped, which traffic source sends real signups, or whether a new onboarding step causes drop-off. Let that question decide what you instrument.

The core numbers for a small product

For an early product, a lean dashboard is more useful than an exhaustive one. Focus on:

Pageviews can go up while signups go down. Indie hackers should tie almost every metric back to an action that matters for the product.

Track the moments that matter

Analytics should record the few events that map to progress. For a typical indie SaaS, those might be:

For a content site, the important events might be email signup, link click, file download or time spent on a key page. You do not need dozens of events. Start with the ones you would mention in a weekly update to a co-founder.

Build a simple funnel early

A funnel does not need to be complex. A useful early funnel might be landing page visit, signup click, account created, first meaningful action. Look at the drop-off between each step.

The biggest drop-off tells you where to work next. If many visitors reach the signup form but few submit, the form or offer is the problem. If many create accounts but few take the first action, onboarding is the problem. This is more actionable than watching a single number move up or down.

Treat traffic sources as funnels, not scores

A source that sends 5,000 visitors and 10 signups is worse than one that sends 500 visitors and 25 signups. Indie hackers often chase the first source because the volume feels good. Instead, compare sources by the action you care about.

Tag every link you control with UTM parameters so you can see source, medium and campaign. Keep a consistent naming convention. For example, use the same campaign name across a launch tweet, newsletter and forum post so you can compare the whole launch rather than fragmenting it.

Ask your coding agent for answers

If you already use Claude Code, Cursor or Codex, you can let the agent read your analytics instead of clicking through dashboards. Some analytics tools expose an MCP server for this. For example, measuremy.site is a hosted cookieless tracker that connects to those agents over MCP. After a one-time sign-in, you can ask questions like:

This is useful for indie hackers who would rather work in a terminal or editor than switch to yet another web app. The agent can also create funnels and tracked links if the tool supports it.

Review weekly, not hourly

Daily analytics checks tend to produce noise and anxiety. A small site can swing 50 percent day to day without meaning anything. A weekly review is usually enough:

This rhythm keeps analytics connected to decisions instead of turning it into a scoreboard.

Privacy and speed are product decisions

Indie hackers often sell to developers, founders or privacy-conscious users. A heavy analytics setup with cookie banners can slow down the site and create friction before the first visit even loads. A lightweight cookieless tracker can give you visitors, pages, sources, countries, browsers and systems without setting cookies or storing personal data.

That does not automatically remove every legal obligation. Privacy rules vary by jurisdiction and depend on how you use the data, so check your own legal position. But from a user experience perspective, a small script and no consent banner is easier to ship and easier to explain.

A minimal setup checklist

For a new indie project, keep the setup boring:

Avoid building a custom analytics backend, installing a tag manager, or tracking every click before you have a real question to answer. The goal is not to collect everything. The goal is to learn what moves people from visitor to user.

Website analytics for an indie hacker works best when it is small, tied to decisions, and reviewed on a schedule. Watch the few numbers that describe real progress, track the handful of actions that matter, and use your coding agent to pull answers when you already live in a terminal. That leaves more time for building and talking to users, which usually moves the needle more than another dashboard.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog