DatriseAI-first ETL

Iterable Azure Synapse

AI-first ETL from Iterable into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Iterable into Azure Synapse

Datrise syncs Iterable's users, campaigns, journeys, message events, and experiments into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Iterable: Cross-channel marketing automation and journeys.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Iterable entities map to Azure Synapse

Iterable entityAzure Synapse objectNotes
usersiterable_usersid PK · custom fields → NVARCHAR(MAX) JSON columns
campaignsiterable_campaignsid PK · linked to iterable_users
journeysiterable_journeysid PK · linked to iterable_users
message eventsiterable_message_eventsdatetime2 events

FAQ

How does Datrise handle Iterable's custom fields in Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Iterable to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Iterable to Azure Synapse 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.