Conform customer across facts
Model two business-process facts that share one reusable customer dimension instead of creating siloed customer lookalikes.
Concept
conformed-dimensions
The primary modeling idea this problem reinforces.
Requirements
3
Business needs the model must satisfy.
A commerce company wants to compare support burden against customer purchasing behavior. Orders and support tickets come from different source systems, but analysts need both processes to roll up by the same customer attributes and segments.
Conformed dimensions are where dimensional modeling stops being a set of isolated stars and becomes an analytical system. If each process owns its own customer table, cross-process metrics look easy to build but produce inconsistent segmentation and duplicated identity logic.
- Keep customer identity and segmentation attributes in one reusable customer dimension.
- Model order and support-ticket activity as separate fact tables.
- Connect both facts to the same customer dimension through explicit N:1 foreign-key relationships.
Template
Customer conformance starter workspace
The model users start from in the full workspace.
Entities
3
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.