DatriseAI-first ETL

Pendo Apache Superset

AI-first ETL from Pendo into Apache Superset. Governed entities, incremental sync, typed landing tables.

How Datrise loads Pendo into Apache Superset

Datrise syncs Pendo's events, guides, NPS, feature adoption, and account metadata into Apache Superset as governed SQL tables Superset queries directly. Flexible or custom fields land in flattened columns for the explore UI, and timestamps such as created, updated, and status changes are typed as temporal columns for time-series charts.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned tables to keep dashboards responsive. Superset charts run live SQL, so Datrise lands query-friendly, indexed tables rather than wide raw payloads.

Ideal for open-source dashboards over your own database.

Endpoints

Pendo: Product analytics and in-app guidance for SaaS teams.

Apache Superset: Open-source BI for SQL exploration, charts, and dashboard publishing.

How Pendo entities map to Apache Superset

Pendo entityApache Superset objectNotes
eventspendo_eventstemporal columns for time-series charts events
guidespendo_guidesid PK · linked to pendo_events
NPSpendo_npsid PK · linked to pendo_events
feature adoptionpendo_feature_adoptionid PK · linked to pendo_events

FAQ

How does Datrise handle Pendo's custom fields in Apache Superset?

Flexible values are stored as flattened columns for the explore UI, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Apache Superset types.

How does the Pendo to Apache Superset sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the queried tables.

Related pipelines

Early access

Connect Pendo to Apache Superset 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.