4 - Dash Package Dashboard Customization

Your Dashboards, Your Way

Once you've got a firm grasp on the customization process, it's time to put that knowledge into practice!

Before you decide how to customize your dashboards, take the time to identify how your company wants to use this data. In addition to adding components, you will be cloning dashboards and underlying reports to setup the data to meet your needs.

This documentation section is designed to explain three major areas of Funnel Metrics customization:

• Adjusting the timeframes for the underlying data
• Adjusting dashboard segments
• Adjusting the components displayed in dashboards

A Note for New Salesforce Users

You saw these links in the previous section, but if you're new to Salesforce dashboards and reports, please review the following content before diving into customization:

Salesforce Reports & Dashboard documentation:
https://help.salesforce.com/articleView?id=analytics_overview.htm&type=0&language=en_us

Salesforce Trailhead:
https://trailhead.salesforce.com/trails/force_com_admin_beginner/modules/reports_dashboards

Ready? Set? Customize!

Global Data Filters

You may have data in your organization that you want to filter out for all cases. For example, you can exclude...

• Certain opportunity types
• Individual campaigns
• Specific geographies

If you have these types of filters, add them to all of the reports underlying the dashboard package before creating additional dashboards and reports.

Identify Your Audience

Different dashboard users may have different needs, both in terms of the data and in terms of the way in which they consume the data. Demand marketers, for example, may only be interested in their Geo, and they're likely to be working in Salesforce. By contrast, the CMO may want breakdowns by Geo, and prefer to have the dashboard emailed to them.

Determine Timeframes for Each Dashboard

Each of your Funnel Metrics dashboards has its own default timeframe. Review these below, then determine which timeframes your company will want to have so that you will know how many dashboards you'll need to create.

Dashboard Name	Timeframe	Comments
Planning	Last 12 Months. Note that this means the data does NOT include the current month.	This dashboard should have a long enough timeframe to be able to see aggregate data; however, when monitoring shifts in trends, shorter timeframes may come in handy.
Achieving	Fiscal year to date, with two opportunity coverage components displaying Closing this FQ and Closing next FQ.	If you have quarterly goals, you may wish to create quarterly dashboards in addition to viewing the previous year’s data.
Optimizing	No timeframe restrictions. Dashboard has a cohort filter for Response Date.	Filtered dashboards cannot be scheduled (i.e. send reports automatically based on predetermined schedules), but they are a great way to easily switch data around.  Using the Response Date filter creates a cohort of all of the underlying data. For example, with a Response Date filter, the Unworked MQLs component will show you only the subset that meets the filter criteria, rather than every unworked MQL in the database. You may want to do a couple things with this dashboard: Create a cutoff date on all underlying reports so that there are no responses before a certain date. This will enable the dashboard to load faster. If you do this, we recommend adjusting the dashboard description field to reflect this cutoff date. Adjust the response date filters.
Evaluation	Most dashboard components use all time data. The following components, however, use fiscal year to date: Disposition Reasons – MQL Disposition Reasons by Campaign Type Disposition Reasons – SAL Disposition Reasons by Campaign Type SQLs by Lost Reason Pipeline by Lost Reason	We recommend creating a cutoff date on all underlying reports to restrict data to after a defined date. This will enable the dashboard to load faster, as it won't have to try to calculate all the data in your database. If you do this, we recommend adjusting the dashboard description field to reflect this cutoff date. The cutoff dates will differ depending on the component. For example, if you don’t want to review data prior to 2016, you would add the following date filters to each underlying component’s report: The following component’s underlying reports would be filtered by Response Date. Response Date > 12/31/2015 Disposition Reasons SAL Disposition Reasons by Campaign Type The following component’s underlying reports would be filtered By Opportunity Created Date. Opportunity Create Date > 12/31/2015 Opportunity to Won Conversion Rate Opportunity to Won Velocity Rate Average Deal Size Most Revenue (Won) Most Revenue (Lost) Most Won Opportunities (Count) Attribution by Campaign Type SQLs by Lost Reason Touch Timing SAL Disposition Reasons by campaign Type Pipeline by Lost Reason

Other Dashboard Segments

There may be other dashboards that segment data in ways that align well with your company. Consider the following when identifying the segmented dashboards your team will need:

• Teams (marketing or sales)
• Geo
• Industry
• Other custom fields, such as market segment, company sizes, etc.

Segmentation may require unique dashboards and underlying reports, or may be addressed with dashboard filters.

When you're planning to create a new dashboard, be sure to review the following to makes sure a filter will work for your specific use case:
https://help.salesforce.com/articleView?id=dashboard_filters_overview.htm&type=0&language=en_US&release=206.13

Adjusting Dashboard Components

Funnel Metrics dashboards can contain up to 20 components. If you have more than 20, including additional funnel stages, you may need to split out a single dashboard into two dashboards. The Planning dashboard, for example, is delivered with 20 components, so you will need to create an additional dashboard if you want to add additional Planning components.

Recommended Steps for Dashboard Customization

Now that you've established the timeframe, segmentation, and component customization needs, you're ready to execute the plan! We recommend the following protocol:

1. Compile a complete list of dashboards you will be creating.
   1. Timeframe segmented dashboards
   2. Other types of segmented dashboards (team, geo etc.)
   3. Folder names for dashboards and dashboard reports.
   4. Audience for each dashboard clearly identified
2. Start with the right "master" dashboards
   1. The components you want to use are set up
   2. Any underlying global filters applied to underlying reports
   3. Any additional master dashboards are generated
3. Validate these master dashboards with key stakeholders before beginning additional customization work. You're about to put in a fair amount of work to get these dashboards up and running. You probably don't want to end up doing it twice.
4. Establish the order in which you want to clone dashboards and reports. Grouping similar changes together will streamline your work. If you're going to create four versions of the Achieving dashboard, for example - one for each fiscal quarter this year - executing your tasks in the following order will save you time:
   1. Clone the dashboard four times and rename for each time period.
   2. For each report, ‘save as’ and customize four times (one for each timeframe).
   3. For each dashboard, edit and replace the underlying report with the new report for each timeframe.
5. Create new dashboard and report folders. Make sure all the relevant users have access to them.
   Note: Consider locking underlying report folders to view only, particularly if you are using filtered reports.
6. Clone the master dashboards and put them into the corresponding new dashboard folder with the correct names.
7. Click through each master dashboard and do a ‘save as’ for the underlying report. Adjust filters as needed.
   Note: It may be most efficient to create multiple version of the same report at the time.
8. Edit the new dashboards.
   1. Adjust dashboard description to describe global filters.
   2. Update the components to the correct underlying new reports.
9. Save and QA the dashboard and reports.