DatriseAI-first ETL

Amplitude Azure Synapse

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

How Datrise loads Amplitude into Azure Synapse

Datrise syncs Amplitude's product events, user properties, funnels, cohorts, and retention curves 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

Amplitude: Product analytics source for events, funnels, and cohorts.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Amplitude entities map to Azure Synapse

Amplitude entityAzure Synapse objectNotes
product eventsamplitude_product_eventsdatetime2 events
user propertiesamplitude_user_propertiesid PK · linked to amplitude_product_events
funnelsamplitude_funnelsid PK · linked to amplitude_product_events
cohortsamplitude_cohortsid PK · linked to amplitude_product_events

FAQ

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