Metric definitions
Metric Hive keeps formulas, denominators, date bases, and aggregation behavior close to the backend dataset contract.
Quick take
Supermetrics moves data. Metric Hive governs the model.
Supermetrics is useful when the main job is connector automation into Google Sheets, Looker Studio, Power BI, warehouses, or APIs. Metric Hive is for teams that want governed definitions behind the metrics before they become reports.
| Decision area | Metric Hive | Supermetrics |
|---|---|---|
| Primary motion | Build governed source and query contracts, then expose only the datasets and surfaces that pass current product and account-readiness gates. | Connect marketing data sources and deliver data into reporting, storage, warehouse, and activation destinations. |
| Semantic depth | Canonical entities, explicit grains, metric aggregation behavior, guarded query datasets, and destination registry-eligibility rules. | Transformation, blending, custom fields, storage, and delivery workflows; public docs do not show a Metric Hive-style semantic contract. |
| Pricing and access | A published monthly usage framework without row-based source pricing. Pricing does not prove that an export, commerce output, or measurement module is enabled. | Starter, Growth, Pro, and Enterprise packaging with entry prices for lower plans and quote-based Enterprise. |
| Growth risk | The published framework separates sources and optional capabilities; gated capabilities require release and readiness confirmation before use. | Final cost can become add-on or quote dependent as destinations, users, sources, accounts, refresh cadence, API rows, storage, and transformations expand. |
Metric governance
Connector data still needs a business contract
The Supermetrics value proposition is strongest around destination automation. Metric Hive should be evaluated when teams need the same definition of spend, revenue, ROAS, MER, contribution margin, campaign, account, customer, and order to hold across every surface.
Commerce semantics
Commerce contracts can distinguish order revenue, line-item profit, refunds, shipping income, fulfillment cost, payment fees, COGS, and contribution profit. Broad customer availability remains pilot-gated.
Source traceability
Modeled outputs retain source and account context so teams can explain where a metric came from when a dashboard changes.
Export contract, not a live promise
Adapters and registry rules are designed to preserve the same semantic fields across eligible destinations. Live customer exports remain disabled until account readiness and a destination smoke test are confirmed.
Pricing
Use this page when Supermetrics becomes plan and add-on dependent
Supermetrics publishes entry prices, but the buyer still has to reason through destinations, users, sources, accounts, refresh cadence, API row limits, storage, transformations, and Enterprise custom requirements.
Lower plans have limits
Public Supermetrics packaging limits lower plans by users, sources, accounts, refresh cadence, API rows, and destination count.
Enterprise gates important work
Public docs and pricing place capabilities such as Data Transformations, Data Blending, Custom Fields, full Storage, Management API access, multiple teams, and data residency in higher tiers or add-ons.
Published economics are not availability
Metric Hive publishes intended usage economics separately from product readiness. Live destinations, commerce outputs, and measurement access must still be confirmed for the account.
Fit
When to choose Metric Hive or Supermetrics
Choose based on whether the team needs mature connector automation now or wants to evaluate an inspectable semantic contract with explicit readiness boundaries.
Choose Metric Hive when
Your team wants public source mappings, explicit report grains, metric guardrails, and a readiness review that distinguishes implemented contracts from customer-enabled capabilities.
Choose Supermetrics when
Your main requirement is a mature connector and destination automation stack for reporting into the tools your team already uses.
Metric Hive is not right when
You need broad destination automation, production-ready MMM or MTA, turnkey commerce-profit workflows, or established spreadsheet and BI delivery today and cannot accept a controlled pilot or readiness gate.
Source notes
Refresh these sources before publishing changes
Competitor packaging can change. Re-check public pages before editing claims about price, plan limits, or gated features.
Inspect the contract before comparing access
Review the public semantic contracts first, then confirm connector, destination, commerce, and measurement readiness for the account you would actually use.