Google Analytics 4 to MySQL Integration

How Datrise loads Google Analytics 4 into MySQL

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

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

MySQL: Widely used OSS relational engine (InnoDB).

How Google Analytics 4 entities map to MySQL

Google Analytics 4 entity	MySQL object	Notes
events	`ga4_events`	DATETIME/TIMESTAMP 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 MySQL?

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 MySQL types.

How does the Google Analytics 4 to MySQL 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 Google Analytics 4 to MySQL 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.