Google Analytics 4 to MongoDB Integration

How Datrise loads Google Analytics 4 into MongoDB

Datrise syncs Google Analytics 4's events, users, sessions, traffic sources, conversions, and audiences 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

Google Analytics 4: Event-based web and app analytics from Google.

MongoDB: Document database for flexible schemas.

How Google Analytics 4 entities map to MongoDB

Google Analytics 4 entity	MongoDB object	Notes
events	`ga4_events`	BSON Date events
users	`ga4_users`	id PK · linked to ga4_events
sessions	`ga4_sessions`	id PK · linked to ga4_events
traffic sources	`ga4_traffic_sources`	id PK · linked to ga4_events

FAQ

How does Datrise handle Google Analytics 4'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 Google Analytics 4 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 Google Analytics 4 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.