Google Ecommerce to Supabase Integration

How Datrise loads Google Ecommerce into Supabase

Datrise syncs Google Ecommerce's transactions, products, product impressions, checkout steps, revenue, and refunds into Supabase as a typed table per source entity in your Supabase Postgres. 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 for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Google Ecommerce: Ecommerce reporting from Google Analytics.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Google Ecommerce entities map to Supabase

Google Ecommerce entity	Supabase 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 Supabase?

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

How does the Google Ecommerce to Supabase 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 Supabase 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.