Solution guide · GoHighLevel
GoHighLevel dashboard not showing data? How to fix it
GoHighLevel dashboard not showing data? Fix blank widgets, the wrong date property, permissions and ad connections, then build a custom dashboard that works.

Key takeaways
- Most GoHighLevel dashboards that show no data are not broken: the widget is filtered, using the wrong date property, pointed at a missing data source, or hidden by the user’s permissions.
- Opportunity widgets count by Last Status Change by default, not by the date the opportunity was created, so their totals rarely match the Opportunities tab until you change the date property.
- Users with “Only Assigned Data” switched on only see records assigned to them, so the same dashboard can look full for an admin and empty for a sales rep.
- Google Ads, Meta and Google Analytics widgets stay blank until the account is connected under Settings → Integrations, and GA4 is the only Analytics version supported.
- Widgets with a red border after a snapshot or duplicate are missing a pipeline, custom value or custom field in the new sub-account; edit each one and reconnect it.
If your GoHighLevel dashboard is not showing data, the widget is almost always working: it is filtered, counting by a different date, pointed at a missing pipeline or custom value, hidden by the user’s permissions, or waiting for an ad or Analytics account to be connected. Open the widget, check its Conditions and date property, then check permissions and integrations.
This guide goes through every cause I see when clients send me a blank or wrong dashboard, with the exact fix for each, as of November 2026. Then it shows how to build a custom dashboard that shows the numbers you actually run the business on, which is the same process I use for GoHighLevel dashboard customisation.
What changed on the GoHighLevel dashboard recently
The dashboard has changed a lot in 2026, which is why older tutorials and screenshots no longer match what you see:
- General widgets are now editable. The default widgets on a sub-account dashboard (opportunity status, value, conversion and so on) used to be fixed. HighLevel’s changelog says they can now be edited, filtered, renamed and themed, with a date range override and a comparison mode. The help article, updated on 24 September 2026, says you open a widget’s three-dot menu, click Edit, and work through three tabs: Configure, Conditions and Themes.
- The widget face shows its date property and range. That same update made each widget show which date it is counting on, which is the single most useful clue when a number looks wrong.
- Multiple dashboards on every plan. HighLevel made multiple dashboards and custom reports available on all plans, so you no longer need the top plan to build your own.
One thing the official sources disagree on: the changelog lists dashboard Quick Filter support for general widgets, while the September help article says general widgets do not currently respond to Quick Filters. If a Quick Filter at the top of the dashboard does not change a general widget, that is expected. Set the filter inside the widget on its Conditions tab instead.
Blank or wrong
- Avoid: Old filter left on Conditions
- Avoid: Counting by Last Status Change
- Avoid: Dashboard still private
- Avoid: Ad account not connected
- Avoid: Pipeline missing after snapshot
Shows real numbers
- Do: Only the filters you meant
- Do: Date property you chose
- Do: Shared with the right roles
- Do: Google Ads and Meta connected
- Do: Every widget remapped
Why your GoHighLevel dashboard is not showing data: the quick diagnosis
Start with what you see on the widget. This table maps each symptom to its cause and the section below that fixes it.
| What you see | Most likely cause | Fix |
|---|---|---|
| “No data” or 0 on a widget you know has records | A filter on the Conditions tab, a date range override, or a narrow date range | Fix 1 |
| Numbers that do not match the Opportunities tab | The widget counts by Last Status Change, not Created On | Fix 2 |
| Full for the admin, empty for a team member | Only Assigned Data, or a widget filtered to another user | Fix 3 |
| A team member cannot see the dashboard at all | The dashboard is private or the role has No Access | Fix 3 |
| Google Ads, Meta or Analytics widgets empty | Integration not connected, expired, or wrong account | Fix 4 |
| Red border and “error while loading data” | The widget’s pipeline, custom value or field is missing | Fix 5 |
Fix 1: Widgets show 0 or “No data”
HighLevel’s own troubleshooting advice for a blank widget is to check that records exist, that the date range covers them, and that filters are not excluding everything. In practice it is the filter almost every time.
- Widen the dashboard date range at the top of the page to Last 90 days or All time. If the number appears, the data is there and the range was the problem.
- Hover the widget, click the three-dot menu → Edit.
- On the Conditions tab, read every condition. Conditions in one group are joined with AND; a new group adds an OR. A single leftover condition such as Tag is “facebook” or Assigned user is Sarah can empty the widget. Remove anything you did not mean to keep.
- On the Configure tab, look for a date range override. A general widget follows the dashboard date filter unless an override pins it to a fixed period. Turn the override off unless you want it.
- For opportunity widgets, check the Pipeline filter on the widget face. Pipeline is a runtime filter there, not part of Conditions, and Stage only works once a Pipeline is selected.
- If you filter by UTM source or campaign, add First or Latest Attribution first; the UTM fields only appear after that, and they only work on Contact and Opportunity widgets.
- Click Save, then Save Changes to leave edit mode.
Fix 2: Dashboard numbers don’t match the Opportunities tab
This is the most common “the dashboard is wrong” complaint. HighLevel’s dashboard FAQ explains it: opportunity widgets moved from the Created date to the Last Status Change date. An opportunity created in March that was marked Won this week counts as this week on the dashboard, but not in an Opportunities tab filter of “created this week”. Every reopened or re-lost deal moves its date again.
To get counts that match and stay stable:
- Edit the widget and open the date property option (the filter icon on a general widget, or the Configure tab on a custom widget).
- Choose Created On if you want “new opportunities in this period”. Choose Status Change only for “deals won or lost in this period”.
- On general widgets, changing the date property on one filter updates the other general filters too, so recheck the whole row afterwards.
- Add a Status condition (for example Status is Won) rather than relying on the date to separate won from open deals.
- Compare against the Opportunities tab with the same pipeline and the same date field. Different widgets can use different date properties, so compare one widget at a time.
| Question you want answered | Date property | Extra condition |
|---|---|---|
| How many new leads entered the pipeline? | Created On | Pipeline = your sales pipeline |
| How much did we win this month? | Status Change | Status is Won |
| How many deals did we lose, and why? | Status Change | Status is Lost; group by lost reason |
| What is sitting in the pipeline right now? | Created On, wide range | Status is Open |
Fix 3: The dashboard is empty for one user, or they can’t see it
Two settings cause this, and they are easy to confuse.
Dashboard permissions decide who can open a dashboard. Each dashboard can be private or shared with Full, Edit, View or No Access per user or role, and only the owner or someone with Full access can change it. To share one:
- Open the dashboard, click the three-dot action menu → Manage Permissions.
- Turn Private off.
- Give each role or user View (read-only) or Edit access. Higher roles override lower ones, so check agency-level roles too.
- Save, then ask the user to refresh and open the dashboard selector.
Only Assigned Data decides which records a user sees once the dashboard is open. It is switched on per user in that user’s Roles & Permissions settings, and it filters dashboard widgets to records assigned to that user. An unassigned lead is invisible to them. If a widget is hard-filtered to another team member, that user sees a permission message instead of numbers. The fix:
- Remove any Assigned user is [name] condition from shared widgets.
- To give each rep their own view on one dashboard, add the condition User → Logged in user on each widget’s Conditions tab, as HighLevel recommends.
- Make sure new leads are actually assigned (a round-robin or “Assign to user” workflow action), or they will never show on a rep’s dashboard.
Fix 4: Google Ads, Meta or Google Analytics widgets are blank
Ad and Analytics widgets read from outside accounts, so they need a working connection in the same sub-account as the dashboard.
- Google Ads: go to Settings → Integrations → Google Ads and connect with your Google account, Manager account (MCC) and ad account. HighLevel says widgets show no data until this is connected, and also none when there was no ad activity in the date range.
- Meta: go to Settings → Integrations → Facebook and connect an eligible ad account. If it disconnects, the widgets stop showing data but keep their layout and settings, so reconnecting brings them back. HighLevel lists the usual causes of an empty Meta widget as a narrow date range, restrictive campaign filters, no eligible ad account selected, or missing LeadConnector permissions.
- Google Analytics: connect a GA4 property and data stream under Settings → Integrations → Google Analytics, with a Google account that has at least view access to both. Universal Analytics is not supported.
- After reconnecting, widen the date range and remove campaign or source filters, then narrow them again once data appears.
Ad numbers follow the time zone set in the ad account, while dashboard widgets use a system time zone, so small differences around midnight against Ads Manager are normal. If you want ad clicks tied to booked jobs rather than just spend, that is a conversion-tracking job: see GoHighLevel Google Ads conversions not working.
Fix 5: Red borders after a snapshot or duplicate
Dashboards can travel in snapshots and be duplicated to other sub-accounts, but the things they point at do not always travel with them. When a widget’s data source does not exist in the target sub-account, it shows a red border and “error while loading data”. Agencies have reported the same red borders on every custom widget after pushing a dashboard through a snapshot.
- When you build the snapshot, include the pipelines, custom fields and custom values the dashboard uses. HighLevel warns that leaving linked assets out causes missing-property errors.
- In the new sub-account, open each red widget in edit mode, select the pipeline, field or custom value that exists there, and save.
- For custom values, check Settings → Custom Values in the new account. Location-based values resolve from the sub-account viewing the dashboard, so make sure you are in the right one.
- Delete any widget you cannot remap rather than leaving a broken tile for the client to find.
For the wider snapshot side of this, see GoHighLevel snapshot not working.
How to build a GoHighLevel custom dashboard that works
Once the data is flowing, a custom dashboard is quick to set up. The steps below follow HighLevel’s create-a-dashboard and add-widget articles, as of November 2026.
- Decide the questions first. Write down the five to eight numbers the owner checks every week: new leads, booked appointments, show rate, won revenue, open pipeline value, unread conversations, ad spend.
- Create the dashboard. On Dashboard, open the dashboard selector, click + Add Dashboard, and choose Create a Blank Dashboard or a template from the library. Name it after its audience: “Owner weekly”, “Sales team”.
- Add widgets. Click the pencil icon, then + Add Widget. The Widget Gallery filters by module (contacts, opportunities, appointments, conversations, ads). Pick one widget per question.
- Configure each widget. Set the object, the metric (count or sum), the date property from Fix 2 and the chart type. HighLevel can sum numeric and monetary custom fields, which is useful for things like job value or deposit paid.
- Add conditions. Use the Conditions tab for permanent filters (pipeline, tag, source) and Logged in user for personal views.
- Lay it out and share it. Drag widgets by the six-dot handle so the most important number is top left, click Save Changes, then set permissions as in Fix 3.
- 1Pick the weekly questionsFive to eight numbers, no more.
- 2Add a blank dashboardDashboard selector, then + Add Dashboard.
- 3One widget per questionUse the Widget Gallery by module.
- 4Set the date propertyCreated On for leads, Status Change for wins.
- 5Add conditionsPipeline, source or Logged in user.
- 6Share with rolesManage Permissions, View or Edit.
Mistakes that make dashboards lie
- Mixing date properties on one row. A “leads” tile on Created On next to a “won” tile on Status Change is fine; two lead tiles on different date properties will never agree.
- Testing as the agency admin only. Admins see everything. Always check as the role that will use it.
- Copying a dashboard without its sources. Pipelines, custom fields and custom values must exist in the target account first.
- Leaving leads unassigned. Anyone with Only Assigned Data sees nothing until a workflow or person assigns the contact or opportunity to them.
Getting a dashboard you can trust
A blank GoHighLevel dashboard is nearly always a setting, not a bug: a leftover condition, the wrong date property, a private dashboard, Only Assigned Data, a disconnected ad account or a widget that lost its source in a snapshot. Work through the five fixes above in order and most dashboards come back in minutes.
If you would rather have it done properly, I build custom GoHighLevel dashboards wired to your real pipelines, calendars and numbers, split by role, and tested as each user before handover. If the pipelines themselves need cleaning up first, that is part of a GoHighLevel CRM setup, and agencies rolling the same dashboard out to many clients can bake it into a snapshot with snapshots and SaaS mode.
References
- How to Create & Add Dashboard Widgets — HighLevel Support Portal
- How To Create A Custom Dashboard — HighLevel Support Portal
- Configure and Filter General Widgets on your Sub-account Dashboard — HighLevel Support Portal
- Configure and filter your general widgets in sub-account dashboards — HighLevel Changelog
- Dashboard Widget Filters: Groups, OR Logic, and Chart Picker — HighLevel Support Portal
- Dashboards FAQs — HighLevel Support Portal
- Manage Dashboard Permissions in HighLevel — HighLevel Support Portal
- How to use “Only Assigned Data” setting with Dashboard — HighLevel Support Portal
- Opportunities Widgets in Dashboards & Reports — HighLevel Support Portal
- Google Ads Widgets for Dashboards & Reporting — HighLevel Support Portal
- Meta Ad Widgets for Dashboards & Reporting in HighLevel — HighLevel Support Portal
- Google Analytics Widgets for HighLevel Dashboards — HighLevel Support Portal
- How to duplicate a dashboard to another sub-account — HighLevel Support Portal
- Sub Account Dashboards: Snapshot support for Dashboard — HighLevel Changelog
- Use Custom Values in Dashboards and Custom Reports — HighLevel Support Portal
- How to add attribution and UTM parameters as filters on custom widgets — HighLevel Support Portal
- Dashboard and Custom Report available on all plans — HighLevel Changelog
- Custom Object Widgets for Dashboard and Reporting — HighLevel Support Portal
- Bug: Red Border around All Custom Dashboard Widgets from Snapshot — HighLevel Ideas





