Linking Qualtrics 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 Qualtrics connector syncs surveys, users, groups, 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 Qualtrics datacenter ID and credentials to pull surveys, responses and account metadata.
Find your datacenter ID under Account settings > Qualtrics IDs. It looks like iad1 or fra1. If your brand uses a custom domain, paste the full hostname instead.
The quickest way to connect is an API token from Account settings > Qualtrics IDs. The Qualtrics user needs the "Access API" permission plus read access to the surveys, users, groups, divisions and distributions you want to sync.
You can also connect with an OAuth client: create one under Account settings > Qualtrics IDs, pick the client credentials grant, and give it read access to surveys, survey responses, survey definitions, users, groups, divisions and distributions.
Survey responses sync incrementally on recordedDate. Every other table is a full refresh, because Qualtrics has no modified-since filter on its collection endpoints.
You'll be asked for:
- Datacenter ID: for example
iad1. - Authentication method: choose between API token and OAuth client credentials.
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 Qualtrics tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Datacenter ID | text | Yes |
Authentication method | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
surveys | Every survey in the Qualtrics brand the credentials can see, with its owner and status. | Full refresh | — | — |
users | Users in the Qualtrics brand, with their division, role and account status. | Full refresh | — | — |
groups | Groups used to share surveys, libraries and other assets between Qualtrics users. | Full refresh | — | — |
divisions | Divisions used to partition users and content inside a Qualtrics brand. | Full refresh | — | — |
distributions | Distributions (email, SMS and link invitations) sent for each survey. | Full refresh | — | — |
survey_questions | Question definitions for each survey, from the survey definition API. | Full refresh | — | — |
survey_responses | Recorded responses for every survey, pulled through the Qualtrics response export. | Incremental, Full refresh | recordedDate | — |
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.