DatriseAI-first ETL

Google Analytics 360 Neon

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

How Datrise loads Google Analytics 360 into Neon

Datrise syncs Google Analytics 360's records, events, and configuration objects into Neon as a typed table per source entity. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

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

Neon: Serverless Postgres destination with branching and autoscaling.

How Google Analytics 360 entities map to Neon

Google Analytics 360 entityNeon objectNotes
recordsgoogle_analytics_360_recordsid PK · custom fields → jsonb columns
eventsgoogle_analytics_360_eventstimestamptz 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 Neon?

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

How does the Google Analytics 360 to Neon sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Google Analytics 360 to Neon 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.