Heimdall
Heimdall ScanOpen Beta
OptionalProObservability

Missing product analytics

Product analytics tracks what users actually do inside your app. Which buttons they click, which pages they spend time on, where they bail. Without it, every product decision is a guess.

#What goes wrong

AI scaffolds rarely add analytics. Founders defer it as a 'later' problem. By the time it is set up, the early-user data is gone forever. There is no way to backfill the funnel for a user who churned three months ago.

#Why it matters

Analytics is what turns guesses into decisions. Which onboarding step loses the most people? Where does the trial-to-paid funnel actually break? Which feature is used by your best customers? Without data, you are reasoning from a sample of yourself.

#How Heimdall checks for this

Heimdall looks for PostHog, Mixpanel, Amplitude, Plausible, Umami, or Vercel Analytics initialization in your project. Either a client provider component or a script tag in the layout counts. The check is optional severity because analytics does not affect users, but missing it costs founders meaningful insight.

#How to fix it

PostHog is the most popular pick for SaaS because it bundles product analytics, session replay, and feature flags. Add the PostHog provider to your root layout, identify users on login, and start by tracking your top three conversion events.

Frequently asked questions

Should I use PostHog or Plausible?

Does analytics require cookie consent?

What events should I track first?

Run this check on your own repo

Heimdall scans your GitHub repo for this and 16 other issues in under a minute.