Yotpo → GoodData
AI-first ETL from Yotpo into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Yotpo into GoodData
Datrise syncs Yotpo's reviews, loyalty members, redemptions, and campaign events into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Yotpo: Reviews and loyalty marketing for e-commerce brands.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Yotpo entities map to GoodData
| Yotpo entity | GoodData object | Notes |
|---|---|---|
| reviews | yotpo_reviews | id PK · custom fields → flattened columns |
| loyalty members | yotpo_loyalty_members | id PK · linked to yotpo_reviews |
| redemptions | yotpo_redemptions | id PK · linked to yotpo_reviews |
| campaign events | yotpo_campaign_events | date dimensions events |
FAQ
How does Datrise handle Yotpo's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Yotpo to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Yotpo
Early access
Connect Yotpo to GoodData 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.