Analytics live. Now we actually know who's reading.
PostHog project 181784 on the EU cluster is now ingesting events from every public surface, with the founder's own machine identifiers excluded so the data set isn't polluted by the operator. Personal API key configured for downstream scripts.
Build day TL;DR
- Date
- Monday, 18 May 2026
- Hook
- Analytics live. Now we actually know who's reading.
- TL;DR
- PostHog project 181784 on the EU cluster is now ingesting events from every public surface, with the founder's own machine identifiers excluded so the data set isn't polluted by the operator. Personal API key configured for downstream scripts.
- Tags
- analytics, infra
- Pull requests
- —
What shipped, and why
Up to this point we had been shipping pSEO surfaces without seeing what readers were actually doing on them — which is how indie SaaS founders quietly waste six months of work. Today PostHog is live end to end, on the EU cluster (project 181784), with the personal API key configured for offline analysis scripts.
Founder traffic is excluded from the data set at the source: distinct_id c7c29d8d-… plus country GR are filtered out so the operator's own browsing doesn't show up as engagement. That matters more than it sounds — without it, the first thirty days of analytics would have been pure self-noise.
The point of getting analytics on now is the same as the diagnostic: before traffic arrives, not after. Once the first cohorts of paid traffic hit, we want clean data from day one, not a retroactive 'huh, that didn't track.'
Linked surfaces
What you should do next
If you're pre-traffic too, wire analytics before launch — not after. The diagnostic checks whether your tracking actually fires.
Adjacent build days
Apply the lesson to your own funnel
Reading the log is half. The other half is checking whether the same constraint is hiding on your live page. The free 90-second Launch Diagnostic returns Hook / Story / Offer scores plus the one thing to rebuild first.