DatriseAI-first ETL

Smartengage Metabase

AI-first ETL from Smartengage into Metabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Smartengage into Metabase

Datrise syncs Smartengage's records, events, and configuration objects into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Smartengage: SaaS or API data source for analytics and warehouse sync.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Smartengage entities map to Metabase

Smartengage entityMetabase objectNotes
recordssmartengage_recordsid PK · custom fields → flattened columns for the question builder
eventssmartengage_eventstemporal columns for trends events
configuration objectssmartengage_configuration_objectsid PK · linked to smartengage_records

FAQ

How does Datrise handle Smartengage's custom fields in Metabase?

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

How does the Smartengage to Metabase sync stay up to date?

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

Related pipelines

Early access

Connect Smartengage to Metabase 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.