DatriseAI-first ETL

Omnisend to Azure Synapse Integration

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

How Datrise loads Omnisend into Azure Synapse

Datrise syncs Omnisend's contacts, campaigns, automations, orders, message events, and segments 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

Omnisend: Ecommerce email and SMS marketing automation.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Omnisend entities map to Azure Synapse

Omnisend entityAzure Synapse objectNotes
contactsomnisend_contactsid PK · custom fields → NVARCHAR(MAX) JSON columns
campaignsomnisend_campaignsid PK · linked to omnisend_contacts
automationsomnisend_automationsid PK · linked to omnisend_contacts
ordersomnisend_ordersid PK · linked to omnisend_contacts

FAQ

How does Datrise handle Omnisend'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 Omnisend 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 Omnisend 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.