Mailjet SMS to Amazon Redshift Integration

How Datrise loads Mailjet SMS into Amazon Redshift

Datrise syncs Mailjet SMS's SMS messages, recipients, delivery statuses, senders, campaigns, and costs into Amazon Redshift as a typed table per source entity. Flexible or custom fields land in SUPER columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMPTZ.

Sync is incremental: Datrise uses COPY from staged files, then a delete-and-insert merge on stable id, so re-runs update only what changed. A DISTKEY on the join id and a SORTKEY on the load timestamp. Redshift performance hinges on dist/sort keys, so Datrise picks them from your entity ids and sync timestamps rather than defaulting to EVEN distribution.

Ideal for AWS-native warehouses already using the Redshift ecosystem.

Endpoints

Mailjet SMS: SMS delivery and message status tracking.

Amazon Redshift: AWS petabyte-scale warehouse with Spectrum.

How Mailjet SMS entities map to Amazon Redshift

Mailjet SMS entity	Amazon Redshift object	Notes
SMS messages	`mailjet_sms_sms_messages`	id PK · custom fields → SUPER columns
recipients	`mailjet_sms_recipients`	id PK · linked to mailjet_sms_sms_messages
delivery statuses	`mailjet_sms_delivery_statuses`	TIMESTAMPTZ events
senders	`mailjet_sms_senders`	id PK · linked to mailjet_sms_sms_messages

FAQ

How does Datrise handle Mailjet SMS's custom fields in Amazon Redshift?

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

How does the Mailjet SMS to Amazon Redshift sync stay up to date?

It runs incrementally — Datrise uses COPY from staged files, then a delete-and-insert merge on stable id.

Related pipelines

Early access

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