Linking Eppo as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Eppo connector syncs your experimentation and feature flagging data – experiments, metrics, feature flags, bandits, holdouts, and more – from Eppo (Datadog) into PostHog's data warehouse.
Prerequisites
You need an Eppo account with API access. Create an API key under Admin > API Keys in Eppo (this is distinct from SDK/client keys).
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Eppo, you'll need:
- API key – created under Admin > API Keys in your Eppo dashboard. This is a server-side API key, not an SDK or client key.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Most Eppo tables are full refresh only since the API exposes no incremental sync filter. The Experiments table supports incremental sync via the created_date field.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Experiments | An Eppo experiment or holdout: its configuration, variations, metrics, and status. | Incremental, Full refresh | created_date | — |
Metrics | A metric definition used to analyze experiments (e.g. conversion rate, revenue per user). | Full refresh | — | — |
MetricCollections | A named grouping of metrics (e.g. a guardrail metric set) reusable across experiments. | Full refresh | — | — |
FeatureFlags | A feature flag, its variations, allocations, and per-environment configuration. | Full refresh | — | — |
Bandits | A contextual multi-armed bandit that dynamically allocates traffic across variations. | Full refresh | — | — |
Holdouts | A holdout group excluded from one or more experiments for a period, to measure long-run impact. | Full refresh | — | — |
Teams | A team used to group ownership of experiments, metrics, and feature flags. | Full refresh | — | — |
Tags | A tag used to label and filter experiments and feature flags. | Full refresh | — | — |
Audiences | A saved audience definition (targeting rule set) reusable across feature flags and experiments. | Full refresh | — | — |
Environments | A deployment environment (e.g. production, staging) feature flags can be configured per. | Full refresh | — | — |
Troubleshooting
- 401 error: Your Eppo API key is invalid. Create a new API key in your Eppo dashboard and reconnect.
- 403 error: Your API key lacks the required permissions. Check that your key has the appropriate access rights in Eppo.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.