DatriseAI-first ETL

Smartengage to GoodData Integration

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

How Datrise loads Smartengage into GoodData

Datrise syncs Smartengage's subscribers, sequences, broadcasts, tags, message events, and custom fields 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

Smartengage: Messenger and email marketing automation.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Smartengage entities map to GoodData

Smartengage entityGoodData objectNotes
subscriberssmartengage_subscribersid PK · custom fields → flattened columns
sequencessmartengage_sequencesid PK · linked to smartengage_subscribers
broadcastssmartengage_broadcastsid PK · linked to smartengage_subscribers
tagssmartengage_tagsid PK · linked to smartengage_subscribers

FAQ

How does Datrise handle Smartengage'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 Smartengage to GoodData sync stay up to date?

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

Related pipelines

Early access

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