Skip to main content
Published SourceMedium metric definitions, formulas, categories, and aliases. The catalog is regenerated by its producer. Consumer dashboards can use older copies, so compare definitions before assuming equivalence.
This is the source of truth for metric definitions. Query this table to discover available metrics, understand their calculations, and find the right metric for your analysis.

Use Cases

  • Metric Discovery: Find all available metrics and filter by category or type
  • Understanding Calculations: See exactly how each metric is calculated
  • Dependency Tracking: Identify which metrics depend on other metrics
  • Alias Resolution: Map abbreviated metric names (like aov) to their full descriptive names
  • Documentation: Generate metric documentation for your team

Columns

Using definitions in a dashboard

The catalog has no store column. Apply authorized store scope to the business relations, and compare each published definition with the report’s actual population, filters, date basis and grain. A similar label is not a match. Executive Summary orders sum the published summary count. They are not the valid-order count on obt_orders. Revenue per summary order is a report-specific ratio, not valid-order AOV. Summary marketing efficiency and platform-reported ROAS use different inputs and attribution bases. Calculate each ratio from aggregated components, not an average of daily ratios. Resolve dependent_metrics as exact comma-separated metric identifiers. A missing dependency, duplicate definition, cycle, changed filter or changed date expression needs review. Do not silently replace a saved calculation. Custom reports can remain explicitly report-specific. value_format is optional for consumers of older publications. Validate that it agrees with the reviewed measure; an inaccessible field is different from an absent field. Keep exact values for arithmetic and exports, and round only for display. catalog_updated_at records a catalog build, not business-data freshness or numerical reconciliation. The dashboard template displays calculation and filter text as documentation. Its warehouse queries remain developer-authored and parameterized; it does not execute metadata strings as SQL.

Example Queries

Find All Revenue Metrics

Discover Marketing Efficiency Metrics

Resolve an Abbreviated Metric Name

Find All Abbreviations for a Metric

List All Cumulative (MTD/QTD/YTD) Metrics

Find Metrics by Underlying Data Source

Explore Metric Dependencies

Get Canonical Metric Names (Resolving Aliases)

Metric Types Explained

Direct aggregations of a single measure. These are the building blocks for other metric types.Examples:
  • order_net_revenue = SUM(order_net_revenue), over valid orders
  • order_count = COUNT(sm_order_key), over valid orders
  • new_customers = COUNT(DISTINCT sm_customer_key), over customers whose first valid order falls in the period, on Online DTC, Amazon and TikTok Shop
Calculation column shows: the aggregation, such as SUM(column), COUNT(column) or COUNT(DISTINCT column), followed by WHERE [filter applied] when the metric is filtered. The filter itself is in filter_condition.
Division of two metrics, typically used for averages and rates.Examples:
  • average_order_value_net = order_net_revenue / order_count
  • customer_acquisition_cost = total_ad_spend / new_customer_order_count
  • click_through_rate = total_ad_clicks / total_ad_impressions
Calculation column shows: numerator_metric / denominator_metric
Custom calculations combining multiple metrics with expressions.Examples:
  • cost_per_thousand_impressions = total_ad_spend * 1000 / total_ad_impressions
  • gross_margin = gross_profit / order_net_revenue
Calculation pattern: Custom SQL expression
Running totals that accumulate over time periods.Grain-to-date:
  • mtd_net_revenue = Month-to-date net revenue (resets each month)
  • qtd_net_revenue = Quarter-to-date net revenue
  • ytd_net_revenue = Year-to-date net revenue
Trailing windows:
  • trailing_30d_revenue = Revenue for the last 30 days
  • trailing_90d_revenue = Revenue for the last 90 days
Calculation column shows: CUMULATIVE_SUM(measure_name)

Metric Categories

Common Aliases Reference

The semantic layer supports abbreviated metric names for convenience. Always use the full descriptive name for new implementations.
Query the catalog with WHERE is_abbreviation = true to see all available aliases and their preferred metric names.

Best Practices

1

Use Full Metric Names

For new dashboards and queries, always use the full descriptive metric name (e.g., average_order_value_net instead of aov). This improves readability and maintainability.
2

Check Dependencies Before Filtering

When filtering metrics, check the dependent_metrics column to understand what underlying data will be affected. Ratio and derived metrics may behave unexpectedly with certain dimension filters.
3

Match Semantic Models for Joins

When combining metrics in a query, prefer metrics from the same semantic_model_name for consistent dimension availability. Mixing metrics from different semantic models may limit available dimensions.
4

Use Cumulative Metrics for Period Totals

For MTD, QTD, or YTD reporting, use the pre-built cumulative metrics instead of writing custom window functions. They handle edge cases like partial periods correctly.