Define atomic, calculated, and qualified metrics

Define what is measured, how it is calculated, and who owns it before mapping data. Composition determines type, not the metric name alone.

Choose a metric type

Type	Definition	Example	Preparation
Atomic	Indivisible measure of an event/fact	Order amount/count	Object, unit, definition, owner
Calculated	Formula/business rule over atomic metrics	Average order amount, conversion rate	Inputs, formula, aggregation grain, exceptions
Qualified	Atomic/calculated metric with period/qualifiers	Monthly completed order amount	Base metric, period, qualifiers, meaning

Periods and qualifiers identify meaning; they do not automatically add SQL filters. Verify extraction logic in mappings and source data.

Create atomic or calculated metrics

1. Open Metric Management > Atomic/Calculated Metrics > New.
2. Choose type and folder.
3. Enter code, names/abbreviation, and business definition that distinguish object and measure.
4. Set unit, technical properties, and ownership. For calculations, define inputs, formula, aggregation, and boundary conditions.
5. Verify basic, business, technical, and management details after saving.
6. Test a few definitions and approvals before bulk import.

Definitions should specify object, scope, calculation, time basis, unit, refresh frequency, and owner. Names such as total or completion rate are insufficient.

Prepare qualifiers and periods

Qualifiers constrain scope, type, state, or properties, such as completed or online channel. Periods describe day/week/month/year ranges or grain.

1. Create reusable qualifiers without near-duplicate meanings.
2. Maintain approved periods, distinguishing calendar months from rolling 30 days.
3. Review references before changes.
4. Reread composed names and definitions for ambiguity.

Create qualified metrics

1. Open Metric Management > Qualified Metrics, select a folder, and create.
2. Select a published or usable atomic/calculated metric.
3. Choose period and qualifiers; complete definition and ownership.
4. Verify grain and semantic consistency.
5. Save, inspect details, and follow Governance.
6. Configure actual extraction using Mapping and preview.

Verify definitions

• Types match calculations and component references are traceable.
• Codes, names, meanings, units, periods, and ownership are complete and consistent.
• Periods/qualifiers are not mistaken for automatic query conditions.
• Required Dimensions exist.
• Do not claim query/monitoring readiness before mapping and validation.