We create dashboards all the time but the way heap is designed now, you have to make so many reports to support different views. The main problem stems from fact that dashboards cannot be saved with filters applied (at the dashboard level).
Scenario:
I have 2 product lines: Foo and Bar.
I want to have a dashboard that shows:
- Traffic to Foo product pages
- Sign Up conversion for Foo
- Purchase Conversion for Foo
The natural thing you want is to create 3 generic reports that can be filtered on product line. You add these 3 reports to a dashboard and save one instance of it filtering (at the dashboard level) for Product=Foo, and another version of the SAME dashboard, but filtering product=bar.
This then allow me to have 3 reports powering 2 dashboards. My only choices now are:
- have 3 reports with 1 dashboard and teach everyone how to use filters
- create 6 reports (3 filtered on Foo, and 3 filtered on Bar) and create 2 unique dashboards
Heap would be so much more powerful if my ideal scenario was possible. It also reduces the sheer # of reports we have.
Best answer by Emily Brodman
View original