DatriseAI-first ETL

Yandex Metrica to GoodData Integration

AI-first ETL from Yandex Metrica into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Yandex Metrica into GoodData

Datrise syncs Yandex Metrica's sessions, visitors, pageviews, traffic sources, goals, and user parameters into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

Yandex Metrica: Website traffic analytics and session recordings.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Yandex Metrica entities map to GoodData

Yandex Metrica entityGoodData objectNotes
sessionsyandex_metrica_sessionsid PK · custom fields → flattened columns
visitorsyandex_metrica_visitorsid PK · linked to yandex_metrica_sessions
pageviewsyandex_metrica_pageviewsid PK · linked to yandex_metrica_sessions
traffic sourcesyandex_metrica_traffic_sourcesid PK · linked to yandex_metrica_sessions

FAQ

How does Datrise handle Yandex Metrica's custom fields in GoodData?

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

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

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

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