Linking Split 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.
Contents
Enter your Split (Harness FME) Admin API key to pull your workspaces, environments, feature flags, segments, and change requests into the PostHog data warehouse.
Prerequisites
You need an Admin API key for your Split organization. Client-side and server-side SDK keys won't work. Creating Admin API keys requires administrator access in Split.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Split.io.
- In Split, go to Admin settings → API keys and create a new API key with the Admin type. Copy the key.
- Back in PostHog, enter the Admin API key and click Next.
- Select the tables you want to sync, set the sync method and frequency, then click Import.
Once the syncs are complete, you can start using Split data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
workspaces | Workspaces in your Split organization | Full refresh |
environments | Environments, fetched per workspace | Full refresh |
traffic_types | Traffic types, fetched per workspace | Full refresh |
feature_flags | Feature flags (splits), fetched per workspace | Full refresh |
segments | Segments, fetched per workspace | Full refresh |
rollout_statuses | Rollout statuses, fetched per workspace | Full refresh |
flag_sets | Flag sets, fetched per workspace | Full refresh |
groups | Groups in your organization | Full refresh |
users | Active members of your organization | Full refresh |
change_requests | Change requests awaiting or past approval | Full refresh |
attributes | Attributes defined on a traffic type, fetched per workspace and traffic type | Full refresh |
feature_flag_definitions | Flag configuration per environment: treatments, targeting rules, and traffic allocation | Full refresh |
segment_keys | Keys that are members of a segment in an environment, one row per segment, environment, and key | Full refresh |
Tables fetched per workspace carry an injected _workspace_id column. Some tables also include additional injected columns such as _environment_id, _traffic_type_id, or _segment_name to identify the parent resource each row belongs to.
Sync limitations
Split's Admin API exposes no server-side timestamp filter on these resources, so every table is full refresh only and reloads all records on each sync.
Configuration
| Option | Type | Required |
|---|---|---|
Admin API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
workspaces | A Split workspace — a container for environments, traffic types, feature flags, and segments. | Full refresh | — | — |
environments | An environment within a Split workspace (e.g. production, staging). | Full refresh | — | — |
traffic_types | A traffic type within a Split workspace — the kind of entity flags are evaluated against (e.g. user, account). | Full refresh | — | — |
feature_flags | A feature flag (split) within a Split workspace. | Full refresh | — | — |
segments | A segment within a Split workspace — a manually curated list of keys flags can target. | Full refresh | — | — |
rollout_statuses | A rollout status available in a Split workspace, used to track a flag's lifecycle stage. | Full refresh | — | — |
flag_sets | A flag set within a Split workspace — a named grouping of feature flags evaluated together. | Full refresh | — | — |
groups | A group of users in the Split organization. | Full refresh | — | — |
users | A member of the Split organization. | Full refresh | — | — |
change_requests | A change request — a proposed change to a feature flag or segment awaiting approval. | Full refresh | — | — |
attributes | An attribute defined on a Split traffic type, used in targeting rules and to describe identities. | Full refresh | — | — |
feature_flag_definitions | The configuration of a feature flag in one environment: treatments, targeting rules, default rule and traffic allocation. | Full refresh | — | — |
segment_keys | A key that is a member of a segment in one environment. One row per segment, environment and key. | Full refresh | — | — |