DatriseAI-first ETL

Mailjet SMS to GoodData Integration

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

How Datrise loads Mailjet SMS into GoodData

Datrise syncs Mailjet SMS's SMS messages, recipients, delivery statuses, senders, campaigns, and costs 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

Mailjet SMS: SMS delivery and message status tracking.

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

How Mailjet SMS entities map to GoodData

Mailjet SMS entityGoodData objectNotes
SMS messagesmailjet_sms_sms_messagesid PK · custom fields → flattened columns
recipientsmailjet_sms_recipientsid PK · linked to mailjet_sms_sms_messages
delivery statusesmailjet_sms_delivery_statusesdate dimensions events
sendersmailjet_sms_sendersid PK · linked to mailjet_sms_sms_messages

FAQ

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

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

Related pipelines

Early access

Connect Mailjet SMS 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.