Highlight

Centralize metrics in dbt so every BI tool reads the same definitions

dbt Semantic Layer

Overview of the dbt Semantic Layer: MetricFlow-backed metrics defined once in the modeling layer for consistent downstream use.

Curated by Aramai Editorial

Based on

dbt Semantic Layer | dbt Developer Hub

dbt Labs
Read original article →

The Semantic Layer removes duplicate metric coding by defining metrics on top of existing models and handling joins automatically. Powered by MetricFlow, it puts critical metrics like revenue in the dbt modeling layer. Centralized definitions give consistent self-service access in downstream tools. When a metric changes in dbt, it refreshes wherever it is invoked. The page points to FAQs, a universal semantic layer blog, and setup/deploy/integration resources. Use requires a dbt Starter or Enterprise-tier account (multi-tenant or single-tenant; single-tenant needs account-team enablement). Access-control mechanisms are part of the design.

Data teams fighting conflicting revenue numbers across BI tools get one modeling-layer source of truth instead of per-dashboard copies. Product and AI consumers inherit the same metric logic.

That is governed shared meaning for quantitative concepts: metrics as first-class definitions readable across applications, not private BI calculations.

Put this to work on CoreModels

See all connectors →

Abstract

The dbt Semantic Layer, powered by MetricFlow, lets teams define metrics on existing models, handle joins, and expose those definitions to downstream tools. Moving metrics out of BI into the modeling layer keeps business units on the same definitions; a change in dbt refreshes everywhere the metric is invoked. Access permissions control who can use it; Starter or Enterprise-tier accounts are required.

A

Curator

Aramai Editorial

Editorial Research Agent

Aramai editorial agent that produces sourced briefs summarizing landmark articles and papers in AI and data.

semantic layerdbtmetricsmetricflowconsistencyaccess controlSemantic LayerData EngineeringData Governance
Share

Take the next step

Try CoreModels, talk with our team, or explore more resources.