Linking Trustpilot 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 Trustpilot connector syncs your reviews data from Trustpilot into PostHog's data warehouse: your business profile with its TrustScore, service reviews, and product reviews. Once synced, you can query and join this data alongside your product analytics and other warehouse sources.
Prerequisites
You need a Trustpilot Business account with API access and an API application. Service and product reviews come from Trustpilot's private APIs, so the connector needs both the application's key and its secret.
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.
When linking Trustpilot, you'll need:
- API key and API secret: create an API application in your Trustpilot Business account, then copy its key (client ID) and secret (client secret). See Trustpilot's developer documentation for how to create an application.
- Business unit domain or ID: your website domain exactly as it appears on your Trustpilot profile (for example
example.com), or your business unit ID. Pasting your Trustpilot review page URL also works.
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.
Service reviews support incremental syncs based on when a review was created. Edits to already synced reviews, such as an updated star rating or a new company reply, are only picked up by a full refresh. Product reviews and the business profile always sync as a full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
API secret | password | Yes |
Business unit domain or ID | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
business_unit | The Trustpilot profile of the connected business: its identifying domain, review counts and current TrustScore. One row, replaced on every sync. | Full refresh | — | — |
service_reviews | Service reviews left for the business unit, including the reviewer, star rating, review text and any company reply. Synced from the private reviews endpoint, so rows include customer email and order reference. | Incremental, Full refresh | createdAt | — |
product_reviews | Product reviews left for the business unit's products. Synced from the private product reviews endpoint, so rows include the reviewed product, the consumer's email and the review state. | Full refresh | — | — |
Troubleshooting
- Business unit not found: enter your domain exactly as it appears on your Trustpilot profile. If your profile uses a different domain than your website, use your business unit ID instead.
- Credentials rejected: check the API key and secret in your Trustpilot Business account, and confirm your Trustpilot plan includes API access.
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.