Website analytics for indie hackers: what to watch and what to ignore
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:
- Unique visitors or daily active visitors, not total pageviews.
- Top pages and entry pages.
- Traffic sources grouped by channel or campaign.
- Key events such as signup clicks, trial starts, upgrades and invites.
- One main funnel from landing page to activation.
- Returning visitor share, if your product depends on repeat use.
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:
- Signup click or form submit.
- Account created.
- First project or first import completed.
- Invite sent.
- Upgrade or payment started.
- Upgrade completed.
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:
- Which source sent the most signups this week?
- Where is the biggest drop-off in my current funnel?
- What changed on the day of the traffic spike?
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:
- Look at unique visitors, top sources and key events.
- Check the main funnel for the biggest change.
- Write one sentence about what you learned.
- Pick one change to test next week.
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:
- Add one analytics script tag to your site.
- Define three to five key events.
- Tag your external links with UTM parameters.
- Create one funnel for your main path.
- Set a recurring 20-minute weekly review.
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 demoAdd 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
- Analytics tag checker: Which analytics and pixels a site runs, plus duplicate and broken tags.
- Free UTM link builder: Add utm_source, medium and campaign to any link.
- Website traffic checker: A site's popularity rank and estimated monthly visits.
More from the blog
- How to calculate your website conversion rate, and what to compare it to
- Is my A/B test result significant? A plain-English guide with a worked example
- What is bounce rate, how is it calculated, and is yours a problem?
- How to add a visitor counter to your website or GitHub README
- How much traffic does a website get? How to estimate any site's visits
- How to track QR code scans: count them, and see which poster worked
- How to see how many people clicked your link (without a paid shortener)
- How to check if your Google Analytics 4 tag is installed (and only counting once)
- Why GA4 shows your campaign traffic as Unassigned (and how to fix the links)
- Does your redirect keep your UTM tags? How to check before a campaign goes out
- How I built a self-hosted analytics MCP server on Cloudflare Workers and D1
- UTM tracking explained: what the parameters mean and how to use them
- Conversion funnel analysis for small sites: a practical guide
- Sudden drop in website traffic? A checklist for finding the cause
- What is an MCP server? A plain-English guide for people who run websites
- Vanity Metrics vs Useful Metrics: What to Track
- How to Compare Cookieless Website Tracking Tools
- Why Your Analytics Numbers Differ Between Tools
- When GA4 Is Too Much for a Small Website
- How to keep historical data when switching analytics tools
- How to give an AI agent read-only access to your analytics
- Why developers are connecting agents to production data
- How to recover from a sudden traffic drop
- Direct Traffic Explained: Why So Much Is Unknown
- Why a high bounce rate is not always bad
- High bounce rate: 8 causes and practical fixes
- How to Set Up Traffic Alerts for Sudden Drops
- How to Track Traffic From a Podcast
- How to measure the return on a paid ad campaign
- How to use analytics to decide what to write next
- How the Model Context Protocol Works
- Track File Downloads Without Guesswork
- Adding analytics to a Next.js app without slowing it down
- Core Web Vitals and Traffic: Is There a Link?
- Analytics After Cookies: What Actually Changes
- GDPR and website analytics: a practical guide for small sites
- How to Compare Website Analytics Tools by Privacy
- GA4 Events Explained for Beginners
- How to measure a newsletter send with UTM links
- How to track Hacker News traffic
- Adding Analytics to a Framer Site
- How to ask your coding agent about your analytics
- What Is Bounce Rate and How Is It Calculated?
- A practical website analytics retention policy
- Map your site's funnel from first visit to signup
- What Is a Good Bounce Rate?
- How to automate a weekly traffic report
- A Practical Privacy-Friendly Analytics Checklist
- Adding an MCP server to Claude Code
- How long should you keep analytics data?
- How to Build a Small MCP Server That Actually Helps
- How to Find the Biggest Drop Off in a Funnel
- What Is the Urchin Tracking Module?
- What Microsoft MCP servers actually do
- UTM parameters for email newsletters
- Track Button Clicks Without Google Tag Manager
- How to track the results of a social media post without cookies
- How to track traffic from a GitHub README
- How to measure a product launch without guessing