ProlyticsPostHog
Connect PostHog to investigate activation, engagement, product paths, and where users stop progressing.
Connect product behaviour
PostHog gives Health and Engine the product evidence needed to understand whether users reach value, return, deepen usage, and continue through important journeys. Connect it when the question begins with activation, engagement, adoption, or conversion.
Go to setup ↓
What this connection helps you answer
- Where do users stop during onboarding, activation, or checkout?
- Are signups becoming active users, or only increasing traffic?
- Which pages, events, and paths changed during the selected period?
- Did product movement align with reliability or billing pressure?
PostHog can answer product questions on its own. Cross-source claims become possible only when the required records can be linked safely.
Setup
- In PostHog, open Settings > General and copy the Project ID.
- Copy the project host, usually
https://us.posthog.comorhttps://eu.posthog.com. - Open Settings > Personal API Keys and create a key for the selected project.
- Grant the required read access listed below.
- Enter the host, Project ID, and personal API key in Prolytics Connections.
Required access
- Project read validates that the selected project exists and is accessible.
- Event definitions read discovers the event names used by your product.
- Property definitions read discovers the metadata available on events and people.
- Query run retrieves the events and aggregate metrics required by Health and Engine.
- Persons read supports identity coverage and user-level questions when the data allows them.
Cohort and path-query access is optional in the current release. Granting it can improve supported cohort and journey analysis, but a missing optional permission does not block the core connection.
After connection
OS inspects the available event and property definitions, then begins preparing the product metrics your data can support. You may be asked to confirm which events represent activation or another important outcome. OS does not assume these definitions because the same event name can mean something different in every product.
Some metrics become useful immediately. Others need a confirmed definition or enough history to establish a comparison. If a trusted event later disappears or changes meaning, the affected metric is marked as untrusted rather than presented as a real decline.