Linking UserVoice 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 UserVoice connector syncs suggestions, forums, users, 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 UserVoice account subdomain and API access token to pull your UserVoice data.
Create a trusted API client under Settings → Channels → Add API Client in your UserVoice Admin Console, then generate an access token to use here. The token has admin-level read access to your account's feedback data.
You'll be asked for:
- Account subdomain: for example
yourcompany. - API access token
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.
Some UserVoice tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Account subdomain | text | Yes |
API access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
suggestions | A feedback idea submitted to a forum, carrying its vote and supporter counts and current status. | Incremental, Full refresh | updated_at | — |
forums | A feedback forum that groups suggestions, optionally scoped to a product or audience. | Incremental, Full refresh | updated_at | — |
users | An end user (contact) who submits, votes on, or comments on feedback. | Incremental, Full refresh | updated_at | — |
comments | A comment left by a user on a suggestion. | Incremental, Full refresh | updated_at | — |
notes | An internal admin note attached to a user or contact record. | Incremental, Full refresh | updated_at | — |
nps_ratings | A Net Promoter Score rating submitted by a user, with the optional follow-up comment. | Incremental, Full refresh | updated_at | — |
tickets | A helpdesk support ticket. Only present on accounts with the Helpdesk feature enabled. | Incremental, Full refresh | updated_at | — |
ticket_messages | An individual message within a helpdesk ticket thread. Requires the Helpdesk feature. | Incremental, Full refresh | updated_at | — |
suggestion_statuses | A configurable status label that can be applied to suggestions (e.g. planned, started, completed). | Full refresh | — | — |
labels | A label used to tag and organize suggestions. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API access 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.