Mailjet to GoodData Integration
AI-first ETL from Mailjet into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Mailjet into GoodData
Datrise syncs Mailjet's messages, contacts, campaigns, delivery events, lists, and templates 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: Email delivery across transactional and marketing sends.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Mailjet entities map to GoodData
| Mailjet entity | GoodData object | Notes |
|---|---|---|
| messages | mailjet_messages | id PK · custom fields → flattened columns |
| contacts | mailjet_contacts | id PK · linked to mailjet_messages |
| campaigns | mailjet_campaigns | id PK · linked to mailjet_messages |
| delivery events | mailjet_delivery_events | date dimensions events |
FAQ
How does Datrise handle Mailjet'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 to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Mailjet
More sources for GoodData
Early access
Connect Mailjet 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.