Integrations
One read-only key. Every event source via PostHog.
Anku reads from PostHog natively (US & EU, <5 min latency). Segment, Mixpanel, Amplitude, and Snowflake are supported via PostHog ingestion — no write permissions, no tracking scripts, PII scrubbed before synthesis.
Integrations matrix
| Source | Status | Method | Latency |
|---|---|---|---|
| PostHog US (us.posthog.com) | Native | Personal API Key (read-only) | <5min |
| PostHog EU (eu.posthog.com) | Native | Personal API Key (read-only) | <5min |
| Segment (via PostHog) | Supported | Segment destination → PostHog ingestion | <5min after PostHog sync |
| Mixpanel (via PostHog) | Supported | ETL / Segment pipeline → PostHog | <5min after PostHog sync |
| Amplitude (via PostHog) | Supported | ETL / Segment pipeline → PostHog | <5min after PostHog sync |
| Snowflake (via PostHog) | Supported | Reverse ETL → PostHog | <5min after PostHog sync |
How to connect
- Choose region (US/EU) in the Connect modal — must match your PostHog cloud.
- Paste a Personal API Key with read scope for Events, Persons, Insights — Anku probes with a 2s budget before any persistence.
- Run an on-demand diagnostic (under 60s) or wait for the weekly Monday 09:00 UTC scan. Raw event data is processed in-memory and not persisted.
Segment / Mixpanel / Amplitude users: configure their PostHog destination/sync first; then connect PostHog to Anku. See Security for AES-256-GCM and PII scrubbing details.