Semantic layer
Also known as: metrics layer, metric layer
A semantic layer is a shared set of business definitions, such as what counts as 'revenue,' 'active customer,' or 'churn,' that sits between raw data and the tools people use.
Every dashboard, spreadsheet, and AI assistant asks the semantic layer instead of writing its own calculation. While the idea is decades old, it's having a revival because AI tools that answer business questions are only as accurate as the definitions they're given.
Semantic layer, explained at three levels
At home
Imagine a family that argues about what 'dinner time' means. Writing it on the fridge, 6:30 p.m., ends the argument. A semantic layer writes down what business words mean, so every report uses the same definition.
At work
A semantic layer makes sure 'monthly revenue' is the same number in the sales dashboard, the finance spreadsheet, and the CEO's report. That builds trust and saves hours of reconciling.
At home
The layer maps business terms to the actual tables and calculations underneath. A person asks for 'active customers by province,' and the semantic layer turns that into the correct SQL query, including the agreed rules.
At work
Modern semantic layers define metrics, dimensions, and relationships in code, expose them through APIs or SQL interfaces, and connect to BI tools, notebooks, and spreadsheets. Many also enforce access rules and cache common queries for speed.
At home
AI assistants that write SQL often guess how to calculate metrics, and they guess wrong in convincing ways. In my opinion, giving them a semantic layer is like giving a new employee a glossary on day one instead of letting them improvise.
At work
Decide where the layer lives: inside a BI tool (simpler, but locked to it), in the transformation layer (such as dbt's), or as a standalone service. Governance matters more than tooling: assign metric owners, review changes, and document edge cases like refunds or currency conversion. Measure adoption by how many tools actually query the shared definitions.
Real-world examples
At home
Sophie volunteers as treasurer for a non-profit. Two volunteers kept reporting different donor counts because one counted households and the other counted people. A simple shared definition sheet, a basic semantic layer, settled it.
At work
Thomas is a data leader at a Canadian software company rolling out an AI analytics assistant. In testing, it calculated churn three different ways. Connecting it to a semantic layer with one approved churn metric made its answers match the board report.
Common confusions
- A semantic layer is just a data catalogue. — A catalogue describes what data exists. A semantic layer defines how business metrics are calculated.
- Each BI tool's definitions are enough. — Definitions trapped in one tool drift from others, which is the problem a shared layer solves.
- AI can figure out metric definitions on its own. — AI tools can guess plausibly but wrongly. Explicit definitions make their answers reliable.
For analysts
If leadership meetings start with debating whose numbers are right, you need a semantic layer more than a new dashboard. I'd begin with the ten metrics in the board deck and assign each one an owner.
History & origin
Business Objects introduced a 'semantic layer,' which it called a universe, in the early 1990s to let business users query databases with familiar terms. Many BI tools later embedded their own definitions, which meant metrics differed between tools. Looker's LookML modelling language, launched in the 2010s, revived the idea, and Google acquired Looker in 2020 for US$2.6 billion. dbt Labs acquired Transform in 2023 to build a semantic layer, and companies such as Cube and AtScale offered standalone ones. In 2025, Snowflake and partners announced the Open Semantic Interchange initiative to standardize definitions across tools. In my view, the semantic layer is the most boring and most important thing standing between AI and confidently wrong answers.