Yandex Metrica to PlanetScale Integration

How Datrise loads Yandex Metrica into PlanetScale

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

Yandex Metrica: Website traffic analytics and session recordings.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Yandex Metrica entities map to PlanetScale

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

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

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

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

Related pipelines

Early access

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