Yandex Metrica to Azure Synapse Integration

How Datrise loads Yandex Metrica into Azure Synapse

Datrise syncs Yandex Metrica's sessions, visitors, pageviews, traffic sources, goals, and user parameters 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

Yandex Metrica: Website traffic analytics and session recordings.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Yandex Metrica entities map to Azure Synapse

Yandex Metrica entity	Azure Synapse object	Notes
sessions	`yandex_metrica_sessions`	id PK · custom fields → NVARCHAR(MAX) JSON columns
visitors	`yandex_metrica_visitors`	id PK · linked to yandex_metrica_sessions
pageviews	`yandex_metrica_pageviews`	id PK · linked to yandex_metrica_sessions
traffic sources	`yandex_metrica_traffic_sources`	id PK · linked to yandex_metrica_sessions

FAQ

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