Linking Pendo as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

The Pendo connector syncs your Pendo product data – features, pages, guides, visitors, and accounts – into PostHog, so you can analyze product engagement alongside your other data.

Prerequisites

You need a Pendo integration key, which only Pendo admins can create and view. You'll also need to know which data region your subscription uses (US, US1, EU, Japan, or Australia), since the key is specific to that region.

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

Integration key – create one in Pendo under Settings > Integrations > Integration Keys. Only Pendo admins can view these.
Data region – select the region that matches the domain you log in with (US, US1, EU, Japan, or Australia). The integration key is scoped to a single region.

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.

Every Pendo table is full refresh only. Pendo's list endpoints expose no server-side timestamp filter, and the aggregation endpoint's time filters apply only to event sources, not the visitor and account metadata this source pulls.

Configuration

Option	Type	Required
`Integration key`	password	Yes
`Data region`	select	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`features`	A tagged UI element (button, link, etc.) whose usage Pendo tracks within your application.	Full refresh	—	—
`pages`	A tagged page or screen in your application whose views Pendo tracks.	Full refresh	—	—
`guides`	An in-app message or walkthrough shown to users, such as a tooltip, banner, or lightbox.	Full refresh	—	—
`visitors`	An individual end user of your application, identified by a visitor ID, with their metadata.	Full refresh	—	—
`accounts`	An organization or account that groups visitors together, with its metadata.	Full refresh	—	—

Troubleshooting

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.