Pendo → GoodData
AI-first ETL from Pendo into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Pendo into GoodData
Datrise syncs Pendo's events, guides, NPS, feature adoption, and account metadata into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Pendo: Product analytics and in-app guidance for SaaS teams.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Pendo entities map to GoodData
| Pendo entity | GoodData object | Notes |
|---|---|---|
| events | pendo_events | date dimensions events |
| guides | pendo_guides | id PK · linked to pendo_events |
| NPS | pendo_nps | id PK · linked to pendo_events |
| feature adoption | pendo_feature_adoption | id PK · linked to pendo_events |
FAQ
How does Datrise handle Pendo's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Pendo to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Pendo
Early access
Connect Pendo to GoodData the easy way
Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.