Linking Unleash 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 Unleash connector syncs features, projects, environments, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
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.
Enter your Unleash instance URL and an Admin API token to sync your feature flags, projects, environments, strategies, segments, and other configuration data.
The instance URL is where you open the Unleash UI - for Unleash cloud it includes your instance name (e.g. https://us.app.unleash-hosted.com/your-instance); for self-hosted it's your server's URL. The token is a personal access token or, on Enterprise, a service account token; it inherits the owner's permissions, and the users table additionally requires the Admin root role. The features table uses the flag search API, which requires Unleash 5.12 or newer.
You'll be asked for:
- Instance URL: for example
https://us.app.unleash-hosted.com/your-instance. - API token
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.
All Unleash tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Instance URL | text | Yes |
API token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
features | A feature flag with its type, project, lifecycle state, and per-environment strategy/rollout status. | Full refresh | — | — |
projects | A project, Unleash's top-level grouping of feature flags with its own members and health metrics. | Full refresh | — | — |
environments | A deployment environment (e.g. development, production) that flags can be enabled in. | Full refresh | — | — |
strategies | An activation strategy definition (built-in or custom) with its parameter schema. | Full refresh | — | — |
segments | A reusable set of strategy constraints that can be referenced by multiple feature flags. | Full refresh | — | — |
context_fields | A context field available for strategy constraints, such as userId or sessionId. | Full refresh | — | — |
tags | A tag applied to feature flags, identified by its tag type and value. | Full refresh | — | — |
tag_types | A tag type, the namespace that groups related tags (e.g. simple, jira). | Full refresh | — | — |
feature_types | A feature flag type (release, experiment, operational, kill-switch, permission) with its expected lifetime. | Full refresh | — | — |
addons | A configured integration (addon) such as a webhook, Slack, or Datadog notifier. Sensitive parameters are masked by the API. | Full refresh | — | — |
users | A user account on the Unleash instance. Requires a token with the Admin root role. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
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.