Glossary/Semantic Layer & Metrics

Metric Layer

A metric layer is a dedicated section of the semantic layer that defines, manages, and governs business metrics, enabling consistent calculation and delivery across analytics platforms.

The metric layer is the business metrics component within a broader semantic layer. While the semantic layer provides general data abstraction, the metric layer specifically focuses on defining what metrics are, how they're calculated, their valid dimensions, and their aggregation rules. It transforms underlying facts and dimensions into governed business metrics.

The metric layer emerged because organizations realized metrics were being defined inconsistently across BI tools, SQL queries, and dashboards, leading to conflicting revenue reports or customer counts depending on which tool generated them. By concentrating metric definitions in one place with clear ownership and versioning, teams eliminate this fragmentation. The metric layer codifies business rules: whether revenue includes refunds, how to handle multi-currency transactions, which customer segments apply to which metrics.

A metric layer typically includes metric definitions (what to calculate), dimension bindings (which dimensions apply), aggregation types (sum, average, count), time granularity rules, and access controls. Modern metric layers support metric composition: defining new metrics from existing ones (for example, profit equals revenue minus cost). The metric layer is the operationalization of metric strategy.

Key Characteristics

  • Defines business metrics with explicit calculation logic
  • Specifies valid dimensions and filter combinations
  • Implements aggregation rules and time-series handling
  • Enables metric composition and derived metrics
  • Provides metrics to downstream tools via APIs or SQL
  • Includes ownership, versioning, and change tracking

Why It Matters

  • Accuracy: Consistent metric definitions eliminate calculation discrepancies
  • Speed: Metric pre-computation and caching reduce query time
  • Auditability: Clear lineage from metric definition to dashboard
  • Scalability: Support thousands of metrics without manual rewrites
  • Governance: Restrict metric access, track changes, manage deprecation

Example

A metric layer defines "Monthly Active Users" with specific cohort logic, valid dimensions (region, product, customer tier), aggregation rules (count distinct user ID), and time handling (calendar month vs. rolling 30 days). When a dashboard references this metric, it automatically gets the governed definition rather than a custom SQL interpretation.

Coginiti Perspective

Coginiti's metric layer is the measures section of SMDL, where each measure defines its aggregation behavior and the Semantic SQL engine enforces it at query time through the MEASURE() function. This separation means the metric layer is not a runtime service but a declarative specification that the query engine interprets. Changes to metric definitions propagate immediately to all Semantic SQL queries and ODBC-connected BI tools, ensuring the metric layer stays synchronized with how metrics are actually consumed.

See Semantic Intelligence in Action

Coginiti operationalizes business meaning across your entire data estate.