Linking DX as a source

The DX (getdx.com) connector syncs developer experience data into PostHog: survey snapshots, teams, users, audit events, and DX Fabric scorecards. DX is a developer experience platform that measures engineering team health through surveys and analytics.

Prerequisites

You need a DX account with API access and an organization token. Create the token under Admin > Organization tokens in DX. The scopes you enable on the token determine which tables you can sync.

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 DX, you'll need:

• Organization token: your DX organization API token. See getting your organization token below.

Getting your organization token

1. Sign in to your DX account at app.getdx.com.
2. Go to Admin > Organization tokens.
3. Create a new token with the scopes for the tables you want to sync.
4. Copy the token into PostHog.

Token validation calls the auth.whoami endpoint and does not require any specific table scopes.

Token scopes

Different tables require different token scopes:

The scorecards table requires a DX Fabric subscription. It syncs both published and draft scorecards.

Configuration

Supported tables

• snapshots: survey snapshots with schedules and response counts.
• teams: DX teams with hierarchy and manager information.
• users: users with roles, custom properties, team/group membership, or entity ownership.
• team_audit_events: audit events for changes to DX teams.
• scorecards: published and draft DX Fabric scorecards with checks and scoring rules.

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.

All tables use full refresh only. The DX API does not support server-side date filters.

Troubleshooting

• Invalid organization token: the token was deleted or is invalid. Create a new token in DX under Admin > Organization tokens and update the source credentials.

• Authentication failed (not_authed or invalid_auth): check that your organization token is correct and hasn't expired.

• Access denied (not_authorized): your token doesn't have the required scopes for the tables you're syncing. Check the token scopes section above.

• Scorecards table empty or failing: scorecards require a DX Fabric subscription. Verify your DX account has DX Fabric enabled.

• Empty tables: check that data exists in DX first. For example, verify you have snapshots or teams configured in your DX account.

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.