The currenttrackMetricAPI takes an object where the propertyaverageshows up in the portal asvalueSumand the internal documentation states that it is thevalue or average.

We need to

• investigate whether this can still be defined as the "average" and stored in the Portal as an "average" value
• If it's always a value or if "can" be either, then we "should" add another optional property (to keep backward compatibility) to provideaverageorvalueand if both are provided then it should "prefer" theaverage(unless the above investigation identifies the specific case / reason why it's either)

Adding and tagging as an enhancement to review as part of the backlog when we have cycles to investigate further.