Analytics for Indie Hackers: Track What Makes You Money

Most indie hackers install Google Analytics, glance at pageviews once a week, and go back to building. That is not analytics. That is a vanity metric habit dressed up as data-driven decision making.

When you are a solo founder or a two-person team, every hour you spend on marketing needs to count. You cannot afford to pour effort into a channel that drives traffic but zero revenue. You need analytics that answer one question: "Which of my efforts are making me money?"

This guide covers the metrics indie hackers should actually track, the tools that make it practical, and how to set up revenue tracking in under five minutes.

Why indie hackers need different analytics

Enterprise companies can afford to optimize for brand awareness, engagement scores, and multi-touch attribution models that take months to implement. Indie hackers cannot.

When you are bootstrapping a SaaS, course, or digital product, you have three constraints that enterprise teams do not:

1. Limited time — you are the marketer, developer, support agent, and CEO. Analytics setup that takes more than an afternoon is analytics that never gets set up.
2. Limited budget — every marketing dollar matters. You need to know which channels return more than they cost, fast.
3. Revenue is survival — for a VC-backed startup, user growth is a proxy for future revenue. For an indie hacker, revenue is the metric. No revenue, no business.

Traditional analytics tools were built for the enterprise use case. They excel at measuring traffic volume, user flows, and engagement patterns. But they are structurally blind to revenue. Google Analytics can tell you that 2,000 people visited your pricing page last month. It cannot tell you which of those visitors actually paid, or which traffic source brought the paying ones.

This is the gap that kills indie hacker marketing efforts. You optimize for the metrics your tools show you — pageviews, sessions, bounce rate — and ignore the metric that determines whether your business survives.

The metrics that actually matter

Here are the five metrics every indie hacker should track, ranked by importance.

1. Revenue Per Visitor (RPV)

RPV is the average revenue generated per visitor from a given source, page, or campaign. It is the single most important metric for indie hackers because it directly measures traffic quality in dollar terms.

Formula: Total Revenue from Source / Total Visitors from Source

Example: Your blog post about "how to automate invoicing" sends 400 visitors per month. 12 of them convert, generating $588 in MRR. RPV = $1.47 per visitor.

Compare that to your Product Hunt listing, which sent 3,000 visitors last month but only 4 converted, generating $196. RPV = $0.065 per visitor.

The blog post is 22x more valuable per visitor than Product Hunt — even though Product Hunt sent 7.5x more traffic. Without RPV, you would never know this.

For a deeper look at RPV and how it changes marketing decisions, read Revenue Per Visitor: The Metric Your Analytics Is Missing.

2. Conversion rate by traffic source

Overall conversion rate is useful. Conversion rate broken down by source is actionable.

Most indie hackers know their aggregate conversion rate (typically 2-5% for SaaS free trials, 1-3% for paid products). But the variance between sources is enormous:

| Source | Visitors | Conversions | Conversion Rate | |--------|----------|-------------|-----------------| | Organic search | 2,100 | 84 | 4.0% | | Email newsletter | 350 | 28 | 8.0% | | Twitter/X | 1,800 | 18 | 1.0% | | Product Hunt | 5,000 | 25 | 0.5% | | Direct | 900 | 36 | 4.0% |

The email newsletter converts at 16x the rate of Product Hunt. If you are spending 5 hours per week on Twitter content and 30 minutes on your newsletter, your time allocation is inverted.

3. MRR by acquisition channel

If you run a subscription business, knowing which channel your MRR comes from changes everything. It is not enough to know where signups come from — you need to know where paying customers come from.

A channel that drives a high volume of free trial signups but low conversion to paid is worse than a channel that drives fewer signups with high conversion. MRR by channel reveals this.

What to track:

• Which channels produce customers who pay, not just sign up
• Which channels produce customers who stay (low churn)
• Which channels are trending up or down month-over-month

4. Payback period by channel

For indie hackers spending money on ads, sponsorships, or paid content, payback period is critical. How many months does it take for a customer acquired from this channel to generate enough revenue to cover the acquisition cost?

