Google Ecommerce to Neon Integration

How Datrise loads Google Ecommerce into Neon

Datrise syncs Google Ecommerce's transactions, products, product impressions, checkout steps, revenue, and refunds 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 Ecommerce: Ecommerce reporting from Google Analytics.

Neon: Serverless Postgres destination with branching and autoscaling.

How Google Ecommerce entities map to Neon

Google Ecommerce entity	Neon object	Notes
transactions	`google_ecommerce_transactions`	id PK · custom fields → jsonb columns
products	`google_ecommerce_products`	id PK · linked to google_ecommerce_transactions
product impressions	`google_ecommerce_product_impressions`	id PK · linked to google_ecommerce_transactions
checkout steps	`google_ecommerce_checkout_steps`	id PK · linked to google_ecommerce_transactions

FAQ

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