Linking Gainsight PX 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 Gainsight PX connector syncs accounts, users, features, 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.
Connect Gainsight PX with your project's API key. Generate a key with Read access under Administration → REST API in Gainsight PX, then pick the region your subscription is hosted in.
All tables are synced as full refresh - Gainsight PX's list endpoints don't expose an "updated since" filter.
You'll be asked for:
- API key
- Region: choose between US (api.aptrinsic.com), EU (api-eu.aptrinsic.com) and US2 (api-us2.aptrinsic.com).
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 Gainsight PX tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | Companies (accounts) tracked in Gainsight PX, aggregating the users that belong to them. | Full refresh | — | id |
users | Individual end users tracked in Gainsight PX, with their profile and engagement attributes. | Full refresh | — | id |
features | Product features tagged in Gainsight PX for adoption tracking. | Full refresh | — | id |
segments | User/account segments defined in Gainsight PX. | Full refresh | — | id |
engagements | In-app engagements (guides, surveys, dialogs) configured in Gainsight PX. | Full refresh | — | id |
articles | Knowledge Center articles published in Gainsight PX. | Full refresh | — | id |
kc_bots | Knowledge Center bots configured in Gainsight PX. | Full refresh | — | id |
page_view_events | Page view events captured by the Gainsight PX tag, one row per page viewed. | Incremental, Full refresh | date | eventId |
session_events | Session initialized events, one row per user session started. | Incremental, Full refresh | date | eventId |
engagement_view_events | Engagement view events: views of and interactions with in-app engagements (guides, surveys, dialogs). | Incremental, Full refresh | date | eventId |
feature_match_events | Feature match events, one row each time a user uses a tagged feature. | Incremental, Full refresh | date | eventId |
segment_match_events | Segment match events, one row each time a user matches a segment. | Incremental, Full refresh | date | eventId |
custom_events | Custom events your product sends to Gainsight PX, with the event name and its attributes. | Incremental, Full refresh | date | eventId |
identify_events | Identify events, one row each time a user is identified to Gainsight PX. | Incremental, Full refresh | date | eventId |
survey_responses | Survey responses (NPS, CES, rating, boolean and multiple-question surveys) users submitted to in-app surveys. | Incremental, Full refresh | date | eventId |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.