If your Google Ads CAC is $120 and your average plan is $29/month, payback period is 4.1 months. If your Twitter Ads CAC is $85 and same plan price, payback period is 2.9 months. Twitter Ads wins — not because it is cheaper per click, but because it pays back faster.

5. Revenue per page

Which pages on your site actually contribute to revenue? This is different from "which pages get the most traffic" and different from "which pages have the best conversion rate."

Revenue per page tells you which content, landing pages, or product pages are in the journey of visitors who eventually pay. This is the metric that should drive your content strategy.

Lightweight tools that work for indie hackers

The analytics tool landscape is overwhelming. Here is a practical framework for choosing:

What indie hackers actually need:

• Privacy-friendly (no cookie banners eating your conversion rate)
• Quick to install (under 5 minutes)
• Revenue attribution built in (not a bolt-on or requires custom events)
• Small script size (does not slow down your site)
• Affordable at indie scale

What indie hackers do not need:

• Heatmaps (nice-to-have, not essential)
• Session recordings (usually a distraction at early stage)
• Multi-touch attribution modeling (you do not have enough traffic for this to be statistically meaningful)
• Real-time dashboards (vanity feature)

The biggest decision point is whether your analytics tool can natively connect traffic to revenue. If it cannot, you will spend hours every month in spreadsheets trying to manually join data from your analytics tool and your payment provider — and most indie hackers never actually do this work.

Tools like DataSaaS connect directly to Stripe, LemonSqueezy, and Polar, so revenue attribution is automatic. You see RPV, conversion rate by source, and MRR by channel without any manual data wrangling.

How to set up revenue tracking in 5 minutes

Here is the actual process, step by step.

Step 1: Add the tracking script (1 minute)

Add one line to your site's <head>:

<script defer src="https://datasaas.co/js/script.js" data-domain="yourdomain.com"></script>

That is it. No Google Tag Manager. No npm packages. No build step. The script is 4.8KB — smaller than most favicons.

Step 2: Connect your payment provider (2 minutes)

Go to your dashboard, click Integrations, and connect Stripe, LemonSqueezy, or Polar. This is an OAuth flow — you click authorize, and it connects.

Once connected, the integration automatically matches payments to the visitor sessions that preceded them. No manual event tagging required.

Step 3: Verify the connection (2 minutes)

Make a test purchase (or have a friend do it). Within a few minutes, you should see the payment appear in your revenue dashboard, attributed to the correct traffic source.

Step 4: Wait 48 hours, then check your data

Revenue attribution needs a bit of data to be meaningful. After 48 hours, you will have enough to start seeing patterns:

• Which sources have the highest RPV
• Which landing pages appear in the journey of paying customers
• Whether your paid channels are returning more than they cost

The RPV-first marketing framework

Once you have revenue data, here is how to use it to make marketing decisions.

Audit your channels monthly

Every month, pull up your RPV by source and ask:

1. Which channel has the highest RPV? Double down on it. Write more content for that channel. Spend more on that channel. This is your highest-leverage activity.
2. Which channel has the lowest RPV? Either fix it or cut it. If Twitter sends 2,000 visitors per month with an RPV of $0.02, that entire channel generates $40/month. Is that worth 5 hours per week of your time?
3. Which channel is trending? A channel with low absolute RPV but rapidly increasing RPV might be worth investing in. A channel with declining RPV might be dying.

Optimize pages, not just channels

RPV by page reveals which content attracts buyers. Double down on that content type. If your "comparison" blog posts have 5x the RPV of your "tutorial" blog posts, write more comparisons.

Set RPV targets, not traffic targets

Instead of "I want to get to 10,000 pageviews per month," set goals like "I want to increase organic search RPV from $0.80 to $1.20." This forces you to focus on traffic quality — writing content that attracts buyers, not just browsers.

Common mistakes indie hackers make with analytics

Mistake 1: Tracking everything, acting on nothing

