Custom Metric Dashboard Widgets Need Full Range of Conditions
J
John Flaniken
Love the potential for the new CUSTOM METRIC Widgets in the dashboard builder.
But, they are lacking metric customizability via conditional options for each metric type. For example: the only thing you can filter for when choosing Opportunities within the custom metric calculation is the date field you want to choose from. We need to be able to use the full range of conditions that we can use in typical opportunities widgets to make this useful. (ie, pipeline, stage, value, custom values, etc.))
ALSO, the opportunities conditionally chosen to build the custom metrics should abide by the user-assigned filters that you can use at the dashboard viewing level.
Log In
K
Kelvin Khoo
I agree. There needs to be better options such as selecting a value that is displayed on the customer dashboard and applying an operation with another value that is displayed to be able to create a KPI custom metric. For example, taking the Ad Spend value displayed from Meta divided by total number of Contacts/Opportunites that came from Meta to get CPL
W
Will Dukes
Even if we were able to access another widget's output, it would be helpful. E.g . I have a widget for number of opportunites with status won in a certain pipeline. Being able to access that output in a custom widget, and then operate on it with the output from another widget would also allow me to get very granular in my metrics without having to export to a google sheet.
J
John Flaniken
EDIT: the metrics conditionally chosen to build the custom widgets should have individual toggles to abide by user-assigned filters that you apply at the dashboard viewing level (ex. you want to multiply user-owned opp-count in one pipeline by total opp value in another pipeline)
Also, date-range override filters should be added per individual metric in the builder too (ex. You want to multiply opps created within "dashboard date range" by opps created within (override) "to date")
T
Tracey Lipnicki
YES, so many things are missing that we cant filter data correctly. the conditions need to have access to ALL fields otherwise we cant use them for proper KPIs.