PostHog
Day 38 after signup
Analytics has changed. Here's what to do about it
Everything builders need to know about analytics
Why it works
- Frame the topic around a timely change, then explain why it matters before offering recommendations.
- Organize a long editorial email into numbered sections so readers can follow distinct ideas.
- Support abstract advice with concrete examples and data points to make each section more useful.
How it is built
- Publication header
- Article title and byline
- Context-setting introduction
- Numbered advice sections
- Reader engagement actions
Email copy
Forwarded this email? Subscribe here for more Analytics has changed. Here's what to do about it Everything builders need to know about analytics now Ian Vanagas Nov 2 READ IN APP In the last few years, analytics has changed as much as coding has, but with nearly none of the fanfare. Products now take in more data, scale faster, and have higher costs. Doing analytics the old way will leave you overwhelmed and underinformed. To help you update your knowledge, here are the things you need to know about how analytics has changed, and the best practices for doing analytics now. 1. Let AI make your analytics proactive Humans can’t handle all the analytics data coming their way. For example, the median company records 9 hours of session replays per month, which leads to 99.8% of session recordings going unopened. AI and automations might do a worse job than humans, but they can do analytics more proactively. This can squeeze more value out of your analytics data that currently goes unused and wasted. Getting AI to do proactive analytics requires giving it direction. It’s not enough to just let AI loose on your analytics data and say “find some fixes.” When given free rein over all your data, agents often get lost or confused. Our proactive analytics agents (we call them Scouts) always have skills to guide them and a clear output format. Examples include: 404 fixer. The skill tells it to “keep posthog.com free of dead URLs. Each run: find 404s that real people actually hit, work out why the URL is dead, and file a report carrying the exact fix so a draft PR opens against posthog.com.” In the 2 months it has run, it has changed 377 files and saved 3000+ broken link requests per week. Customers struggle scanner. Turns “the last 24 hours of observations from one Replay Vision scanner into one Slack message for a customer success manager. The scanner judges one recording at a time. Your job is the cross-session work: refresh the scanner’s account scope, group its findings by account, and write the digest.” Has found query failures as well as customers “repeatedly clicking the recording summary control with no visible output, then abandoning” that led to outreach to those specific customers. Dashboard maintainer. This has “four jobs: surface interesting changes, close what’s missing, maintain the dashboards, and discover dashboards to watch.” One finding was noticing 3,401 skipped evaluations that no insight covered. It built a new chart breaking down the reason that was then added to their main dashboard. 2. Connect your product and business analytics Pre-AI, you could get away with focusing on product analytics. More users and usage was good because it didn’t cost you anything (or cost very little). Just making your product good was good enough, worrying about the business could come later. This isn’t the case anymore. The primary reason for this is that AI costs a lot of money. Devs pay hundreds of dollars for coding agent subscriptions. AI-powered features can cost a lot. Building AI into your product means it’s no longer possible to scale to hundreds of thousands of users with your only expenses being a $15/m server and Stripe fees. Software doesn’t have zero marginal costs anymore. You’ll actually need to figure out what customers will pay for and how to charge them from the start. You can vibe code an app, but you can’t vibe code a business. AI helps here (again) by: Reducing silos. In the past, all your data would be in isolated platforms. Using either PostHog or a bunch of MCP servers enables you to have it all in one place. Reducing complexity. Querying and combining multiple different sources require complex joins and identification. AI can handle them for you. Anyone can do complicated, cross-source investigations now. With data like revenue, subscriptions, account status, ad spend, and AI observability in one place, you can figure out things like: Which features paying customers need, not just free use