Installing five analytics tools, setting up custom events for every button click, and building elaborate Notion dashboards of metrics — but never actually changing behavior based on the data. Pick three metrics. Check them weekly. Make one decision per week based on what you see.

Mistake 2: Optimizing for traffic volume

The most seductive trap in analytics. "We hit 10K pageviews!" feels great. But if those pageviews come from an Hacker News spike of people who will never buy your B2B invoicing tool, they are worth exactly zero.

RPV corrects for this. It is impossible to celebrate a high-traffic, zero-revenue channel when you can see the RPV is $0.00.

Mistake 3: Not connecting revenue data

If your analytics tool and your payment provider are separate systems with no connection, you are flying blind. You can see traffic and you can see revenue, but you cannot see which traffic produces which revenue. This is like running a store where you can count foot traffic and count sales separately, but never know which door the paying customers walked through.

Mistake 4: Over-investing in paid before understanding organic

Many indie hackers start running ads before they understand their organic channels. This is backwards. Organic channels (search, referrals, direct) give you baseline RPV data. Once you know that organic search visitors convert at $1.50 RPV, you know that paying more than $1.50 per click on Google Ads is a losing proposition.

Understand your organic RPV first. Then use it as a ceiling for paid acquisition costs.

Mistake 5: Ignoring email as a channel

In nearly every dataset we have seen, email has the highest RPV of any channel. It is not close. Newsletter subscribers who click through to your site convert at 3-10x the rate of social media visitors. Yet most indie hackers spend 80% of their marketing time on social media and 5% on email.

If you are not tracking RPV by source, you will never see this disparity — and you will keep over-investing in low-RPV social channels.

Mistake 6: Switching tools instead of acting on data

A common pattern: install GA4, feel overwhelmed, switch to Plausible, realize you want more data, add Hotjar, get distracted by heatmaps, switch to Mixpanel. Six months later you have used four tools and made zero marketing decisions based on data.

The tool does not matter as much as the habit. Pick one tool that tracks RPV. Use it consistently. Make one decision per month based on what you see. A simple tool used consistently beats a powerful tool used sporadically.

Mistake 7: Not tracking landing page performance

Most indie hackers look at overall conversion rates. Few look at conversion rates by landing page. This matters because your homepage might convert at 3% while your "pricing" page converts at 8% and your "how it works" page converts at 0.5%.

When you know which pages convert, you can direct more traffic to high-converting pages (through internal linking, ad targeting, or featured content) and fix or remove low-converting pages that waste visitor attention.

Building an analytics habit

The best analytics setup in the world is useless if you do not look at it. Here is a practical routine for indie hackers:

Weekly (10 minutes):

• Check RPV by source. Any significant changes?
• Check conversion rate by source. Any channel improving or declining?
• Scan for anomalies. Did a specific page suddenly start converting well?

Monthly (30 minutes):

• Review MRR by channel. Which channels contributed most to new MRR?
• Compare this month's RPV to last month's. Are your marketing investments paying off?
• Make one strategic decision: increase investment in one channel, decrease in another.

Quarterly (1 hour):

• Full channel audit. Kill anything with consistently near-zero RPV.
• Review content strategy. Which topics attract buyers?
• Set RPV targets for next quarter.

The bottom line

Indie hackers do not need more data. They need the right data — data that connects effort to revenue. Traditional analytics tools measure traffic. Revenue analytics measures what matters.

The shift is simple: stop asking "how much traffic do I get?" and start asking "which traffic makes me money?" Once you can answer that question for every channel, page, and campaign, your marketing decisions become obvious.

Set up revenue attribution once. Check RPV weekly. Cut what does not convert. Double down on what does. That is the entire analytics strategy.

---

Related reading:

• Analytics for Indie Hackers — why DataSaaS is built for bootstrapped founders
• Revenue Attribution Analytics — how traffic-to-revenue tracking works
• LemonSqueezy Integration — connect LemonSqueezy revenue data in 2 minutes
• Revenue Per Visitor: The Metric Your Analytics Is Missing — deep dive into RPV