> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking LaunchDarkly as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/launchdarkly

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

Enter your LaunchDarkly access token to pull your projects, environments, feature flags, metrics, members, teams, metric groups, code references, and audit log into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to LaunchDarkly.
3.  Create a personal or service access token in your [LaunchDarkly account settings](https://app.launchdarkly.com/settings/authorization). A token with the **Reader** role grants read access to every resource this source syncs. Copy the **Access token**.
4.  Back in PostHog, enter the access token and click **Next**.
5.  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 LaunchDarkly data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `projects` | Projects in your LaunchDarkly account | Full refresh |
| `members` | Account members | Full refresh |
| `auditlog` | Audit log entries | Full refresh |
| `environments` | Environments, fetched per project | Full refresh |
| `metrics` | Metrics, fetched per project | Full refresh |
| `flags` | Feature flags, fetched per project | Full refresh |
| `metric_groups` | Metric groups, fetched per project | Full refresh |
| `teams` | Teams in your LaunchDarkly account | Full refresh |
| `team_maintainers` | Team maintainers, fetched per team | Full refresh |
| `team_roles` | Team roles, fetched per team | Full refresh |
| `code_ref_repositories` | Code reference repositories | Full refresh |
| `code_ref_statistics` | Code reference statistics, fetched per project | Full refresh |

**Incremental** tables sync only new or updated records on each run. **Full refresh** tables reload all data on each sync.

## Sync limitations

LaunchDarkly's 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 |
| --- | --- | --- |
| `Access token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | A LaunchDarkly project — a container for environments, feature flags, and metrics. | Full refresh | — | — |
| `members` | A member of the LaunchDarkly account. | Full refresh | — | — |
| `auditlog` | An entry in the LaunchDarkly audit log recording a change made in the account. | Full refresh | — | — |
| `environments` | An environment within a LaunchDarkly project (e.g. production, staging). | Full refresh | — | — |
| `metrics` | A metric used to measure the impact of feature flags and experiments. | Full refresh | — | — |
| `flags` | A LaunchDarkly feature flag and its targeting configuration across environments. | Full refresh | — | — |
| `segments` | A segment of contexts that flag targeting rules can include or exclude, per environment. | Full refresh | — | — |
| `flag_statuses` | The status of each feature flag in an environment, with the time it was last requested. | Full refresh | — | — |
| `experiments` | A LaunchDarkly experiment, including its current, draft, and previous iterations. | Full refresh | — | — |
| `holdouts` | A holdout that excludes a percentage of traffic from experiments to measure their overall effect. | Full refresh | — | — |
| `metric_groups` | A metric group: an ordered set of metrics that experiments and guarded rollouts measure together. | Full refresh | — | — |
| `teams` | A team: a group of account members that share custom roles and maintain resources together. | Full refresh | — | — |
| `team_maintainers` | An account member assigned as a maintainer of a team. | Full refresh | — | — |
| `team_roles` | A custom role assigned to a team. | Full refresh | — | — |
| `code_ref_repositories` | A source code repository connected to LaunchDarkly code references. | Full refresh | — | — |
| `code_ref_statistics` | The number of code references to a flag in one repository, on the repository's default branch. | Full refresh | — | — |