The problem / use case
Today, when we map a custom numeric field into Staircase via account field mapping (Settings > Configuration > Account Fields), Staircase automatically treats it as Product Usage. Every custom numeric value we bring in gets pulled into Product Usage by default so a field like ARR ends up counted as usage even though it's a revenue figure, not a usage metric. There's no way to tell the system which numeric fields are actually part of usage and which aren't.
Current behavior
Any mapped custom numeric field → automatically included in Product Usage, with no control over which fields qualify.
Requested enhancement
Give admins a way to explicitly designate which custom numeric fields are part of Product Usage e.g. a per-field toggle or a "use as Product Usage" flag in the Account Fields mapping. Fields not designated would be brought in as standard numeric data and excluded from the Product Usage calculation/display.
Business value
Product Usage is only meaningful if it reflects actual usage. Auto-including every custom numeric field mixes in financial and other non-usage values (like ARR), which distorts the usage signal and undermines trust in Staircase data. An opt-in designation keeps Product Usage accurate while still letting teams map other numeric fields for reporting and context.