Sources
The seven upstream systems CCC ingests from, and what each can and cannot give you.
Seven upstream systems feed CCC. This section describes each as the data arrives: what it delivers, how often, over what window, and what it will not give you.
What CCC builds from them, and which period of history came from which, is in objects.
| Source | Delivers | Can it backfill? |
|---|---|---|
| NetSuite | Transactions, items, customers, ledger | Yes, by date |
| Akeneo | Product information | Current state; mixed upserts and swaps |
| commercetools | Cart and order discounts | Yes, by date, one day per batch |
| GA4 | Order attribution and traffic | Attribution: no. Traffic: requested by date |
| verkoopdump | Pre-2022 history, the GA4 gap, old sequence | Yes, by hand in slices |
| Azure | Product stock | Current state only |
| PriceShape | Product prices per domain | Current state only |
The two facts that explain most history questions
GA4 order attribution never backfills. Its cm2sourcemedium call takes no date and answers one rolling window whatever day the batch carries. So it refreshes recent orders and nothing else, and the period from 2022 to 2025 has no source and medium from it at all.
verkoopdump fills what the others cannot. It holds pre-2022 transactions, the source and medium GA4 never reached, and the old pipeline's customer sequence. It is read-only, and it is the company's only copy of that history.
Together those two produce the seam that runs through most objects: one provenance before a date, another after it.
Related
- Type
index - Status
active - Updated
2026-09-14 - Created
2026-09-13