DatriseAI-first ETL

Pendo Amazon QuickSight

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

How Datrise loads Pendo into Amazon QuickSight

Datrise syncs Pendo's events, guides, NPS, feature adoption, and account metadata into Amazon QuickSight as warehouse tables or a SPICE-loaded dataset. Flexible or custom fields land in flattened columns for analyses, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind SPICE or direct query, so re-runs update only what changed. Date-partitioned facts to bound SPICE refresh. QuickSight SPICE is an in-memory copy, so Datrise keeps the backing tables incremental so refreshes stay cheap.

Ideal for AWS-native dashboards with pay-per-session pricing.

Endpoints

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

Amazon QuickSight: AWS serverless BI with SPICE and embedded analytics.

How Pendo entities map to Amazon QuickSight

Pendo entityAmazon QuickSight objectNotes
eventspendo_eventsdate/time fields 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 Amazon QuickSight?

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

How does the Pendo to Amazon QuickSight sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind SPICE or direct query.

Related pipelines

Early access

Connect Pendo to Amazon QuickSight 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.