DatriseAI-first ETL

Heap to Apache Superset Integration

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

How Datrise loads Heap into Apache Superset

Datrise syncs Heap's events, users, sessions, funnels, segments, and user properties 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

Heap: Autocaptured product analytics and funnels.

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

How Heap entities map to Apache Superset

Heap entityApache Superset objectNotes
eventsheap_eventstemporal columns for time-series charts events
usersheap_usersid PK · linked to heap_events
sessionsheap_sessionsid PK · linked to heap_events
funnelsheap_funnelsid PK · linked to heap_events

FAQ

How does Datrise handle Heap'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 Heap to Apache Superset sync stay up to date?

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

Related pipelines

Early access

Connect Heap 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.