Google Analytics is the wrong tool for your indie project - Statjot - Statjot

If you've ever opened Google Analytics 4, stared at the dashboard for ten minutes, and closed the tab without learning anything useful: you're not bad at analytics. You're using the wrong tool.<br>GA4 was rebuilt from the ground up for enterprise marketing teams running multi-channel attribution models across paid media budgets in the millions. The event-based data model, the exploration reports, the conversion paths, the predictive audiences: none of it was designed for someone who just wants to know whether people are reading the blog post they wrote last week.<br>Yet indie founders reach for GA4 by default because it's free and because they've heard of it. Then they spend three hours reading documentation to understand why their pageview count doesn't match what Cloudflare shows, give up, and make product decisions based on gut feeling anyway.<br>This post is about the gap between what Google Analytics actually is and what indie founders actually need, and what to do about it. I'll cover the specific ways GA4 fails you, the privacy and legal reality that most founders ignore, and a fair review of the alternatives before you decide what to use.<br>I have a stake in this topic, which I'll be transparent about at the end. The alternatives section covers tools I compete with.<br>What GA4 was actually built for<br>Google Analytics 4 replaced Universal Analytics in July 2023. The migration was so disruptive - breaking every existing report, changing fundamental concepts like sessions and bounce rate - that thousands of businesses delayed as long as possible and many didn't finish before the deadline.<br>That disruption wasn't accidental. Google was following money that flows from its biggest customers.<br>Google Analytics 360 - the enterprise version of GA4 - costs around $150,000 per year. The organizations paying that price need things that you do not need:<br>Cross-device tracking that stitches together sessions across Google's signed-in ecosystem<br>Attribution modeling that connects YouTube ads, Display ads, and Search ads to downstream conversions<br>Raw BigQuery export for data science teams running SQL on event streams<br>Predictive audiences ("users likely to churn in 7 days") for remarketing campaigns<br>Consent mode v2 integration with Google's ad measurement infrastructure<br>Server-side tagging for enterprise GTM setups<br>These are legitimate enterprise needs. A retail brand spending $10M/year on Google Ads needs to know which ad creative drove which purchase across which device. The GA4 data model, where everything is an event, sessions are reconstructed after the fact, and users are stitched together across devices using Google's identity graph, exists to serve that use case.<br>That use case is not your use case.<br>When you install GA4 on your indie project, you're deploying infrastructure built for a team of analysts with six-figure tool budgets, pointing it at a product with a few hundred daily active users, then wondering why it feels like overengineering.<br>Because it is.<br>What founders actually need from analytics<br>Before getting into what's wrong with GA4 specifically, it's worth being honest about what a solo founder or small indie team actually checks on a regular basis.<br>I've asked this in a few founder communities and the list is remarkably consistent:<br>How many people visited my site today? This week?<br>Which pages are getting traffic?<br>Where is traffic coming from? (search, Twitter, direct, referral)<br>Is this week better or worse than last week?<br>Did that Product Hunt launch actually drive signups?<br>Is the blog post bringing in search traffic yet?<br>Where do people drop off before signing up?<br>That's it. That's the entire list for most indie projects at the stage where analytics actually matters.<br>You don't need attribution modeling. You don't need predictive churn scores. You don't need a BigQuery export. You need about 40 data points, updated daily, that you can read in under 60 seconds before deciding what to build next.<br>The problem isn't that founders need less data. It's that GA4 optimizes for a completely different set of questions that cost millions of dollars to need to answer.<br>The specific ways GA4 fails indie founders<br>The interface is optimized for analysts, not decisions<br>Open a fresh GA4 property and you're presented with a realtime overview, a reports snapshot that requires configuration, and a left sidebar with nine categories: Reports, Explore, Advertising, Configure, Admin, plus sub-items inside each.<br>The information you actually want - pageviews, top pages, referrers - is buried. The default "Acquisition overview" report shows Sessions (not pageviews), New users (vs. users, two different definitions of the same concept), and Engaged sessions (a metric that didn't exist before GA4 and that most founders couldn't define without Googling).<br>Finding your top pages requires going to Reports → Engagement → Pages and screens. Finding your referrers requires...