Mapping
Connect source fields to Blocchi's semantic business concepts so metrics can be computed.
Mapping tells Blocchi what your source data means. A Salesforce Opportunity, a HubSpot deal or a spreadsheet row all become the same semantic Opportunity once mapped, so metrics, reports and agents work the same regardless of provider.
Mapping overview (/app/data/mapping)
See mapping coverage by source and dataset: which semantic entities and attributes are mapped, and which dimensions are ready for analysis. Open the technical console only when you need to change something.
Editing a mapping
From a source's page, open Mapping (/app/data-sources/[connectionId]/mapping):
- Choose the semantic entity (for example Account, Person, Opportunity) and the source object.
- Match source fields to semantic attributes. Blocchi suggests matches; you confirm them.
- Review the dimension readiness — for example 8 of 10 dimensions are ready for analysis on this dataset.
- Save. Metrics that depended on the new mapping become computable after the next sync.
Why it matters
Most readiness states in Blocchi ("map this field to measure this block") point here. Provider-specific names never become product identifiers: a metric definition refers to semantic attributes, not to provider fields.
Related
Last updated on