“A number of these can be solved by proper tracking and analytics (posthog/ segment etc) that will help you understand where people are stopping and where to focus. From there if you have enough users A/B test fixes.”
“Analytics-wise, PostHog is solid, but if you’re just testing traction, even a lightweight event counter or Google Analytics can give you enough insight.”
“for analytics posthog is fine if you want to self host but do you really need all that for 5 paying users? i just slapped on a simple event counter at first and it told me everything i needed”
“posthog does have some privacy features like masking text fields and IP anonymization but doesn't fix the fundamental consent issue. sorry there's no clean way around it but maybe framing it differently helps a bit”
“We're sending Claude Cowork OpenTelemetry to Posthog, wanting to see which internal skills people actually use. We've seen Cowork's built-in analytics, which are a nice first step, but we'd like more details if possible (not to mention a better interface for analytics).”
“You have a one-click connect to any account (Gmail, Calendar, Granola, PostHog, etc). You have personal accounts (only accessible by you) and also shared accounts (accessible by everyone in the company).”
“On a large one it is the entire problem, and it stays invisible in your case studies because PostHog and n8n had the structure before they had the volume, so nobody watched it degrade.”
“Worth turning your fix into a permanent CI assertion rather than a one-line patch: intercept outbound requests in the E2E run and fail the build if anything hits Sentry/PostHog ingest endpoints at all, so if someone reintroduces a placeholder token later (config refactor, copy-pasted env template) it breaks the build instead of just adding noise back.”
“tools i now use: tailscale, mux, backblaze, github, git, cloudflare, vercel, astro, launchd, claude code, codex, posthog, remotion, azure, aws, and many more”
“Telemetry is off by default. PostHog is for usage analytics on the open source repo. Audit it if you're skeptical.We make money off enterprise licenses and hosting models.I have strong reason to suspect you either can't read or are a bad actor.”
“live roas and posthog data improve grounding, but approval needs context too. send slack the source window, sample size, proposed change, and rollback condition alongside the copy so the reviewer can judge the recommendation, not just wording.”
“Setup was one command: npx @posthog/wizard. It detects Next.js, installs the SDK, instruments client and server, and creates starter events from your actual app.”
“What actually helped me: watching session recordings (PostHog has this built in) instead of just staring at event counts - you'll catch people getting stuck in ways no dashboard shows you.”