Linking Segment as a source

The Segment connector pulls your Twilio Segment workspace configuration, admin, and metadata into the PostHog Data warehouse via the Segment Public API. It does not connect to the event or Profile data plane.

Prerequisites

You need a Twilio Segment workspace and a workspace-scoped Public API token, along with the region your workspace lives in.

Adding a data source

1. In PostHog, go to the Sources tab of the data pipeline section.
2. Click + New source and click Link next to this source.
3. Enter your credentials (see Configuration below) and click Next.
4. 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 Segment, you'll need:

• Region – choose the region your Segment workspace lives in, US (api.segmentapis.com) or EU (eu1.api.segmentapis.com).
• Public API token – create one in your Segment workspace under Settings → Access Management → Tokens.

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_at timestamp). 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.

This source is full refresh only.

Configuration

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Troubleshooting

• If you see an authentication error, your Public API token may be missing or invalid. Create a new Public API token in your Segment workspace settings, then reconnect.
• If you see a forbidden error, your token may be revoked or missing the permissions needed to sync this data. Create a new token with the required access, then reconnect.
• If the connection fails, confirm you selected the region that matches your workspace.

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.