Who can use this: Business admin
Available on: Gong Forecast
Ideal for: RevOps
Required permissions: Manage dashboards
Sometimes dashboards display different data than you expect or do not respond to your selections. Use this guide to identify the cause and resolve common issues.
A viewer can't see the dashboard
Published dashboards are only visible to team members who have both an active Forecast seat and the Dashboards page permission in their profile.
To resolve access issues:
Confirm the dashboard has been published. Unpublished dashboards are only visible to team members with the Manage dashboards permission. Open the dashboard. If it shows Publish and share at the top right corner, it hasn't been published yet.
Ask your tech admin to check that the viewer's permission profile includes the Dashboards page permission. This is found in Admin center > Permission profiles > Pages.
Confirm the viewer has an active Forecast seat allocated to them.
If permissions look correct, ask the viewer to try the following browser steps:
Update their browser to the latest version.
Clear their browser cache and cookies.
Close and reopen the browser.
Try opening the dashboard again.
A widget shows no data or unexpected data
Widget data depends on correctly configured metrics, targets, and filters, as well as the team and date selections made in the dashboard.
To troubleshoot a widget showing no data or unexpected results:
Check the dashboard-level Team and Period selectors at the top of the page.
Check whether the widget shows a note saying Dashboard selections don't apply.
If the team member and date fields are set to fixed values, open the widget settings and change them to be dynamic and respond to the dashboard selection.
If the team member and date fields are set to dynamic values, check the widget settings for any filters that might be excluding expected data.
Verify that the underlying metric is correctly configured. Open Admin center > Data studio > Metrics, find the metric, and review its aggregation, base object, conditions, and team member field.
Note:
The dashboard team selector and the team member field inside a widget's settings are not the same thing. The dashboard selector filters which team's data is shown. The widget's team member field defines which CRM role (for example, opportunity owner or account executive) is used to associate deals with team members. Mixing these up is a common cause of unexpected results.
A widget is not responding to the date picker
Some widgets only support specific date picker types.
To resolve date picker incompatibility:
Identify which widgets are not responding to the date selector.
Check the widget type. Forecast rollup and Target attainment widgets support fiscal dates only.
If your dashboard uses a Rolling range date picker and includes these widgets, consider switching to a Fiscal calendar or combined date picker. Note that changing the date picker type may affect other widgets already configured on the dashboard.
If you are using a combined date picker (Both - Fiscal primary or Both - Rolling primary), be aware that Forecast rollup and Target attainment widgets will only respond to the fiscal calendar component of the selection, not the rolling range.
The dashboard is slow or unresponsive
Dashboards with many widgets, large teams, or high-cardinality groupings (for example, grouping by a field with many distinct values) can become slow to load.
To improve dashboard performance:
Review the number of widgets on the dashboard. Remove any that are rarely used or that duplicate information already shown elsewhere.
Check widgets that use high-cardinality group-by fields and consider whether a simpler breakdown would serve the same purpose.
If the dashboard is regularly used by a very large team, consider splitting it into two smaller dashboards focused on different business questions or audiences.
Data from Trends or Changes is missing or incomplete
The Trends and Changes widgets rely on historical CRM field tracking. If the underlying data appears sparse or shows empty states, it is usually because the prerequisites for historical analysis have not been fully completed.
Required setup, in order:
Enable Track history on the CRM fields you want to use in the widget.
Wait for the historical backfill to complete. This can take time depending on the volume of data.
Enable Historical analysis on the relevant metric in Admin center > Data studio > Metrics.
Only fields with Track History enabled will be available for breakdowns and filters in these widgets. If a field you expect to see is missing from the widget configuration, confirm that Track history is enabled for it.