Analytics for MVPs: Setting Up Event Tracking With PostHog or Plausible

Most MVP founders install Google Analytics, watch the daily visitor count, and feel like they have data. They don't. Page views tell you how many people showed up. They don't tell you what people did, where they got stuck, or whether they came back.

Setting up real analytics takes a couple of hours. It changes what you can learn from your MVP in the first 30 days.

Why Page Views Alone Won't Tell You Anything Useful

Consider this scenario: 200 people sign up for your MVP in the first week. That feels good. But what happened after they signed up?

• Did they complete onboarding?
• Did they use the core feature at least once?
• Did they come back the next day?
• Did they invite a team member?

Without event tracking, you can't answer any of these. And the answers determine whether your 200 sign-ups represent a successful launch or 200 people who bounced before seeing the value.

Events are the actions users take inside your product. Tracking them tells you where users go, what they do, and — critically — where they stop.

The Three Events Every MVP Should Track From Day One

Before you track everything, track these three:

1. Signed Up — when a new user creates an account. Fire this once, on the server side, after account creation completes successfully. This is your baseline: how many users have you acquired?

2. Activated — when a user completes the action that represents "getting value" for the first time. For a project management tool, this might be "created first project." For a marketplace, "completed first booking." Define this specifically for your product.

The Signed Up → Activated conversion rate is your activation rate. Most MVPs have an activation problem, not an acquisition problem. This metric reveals it.

3. Returned (Day 7 and Day 30 retention) — how many users who signed up are still active a week or a month later. This is your retention signal. If activation is high but retention is low, users are getting an initial taste of value but not finding enough to stay.

Everything else — feature usage, funnel steps, error events — comes after you have these three working.

PostHog vs Plausible vs Mixpanel: Choosing for an MVP Budget

Plausible

Plausible is a privacy-first web analytics tool. It tracks page views, referrers, countries, and basic custom events without cookies or GDPR consent banners.

Best for: MVPs that primarily need to understand traffic sources and page-level behavior. It's the simplest option. The downside: it's not built for complex funnel analysis or per-user event streams.

Pricing: $9/month up to 10K monthly page views. Has a self-hosted option.

PostHog

PostHog is an open-source product analytics platform — think Mixpanel but self-hostable and with a generous free tier on the cloud version. It tracks events, builds funnels, creates user cohorts, and offers session recording.

Best for: MVPs where you need to understand user behavior inside the product, not just traffic. If you care about activation funnels, feature usage, and retention — PostHog is the right choice.

Pricing: Free up to 1M events/month on the cloud version. Self-hosted is free indefinitely.

Mixpanel

Mixpanel is the mature, polished product analytics platform. Excellent funnels, cohort analysis, and A/B testing capabilities.

Best for: Products with enough traffic to justify the complexity and cost. For most MVPs under 10K active users, PostHog covers the same ground for less money.

Pricing: Free up to 20M events/month on the Starter plan.

The MVP recommendation: Start with PostHog. Free tier is generous, the funnel and session recording features are immediately useful, and it's straightforward to self-host later if you want data sovereignty.

Installing PostHog in a Nuxt App

The fastest setup uses PostHog's JavaScript snippet via a Nuxt plugin:

// plugins/posthog.client.ts
import posthog from 'posthog-js'

export default defineNuxtPlugin(() => {
  const posthogClient = posthog.init('<your-project-api-key>', {
    api_host: 'https://app.posthog.com',
    capture_pageview: false // We'll handle this manually for SPA routing
  })

  const router = useRouter()
  router.afterEach((to) => {
    posthog.capture('$pageview', { current_url: to.fullPath })
  })

  return {
    provide: { posthog: posthogClient }
  }
})

Then capture events anywhere in your app:

const { $posthog } = useNuxtApp()

// When a user activates
$posthog.capture('project_created', {
  project_type: type,
  user_plan: plan
})

Keep event names consistent — use snake_case and past tense (project_created, not createProject or Create Project). You'll thank yourself when you have 50 events to query.

Defining Your First Funnel and Interpreting the Drop-offs

A funnel in PostHog is a sequence of events you expect users to complete in order. For a typical SaaS MVP:

Signed Up → Completed Onboarding → Created First Item → Invited Team Member

PostHog will show you what percentage of users complete each step and how many drop off at each transition. The biggest drop-off is where to focus your attention first.

Common patterns:

• Big drop at "Completed Onboarding" — your onboarding is too long or confusing
• Big drop at "Created First Item" — the empty state isn't helping users understand what to do
• Good activation, poor retention — users see the value once but aren't finding reasons to return

The Dashboard to Check Every Week

Keep it simple. One weekly check should answer:

1. How many new users signed up this week?
2. What's the activation rate (Signed Up → Activated)?
3. What's Day 7 retention for users from last week?
4. Are there any unusual drop-offs in the funnel?

Five minutes, once a week. This discipline — more than any analytics sophistication — is what separates founders who learn from their MVPs from those who just watch visitor counts go up and down.

If you want analytics built into your MVP from day one, let's talk.