
Primers · Published October 16, 2026
Web analytics vs product analytics
How marketing-site analytics differs from in-app product analytics — questions, data model, script weight, and which AnalyticsVS tools fit each job.
Updated
Quick answer
Quick answer
Web analytics answers how people find and browse your site (pages, referrers, campaigns). Product analytics answers what signed-in users do inside the product (activation, funnels, retention). Plausible and Fathom are web-first; PostHog is product-first; GA4 can span both with more setup.
Two jobs, two dashboards
If your team asks "which blog posts drive signup clicks?" you need web analytics.
If your team asks "what percent of new workspaces invite a teammate in seven days?" you need product analytics.
Using one tool for both is possible (GA4, PostHog) but not free — instrumentation, privacy review, and script weight all go up. Many teams run a light web tool on the marketing site and a product tool in the app.
Data model differences
Web tools optimize for URLs, referrers, UTM campaigns, and goals.
Product tools optimize for named events, user/account identity, funnels, retention, and often session replay or flags.
See Pageviews vs Events: Which Should You Track? for the vocabulary bridge.
Cost and script weight
Lightweight web tags (Plausible, Fathom, DataFast) sit in our light script performance cluster. PostHog’s default web SDK is much heavier because it ships product capabilities — fine in an app shell, often excessive on a brochure homepage.
Price units differ too: pageview tiers vs event volume. Check the pricing calculator.
How to pick a lane
- List the three decisions you make weekly from analytics.
- If they are traffic/campaign decisions → start web-first (Plausible vs PostHog explains the mismatch).
- If they are activation/retention decisions → start product-first (GA4 vs PostHog).
- Add a second tool only when the first lane is clearly insufficient.