Marketo to Azure Synapse Integration

How Datrise loads Marketo into Azure Synapse

Datrise syncs Marketo's leads, programs, campaigns, email events, lists, and lead scores 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

Marketo: B2B marketing automation and lead management.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Marketo entities map to Azure Synapse

Marketo entity	Azure Synapse object	Notes
leads	`marketo_leads`	id PK · custom fields → NVARCHAR(MAX) JSON columns
programs	`marketo_programs`	id PK · linked to marketo_leads
campaigns	`marketo_campaigns`	id PK · linked to marketo_leads
email events	`marketo_email_events`	datetime2 events

FAQ

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