Integration · Analytics
PostHog
PostHog is the open-source analytics tool many teams now self-host. Metapolicy reads PostHog events as reward signal and exposes lift readouts as a PostHog data warehouse table so growth analysts can join against their existing PostHog SQL queries.
The contract
What flows in
- PostHog capture events → reward signal via event-name + property mapping
- Cohort and feature-flag definitions ingested for CATE cut parity
What flows out
- LiftReadout rows queryable as a PostHog data warehouse table
- Optional: assignment + propensity written back as person properties
Setup
- 01Generate a PostHog Personal API key with project read + write scope
- 02In Metapolicy dashboard → Integrations → PostHog, paste the key + your PostHog host URL
- 03Map reward events to reward_spec keys
- 04Validate via a PostHog SQL query against the metapolicy_lift_readout warehouse table
Self-hosted considerations
If your PostHog instance is self-hosted behind a VPN, Metapolicy supports an outbound-only configuration: we push lift readouts to your PostHog instance over a long-lived signed connection and never require inbound network access to your warehouse.
This pattern is common in regulated fintech and healthcare deployments; see the security page for the full SOC 2 alignment.
Other analytics integrations
Wire PostHog in a 30-minute call.
We pair with your engineer, ship the integration live, and run the first decision on your stack.