Google Ecommerce to MySQL Integration

How Datrise loads Google Ecommerce into MySQL

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

MySQL: Widely used OSS relational engine (InnoDB).

How Google Ecommerce entities map to MySQL

Google Ecommerce entity	MySQL object	Notes
transactions	`google_ecommerce_transactions`	id PK · custom fields → JSON 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 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 Ecommerce 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 Ecommerce 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.