Reporting & dashboards
Reporting and dashboards built on governed metrics.
Turn connected marketing, web, and commerce data into reusable operating views without handing the browser table names, raw SQL, or tenant authority. Metric Hive keeps each widget anchored to approved fields, source scope, grain, and date behavior before a query runs.
- Reusable dashboard templates
- Account-scoped semantic queries
- Data Health beside delivery
Last 30 days
All paid sources
Campaign
Performance over timeDaily
Campaign performanceTop 4
CampaignSpendClicks
Brand search$24.8k38.2k
Prospecting$21.6k29.4k
Retargeting$16.2k26.1k
Shopping$12.4k14.7k
Paid media and web analytics stay in their own governed sections; the dashboard does not silently blend their grains.
One contract, several reporting surfaces
Build once around business meaning.
Native dashboards, scheduled delivery, and supported BI connections start from the same backend-owned semantic definitions instead of rebuilding metric logic for every output.
Native dashboard workspace
Start from a dataset-aware template or assemble a custom grid with KPIs, tables, charts, filters, notes, sections, and dividers.
- Save account or personal views
- Reuse global date ranges and filters
- Rename, duplicate, or set a default dashboard
Scheduled semantic exports
Select approved fields, date scope, destination, and schedule while the backend validates the export plan and destination-safe schema.
- BigQuery, Google Sheets, Snowflake, Redshift, and S3 builder flows
- Daily run times with an explicit timezone
- Export health and period state in Data Health
Governed BI handoff
Expose a saved semantic export to supported downstream reporting tools without asking the connector to reinterpret field semantics.
- Looker Studio reads a saved export contract
- Schema and rows are supplied by Metric Hive
- Connector limits and feature availability remain explicit
Reusable starting points
Templates that respond to connected data.
Metric Hive checks required and optional semantic datasets before a template opens. A missing required dataset blocks the template; missing optional data is shown as partial rather than quietly replaced with a different signal.
Paid adsRequired
Paid marketing
Spend, delivery, clicks, campaign performance, platform breakdowns, and efficiency views from compatible paid-media fields.
Paid + webGA4 optional
Performance marketing
Paid advertising and website outcome signals shown in separate, source-bound sections inside one operating view.
Store + marketingShopify required
Ecommerce marketing
Store sales and product performance with optional paid-media and web-analytics sections when those datasets are connected.
Shopify + GA4GA4 optional
Shopify + web analytics
Commerce truth beside website behavior without presenting provider analytics as store revenue or inventing blended metrics.
From connection to review
A reporting workflow with validation at every handoff.
Choose a governed dataset
Available fields come from the query catalog for connected, account-visible sources—not from a frontend-provided table name.
Compose the operating view
Select compatible metrics, dimensions, source scope, dates, filters, visualization, and layout. Required grain dimensions are retained when a metric needs them.
Preflight every widget
The semantic planner checks field availability and compatibility before execution. Invalid widget requests stop with a repair path instead of falling back to broader data.
Save and share the view
Persist the validated dashboard for the account or an individual user, preserve its grid and controls, and choose a default view for repeat reviews.
Deliver on a controlled cadence
Create a governed export for supported destinations, set explicit daily run times and timezone, and keep destination credentials separate from the report definition.
Review trust signals
Use Data Health to inspect freshness, coverage, ingestion jobs, metric trust, export runs, failed periods, and product readiness alongside the reporting workflow.
Clear authority boundaries
Flexible for operators. Constrained where trust depends on it.
Report builders should control the question and presentation. They should not become authority for tenant identity, physical storage, metric aggregation, or semantic relationships.
See how the semantic layer works
You select
Metric Hive proves
Metrics and dimensions
Field roles, aggregation, compatibility, and required grain
Connected sources
Subscription, account, source membership, and dataset match
Date range and filters
Date contract, safe operators, and bounded query scope
Chart and layout
Widget shape, field limits, and preflight validity
Export mode and destination
Approved table plan, schema, currency behavior, and export policy
Data Health
Warnings
Know when a dashboard deserves attention.
Reporting is only useful when teams can see the state behind it. Data Health brings source freshness, downloaded coverage, the latest ingestion job, semantic queryability, export status, and product readiness into one account-scoped review.
Shopify ordersCommerce dataset
Warning
FreshnessHealthy
CoverageWarning
Latest jobFailed
Honest product boundaries
What the reporting layer will not pretend to do.
No silent cross-source joins
When templates include paid media, GA4, or commerce, widgets stay bound to compatible datasets. Side by side does not mean row-level attribution or an approved blended grain.
No frontend SQL authority
The browser submits approved field IDs, filters, dates, and source selections. Backend catalog, planner, compiler, and tenant scope determine the executable query.
No universal metric additivity
Rates, snapshots, averages, and semi-additive measures keep their own aggregation requirements. Required dimensions are not dropped just to make a chart render.
No hidden readiness leap
Template and export availability follows connected sources, compatible fields, destination capability, and product-specific publishing or export gates.
A calmer weekly review
Move the reporting conversation from “which number?” to “what changed?”
Connect your sources, start with a compatible template, and build repeatable reporting around governed metrics and visible trust signals.