Zentrik + PostHog

1. Confirm that the PostHog project uses UTC.
2. In Zentrik, open Settings → Integrations → Connections and connect PostHog.
3. Approve the read-only project:read and query:read scopes.
4. Open Settings → Integrations → Imports → PostHog and select the project that contains the telemetry.

The connection is read-only. Reconnecting updates the workspace connection instead of creating a second connection.

1. In Imports → PostHog, enter Is successful MCP use growing across workspaces?
2. Choose Every day or Every week.
3. Select Translate question and review the event, filters, comparison window, and evidence minimums.
4. Select Preview with PostHog. A preview does not create an Insight or change an active schedule.
5. Select Start daily import or Start weekly import when the preview shows enough evidence.

The first run creates the current Insight. Later runs update the same Insight when the evidence is supported and keep each observation in Evidence history. You can use the Insight in an idea without accepting it first.

Each run uses the saved measurement plan. A model does not rewrite the query during a run. A changed question creates a new reviewed configuration before it can run.

• Current Insight: read the latest supported result, suggested next step, measurement, and evidence window.
• Evidence history: compare prior observations with the current result. The history remains available when a later run has limited evidence.
• Use in an idea: open the idea flow with the Insight attached, then shape the product work that the evidence supports.
• Cursor: after the product context is shaped in Zentrik, use Zentrik + Cursor to send structured context into build work. PostHog does not send code to Cursor.

• Zentrik reads bounded aggregate results from the selected PostHog project.
• Zentrik does not copy raw events, people, or session recordings.
• Each observation records the evidence window, measurement version, coverage state, aggregate result, and provider receipt.
• The first release supports daily and weekly checks of complete UTC periods.
• Disconnecting stops future reads. Existing Insights and evidence history remain available until a team member removes them through Zentrik.

• Use stable event names and properties in PostHog.
• Keep synthetic or test traffic out of the measured event.
• Preview the question before you activate a schedule.
• Use complete periods. A partial period can make the comparison misleading.
• Link the Insight to an idea or brief when it should change product work. Use Cursor after the work has a clear product decision and acceptance criteria.