Admin metrics create and builder
Use Create and the builder experience when you are authoring or substantially changing a metric definition. This path emphasizes validation, preview, and dimension typeahead helpers.
What you do here
- Define keys, scope, aggregation, and filters.
- Run preview to catch issues before publishing.
- Keep Driver-facing description copy short. The builder warns at 110 characters so scorecard tiles stay easy to scan.
- Use summarize and related helpers to understand how the engine interprets the definition.
- Prefill and similar shortcuts may appear depending on your workflow.
Scorecard composite (weighted headline)
For Composite from scorecard metrics, choose Blend mode: Goodness (0–100) maps each component through its score bands (needs two active bands per component), then averages those scores — useful when mixing higher- and lower-is-better metrics; configure composite thresholds on a 0–100 scale. Raw weighted values keeps the legacy Σ(weight × weekly value) / Σ(weight) blend (same units recommended). Pick at least two driver metrics and positive weights. Components cannot be other composites. Components must be shadow or published when you save. After publishing, use Admin metric detail for scorecards and headline grid placement if your permissions allow.
Dimensions and filters
The dimension values endpoint powers filter chips and typeahead in the builder. If something does not appear, confirm the dimension catalog and sync coverage for your data sources.
When you are done
Publishing, lifecycle transitions, goals, alerts, and scorecard inclusion are handled on the metric detail surface after the definition exists. See Admin metric detail.