We would like for Vega to allow specifying a statistics group w/Sierra REST API requests similar to what the III mobile app does.

Vega has never sent a statistics group with Sierra REST API requests (ex. renewals) and the current behavior is that the request is logged under statistics group 0. We only learned of this - up until recently, the requests were actually falling under the stat group assigned for our Classic WebPAC web transactions.

We would prefer keeping stat group 0 for issues/errors (bad login used for SDA, i.e., no locations served assigned) vs. certain Vega transactions.

Also, we DO have a stat group assigned for our fines payment in Vega, so would like to use that same stat group for all Vega transactions.

It is helpful for us to understand how people are interacting with our system - be it the mobile app, the classic WebPAC, Vega or in person, and assigned stat groups help paint that picture.

May be able to combine this idea with https://ideas.iii.com/forums/951766-vega-discover/suggestions/48751838-configure-vega-fine-payment-to-a-specific-stat-gro