Source connector
Google Ecommerce connector
Google Ecommerce integration for databases, warehouses and BI tools
Ecommerce reporting from Google Analytics. Datrise captures Google Ecommerce entities such as transactions, products, product impressions, checkout steps, revenue and refunds, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.
Of the 6 objects, 3 sync as upserts keyed on the primary key and 3 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `google_ecommerce_transactions`) with a schema derived from the Google Ecommerce API rather than a flattened CSV, in any of the 43 supported destinations.
Datrise is in early access: pick a destination below to open the Google Ecommerce pipeline page, and join the waitlist to get the Google Ecommerce connector with guided onboarding.
What Google Ecommerce data Datrise extracts
Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.
| Object | Landing table | Sync mode |
|---|---|---|
| transactions | google_ecommerce_transactions | Append-only, incremental by timestamp |
| products | google_ecommerce_products | Upsert by primary key, incremental on updated-at |
| product impressions | google_ecommerce_product_impressions | Append-only, incremental by timestamp |
| checkout steps | google_ecommerce_checkout_steps | Upsert by primary key, incremental on updated-at |
| revenue | google_ecommerce_revenue | Upsert by primary key, incremental on updated-at |
| refunds | google_ecommerce_refunds | Append-only, incremental by timestamp |
Popular destinations for Google Ecommerce
Choose a destination below to open the ready pipeline page.
- AAirtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline - AAmazon Athena
Serverless SQL over S3 data lake tables.
View pipeline - AAmazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline - AAmazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline - AAmazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline - AAmazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline - AApache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline - AAzure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline - AAzure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline
Google Ecommerce connector FAQ
- What Google Ecommerce data does the connector extract?
- 6 objects: transactions, products, product impressions, checkout steps, revenue and refunds. Each lands in its own table with types preserved; history-style objects (3: transactions, product impressions and refunds) load as append-only streams.
- Is the Google Ecommerce integration incremental?
- Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
- Where can I load Google Ecommerce data?
- Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Google Ecommerce → destination pair has its own page with the object-to-table mapping.
Related sources
Other sources in the same category, each with its own connector page.
Early access
Launch your Google Ecommerce pipeline with guided onboarding
Join the waitlist to get priority access for Google Ecommerce integrations with guided setup, schema-aware mapping, and production-grade incremental sync.