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

# Linking Fullstory as a source

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

> **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

The Fullstory connector syncs your Fullstory user data 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 Fullstory.
3.  You need an API key from Fullstory. Create one in Fullstory under **Settings** > **Integrations & API Keys** > **API Keys**. A key with at least **Viewer** permission level is sufficient for syncing.
4.  Back in PostHog, paste the API key and click **Next**.
5.  *Optional:* Add a prefix to your table names.
6.  Select the tables you want to sync, set the sync frequency, then click **Import**.

Once the sync is complete, you can start using Fullstory data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `users` | Users from Fullstory's Server API v2 | Full refresh |

## Sync limitations

The Fullstory users table is full refresh only. Fullstory's users listing API doesn't expose an "updated since" filter, so each sync reloads all data.

Session and event data in Fullstory is only available through async Data Export jobs, which aren't supported yet. Additional tables may be added in future updates.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `users` | A tracked end user in Fullstory, identified by your application's user id. | Full refresh | — | — |
| `segments` | A saved Fullstory segment: a named set of filters over users and their activity. | Full refresh | — | — |
| `sessions` | A recorded session of an identified user, with a link to its session replay. | Full refresh | — | — |
| `events` | An event captured by Fullstory, from a segment export of the built-in everyone segment. | Append only, Full refresh | EventStart | — |