Yandex Metrica to Neon Integration

How Datrise loads Yandex Metrica into Neon

Datrise syncs Yandex Metrica's sessions, visitors, pageviews, traffic sources, goals, and user parameters into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

Yandex Metrica: Website traffic analytics and session recordings.

Neon: Serverless Postgres destination with branching and autoscaling.

How Yandex Metrica entities map to Neon

Yandex Metrica entity	Neon object	Notes
sessions	`yandex_metrica_sessions`	id PK · custom fields → jsonb 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 Neon?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Neon types.

How does the Yandex Metrica to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Yandex Metrica to Neon 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.