Keep metric units explicit through table transformations — what should the operator record?
A generic value column can combine metrics that look numeric but mean different things. The problem is operational even before anyone compares outcomes: a sum or sort can silently mix incompatible units. Preserve metric names and units from actual evidence, and keep local conversions separate from returned observations and their original representation.
Prevent unlike counts, durations and percentages from sharing an apparently comparable numeric column.
Create metric_name, raw_value, unit and source_context fields. If the source does not establish a unit, use unit-unknown and block unit-dependent calculations rather than guessing from a familiar label or an expected range of values in neighboring records.
Attach unit and conversion revisions to the output, retaining original values where permitted. A sorted numeric column should not imply a universal cross-source performance ranking, and successful conversion does not establish that every source supplies complete or comparable metrics.Inventory actual units
Create metric_name, raw_value, unit and source_context fields. If the source does not establish a unit, use unit-unknown and block unit-dependent calculations rather than guessing from a familiar label or an expected range of values in neighboring records.
Define permissible conversions
Document only justified transformations, such as a known duration unit conversion, in derived_value and derived_unit fields. A percentage and a proportion need an explicit conversion rule; a label containing rate alone does not establish which representation the source supplied.
Test mixed-unit fixtures
Use clearly labeled example durations and percentage-like strings, verifying that incompatible units cannot be aggregated under one metric key. Include unknown-unit input and expect an unresolved state instead of an inferred conversion based on the numeric value's appearance.
Review combined tables
When unioning branches, compare metric definitions as well as column names. The same display label can describe different scopes or units across contexts, so preserve context-specific measures unless an authoritative contract supports direct equivalence for the intended operation.
Release typed measures
Attach unit and conversion revisions to the output, retaining original values where permitted. A sorted numeric column should not imply a universal cross-source performance ranking, and successful conversion does not establish that every source supplies complete or comparable metrics.
Keep the boundaries clear.
- Prevent unlike counts, durations and percentages from sharing an apparently comparable numeric column.
- Operational record: Inventory actual units. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.