Coming from PostHog
Import
Open-source analytics with native hypothesis fields: PostHog experiments become hypothesis_claim + experiment node pairs.
The structural finding
PostHog is the only analytics tool in the series with a native `hypothesis` field on experiments. The adapter extracts it as a separate hypothesis_claim node, making PostHog the most UPG-aware analytics tool in the ecosystem.
What UPG adds
Hypothesis chains: PostHog experiment hypotheses become typed hypothesis_claim nodes connected to experiments and outcomes.
Feature flag traceability: flags become feature nodes, with rollout history traceable to the decisions that drove it.
Open-source alignment: PostHog and UPG are both open. No vendor lock-in on either side.
Schema mapping
The key edge
The single most important semantic relationship this integration enables.
Defined in the UPG specification
Sample import
PostHog experiment with native hypothesis field → UPG hypothesis chain
Roundtrip
Import experiments and feature flags → enrich with UPG opportunity and outcome context → push strategic rationale back to PostHog via API.
- ·Outcome and opportunity context written back to PostHog experiment descriptions
- ·UPG learning node conclusions written back to experiment result summaries
- ·Feature flag rollout rationale linked from UPG decision nodes back to flag metadata
How to import your PostHog data
The PostHog adapter is built and tested. A one-command import via the UPG CLI is in development:
This will fetch your PostHog data, map entity types automatically, and write everything to your graph. Today you can use the Markdown import or the adapter directly in code.
▸ For developers: use the adapter directly
Get started
The PostHog adapter ships in @unified-product-graph/adapters. Install it, then run the import command.
$ npm install -g unified-product-graph
# then import
$ upg import --from notion