DatriseAI-first ETL

Google Analytics 360 PlanetScale

AI-first ETL from Google Analytics 360 into PlanetScale. Governed entities, incremental sync, typed landing tables.

How Datrise loads Google Analytics 360 into PlanetScale

Datrise syncs Google Analytics 360's records, events, and configuration objects 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

Google Analytics 360: SaaS or API data source for analytics and warehouse sync.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Google Analytics 360 entities map to PlanetScale

Google Analytics 360 entityPlanetScale objectNotes
recordsgoogle_analytics_360_recordsid PK · custom fields → JSON columns
eventsgoogle_analytics_360_eventsDATETIME events
configuration objectsgoogle_analytics_360_configuration_objectsid PK · linked to google_analytics_360_records

FAQ

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