Yandex Metrica to MongoDB Integration

How Datrise loads Yandex Metrica into MongoDB

Datrise syncs Yandex Metrica's sessions, visitors, pageviews, traffic sources, goals, and user parameters into MongoDB as a collection per source entity. Flexible or custom fields land in native nested documents, and timestamps such as created, updated, and status changes are typed as BSON Date.

Sync is incremental: Datrise uses upserts by stable id with updateOne(upsert) on the source primary key, so re-runs update only what changed. Optional sharding on the entity id for large collections. Mongo has no fixed schema, so Datrise keeps field types consistent across documents to avoid mixed-type query surprises.

Ideal for document-oriented apps that want CRM data in their existing Mongo store.

Endpoints

Yandex Metrica: Website traffic analytics and session recordings.

MongoDB: Document database for flexible schemas.

How Yandex Metrica entities map to MongoDB

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

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

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

It runs incrementally — Datrise uses upserts by stable id with updateOne(upsert) on the source primary key.

Related pipelines

Early access

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