Analytics
Traffic, behavior, and errors: know what’s happening on your site.
Your site is live, so the next question is whether anyone's using it. There are three layers here, and you almost certainly don't need all three on day one. Start with the first, add the others when a real question comes up.
Layer 1: traffic
“How many people visited?” If you're on Vercel, its built-in Web Analytics answers that in five minutes, and it's privacy-friendly enough to skip the cookie banner.
- 1
In your Vercel project, open the Analytics tab and click Enable. The free Hobby tier is pre-selected.
- 2
It wants a small package added to your code. Delegate it:
Your agentAdd Vercel Web Analytics to this project, then commit and push so it deploys. - 3
Once the deploy is green, open your live site, click around, and refresh the Analytics tab. Within minutes: visitors, page views, top pages. (That first visitor is you. Still counts.)
Layer 2: behavior
The day you care less about how many and more about what they did, add PostHog. It tracks the events you define (“clicked signup,” “finished onboarding”), shows you where people drop off, and can replay real sessions so you watch someone get stuck. Generous free tier, one prompt to wire up: “add PostHog and track when someone completes the main action in this app.”
Layer 3: errors
Analytics tells you what people did. Sentry tells you what broke on them: the error you'd otherwise never hear about because the user just left. It captures crashes with the full context to reproduce them, and pings you when something new starts failing in production. Also a free tier, also one prompt. This is the difference between “a user emailed that it's broken” and “I fixed it before anyone noticed.”
That completes the loop this guide promised: build, checkpoint, push, live, and measured. Everything after this point (the Level up group) is about making your app more capable: pulling in outside data, letting people sign in, and the agentic machinery that makes it all feel effortless.
