01 · Synced, read-only
Billing revamp
PostHog · last 30 days
- Errors
- 3 new this week
- Feedback
- "I couldn't find the annual price" · 12 responses
- Rollout
- annual-billing25%
Product health
In sprint planning the most confident voice usually wins, numbers or no numbers. Connect PostHog and Spectr keeps a read-only picture of what is actually happening in production: the errors users hit, the feedback they left in surveys, and which flags are live. It then quotes those numbers, with the date, in the next spec it writes. A claim about what customers keep hitting becomes something you can check.
How PostHog fits in
Spectr syncs PostHog read-only: PostHog errors, survey feedback and feature-flag rollouts. When it drafts the next spec it quotes those numbers with the date they were true, and the Product Health page shows every project's errors in one place.
A read-only Personal API Key plus your PostHog region. The connect dialog names the three scopes it needs so you can issue a narrow key rather than an all-access one.
PostHog Cloud (US or EU) only. Self-hosted instances are deliberately not supported.
In PostHog, create a Personal API Key with project read, query read, and feature-flag read scopes.
In Spectr, open the project, go to Integrations, choose PostHog, and enter the key plus your region.
Pick the PostHog project to track. Product health is one-to-one.
Spectr runs an initial sync. Open the Product Health page, or generate a spec and see the dated evidence in its context.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. Only aggregate counts are stored, and every verbatim is scrubbed of emails and identifiers before it is written. This is a hard rule, not a setting.
PostHog Cloud runs separate US and EU deployments, and a project id only means something on the deployment it came from. Spectr resolves the host from a fixed list rather than accepting an arbitrary one, which is also what keeps a user-supplied URL from becoming a way to make our servers call somewhere they should not.
Sections fail independently and a failed sync never wipes the previous data. A missing scope on feedback does not cost you errors.
Use case
Real error and feedback numbers from PostHog and Sentry, quoted with a date in your specs