Conform a customer dimension
Share one customer dimension across orders, support, and returns so customer behavior reconciles across all three.
Concept
conformed-dimensions
The primary modeling idea this problem reinforces.
Requirements
3
Business needs the model must satisfy.
A retailer wants customer-level analysis that spans buying, getting support, and returning items. Orders, support tickets, and returns are three separate processes, but leadership wants them tied to one customer identity. The customer dimension exists; the three facts do not.
Three-process conformance is where siloed teams usually fail: each builds its own customer table and the funnels never reconcile. One conformed customer dimension is the fix.
- Add orders, support-ticket, and returns facts, each at its own grain.
- Reference the existing customer dimension from all three facts.
- Declare surrogate-key foreign keys and N:1 relationships from each fact to the customer dimension.
Template
Conformed customer starter
The model users start from in the full workspace.
Entities
1
Seeded tables visible in the public preview.
Dialect
postgresql
Generated SQL target for this starter model.
This preview is read-only. Open the workspace to edit and verify; saving needs a free account.
Open workspaceTry the question first.
The discussion has other people's approaches and solutions. Give it a real attempt before you read them.