Linking Appcues 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.

The Appcues connector syncs your experience settings, segments, segment membership, tags, events, and ingestion filtering rules from Appcues into the PostHog Data Warehouse. Appcues is a user onboarding and product adoption platform.
Prerequisites
You need an Appcues account with API credentials. To create them:
- In Appcues Studio, go to Settings > Integrations > API Keys.
- Create a new API key and give it read access to the experiences you want to sync.
- Copy the API key, API secret, and your Account ID from the account settings.
If you enable the optional export tables, your credentials also need access to the corresponding event or segment membership exports and export job status.
Adding a data source
- In PostHog, go to the sources tab of the data pipeline section.
- Click + New source and then click Link next to Appcues.
- Enter your credentials:
- API key – the API key from Appcues Studio.
- API secret – the API secret from Appcues Studio.
- Account ID – your numeric account ID from Appcues settings.
- Account region – select United States (US) or European Union (EU) depending on where your Appcues account is hosted.
- Click Next.
- Select the tables you want to sync, then click Import.
The events and segment_membership tables are off by default. Enable them during table selection if you need event history or the users in each segment. For events, use append-only syncing with timestamp to add new events on each sync.
The Data Warehouse then starts syncing your Appcues data. You can see details and progress in the data pipeline sources tab.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
API secret | password | Yes |
Account ID | text | Yes |
Account region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
flows | Onboarding flows and their publication settings. | Full refresh | — | id |
flows_v2 | Flows 2.0 and their experience settings. | Full refresh | — | id |
segments | User segments and their creation details. | Full refresh | — | id |
tags | Tags used to organize experiences. | Full refresh | — | id |
pins | Persistent in-app messages and their steps. | Full refresh | — | id |
mobile | Mobile experiences and their steps. | Full refresh | — | id |
launchpads | Launchpad experiences and their settings. | Full refresh | — | id |
banners | Banner experiences and their settings. | Full refresh | — | id |
embeds | Embedded experiences and their settings. | Full refresh | — | id |
nps | NPS 2.0 experiences and their settings. | Full refresh | — | id |
checklists | Onboarding checklists and their completion conditions. | Full refresh | — | id |
ingestion_filtering_rules | The account's allow or deny rules for event, profile, and group property names. | Full refresh | — | account_id |
events | User events, such as flows seen, completed, and dismissed, from the bulk event export. | Append only, Full refresh | timestamp | — |
segment_membership | The users in each segment, from one segment membership export per segment. | Full refresh | — | segment_id, user_id |
Sync behavior and limitations
- Events: PostHog reads bulk exports in one-day time windows, with pagination for large exports. The default initial lookback is 90 days. Each sync excludes the most recent hour to give Appcues time to ingest events. Append syncs add events after the last synced timestamp without updating existing rows or removing duplicates.
- Segment membership: PostHog exports each segment's current members using full refresh. Use
segment_idto join membership to thesegmentstable. This table contains segment and user IDs, not user profile properties or a history of membership changes. - Ingestion filtering rules: This table uses full refresh and contains your account's allow or deny rules for event names and profile or group properties. Check these rules when investigating missing Appcues data. The table is empty if your account has no rules.
- Other tables: Experience settings, segments, and tags use full refresh. Incremental sync isn't supported for these tables because the Appcues API doesn't expose timestamp filters or pagination on its list endpoints.
- User and group profiles aren't available. The Appcues API has no list endpoints for profiles.





