GoHighLevel Dashboards & Reporting Guide (2026)
GoHighLevel Dashboards & Reporting Guide (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 1 August 2026 · 8 min read
On this page: What HighLevel dashboards actually report on · Building custom GoHighLevel dashboards · Permissions: who sees which dashboard · The agency play: one client dashboard, deployed by snapshot · The 6–8 KPIs that matter (and the vanity metrics that don't) · Recommended dashboard layout · Attribution reporting: source, UTM, first vs latest touch · Scheduled reports vs logging in · Common mistakes to avoid · FAQ · Related articles
GoHighLevel dashboards are the first screen most owners and clients see when they log in, and for years they were the weakest part of the platform — one fixed layout, no customisation, take it or leave it. That changed properly with the customisable dashboard builder: multiple dashboards per sub-account, a widget library, permission controls, and the ability to chart custom fields. It is now a genuinely usable reporting layer, if you set it up deliberately.
The catch is that a dashboard is only a mirror. It reflects whatever data your team puts into pipelines, calendars and contact records. In this guide I'll walk through how to build custom dashboards, which widgets earn their screen space, how agencies standardise client reporting with snapshots, and the data hygiene habits that keep the numbers honest. This is the setup I deploy for Australian service businesses week in, week out.
What HighLevel dashboards actually report on
Out of the box, every sub-account gets a default dashboard showing opportunity metrics (total pipeline value, opportunities by status), funnel and stage distribution charts, task counts, appointment stats and conversation activity. It's a reasonable starting point and a terrible finishing point, because it reports on everything equally — which means it prioritises nothing.
The reporting layer goes deeper than the dashboard itself. Under Reporting you'll find dedicated views for Google Ads, Facebook Ads, call reporting, appointment reporting and attribution. The dashboard builder can pull most of this into widgets, so in practice the dashboard becomes the summary and the Reporting tab becomes the drill-down. The HighLevel help centre documents each widget type if you want the full catalogue, but you won't need most of it — more on that below.
Building custom GoHighLevel dashboards
Open the Dashboard in any sub-account and hit the edit (customise) control. From there you can add, remove, resize and rearrange widgets on a grid, then save. You can also create additional dashboards — so rather than cramming everything onto one screen, build several: an owner's dashboard, a sales dashboard, a marketing dashboard, a front-desk dashboard. Each one answers a different question for a different person.
Widget types worth knowing
The widget library breaks down into a few useful families:
- Opportunity widgets — pipeline value, opportunity counts, win/loss, conversion between stages, and funnel/stage distribution charts. These are only as good as your pipeline hygiene, which is why I always pair dashboard work with a proper GoHighLevel pipelines and opportunities build.
- Task and appointment widgets — open tasks by assignee, appointments booked, confirmed, showed and no-showed. Show rate lives here, and it's one of the most valuable numbers in the whole account.
- Communication widgets — call volume and outcomes, SMS sent/received, email delivery, open and reply stats via Mailgun or your SMTP provider.
- Ad reporting widgets — spend, leads and cost-per-lead pulled from your connected Meta and Google accounts. If you run paid traffic through the GoHighLevel Ad Manager, these widgets close the loop between spend and pipeline on one screen.
- Custom widgets — chart or count contacts and opportunities filtered by custom fields and tags. This is the sleeper feature: if you capture "service type" or "suburb" as a custom field, you can build a widget showing leads by service line without exporting anything.
A practical build order: start with a blank dashboard, add one widget per KPI you've already agreed on (next section), and stop. Resist the urge to add a widget just because it renders a pretty chart.
Permissions: who sees which dashboard
Each dashboard has permission settings controlling which users and roles can view or edit it. This matters more than people think. Your front-desk team needs appointments and tasks, not revenue. Your client (in an agency context) needs outcomes, not the internal ops board. Admin users can create and edit dashboards; standard users see only what's shared with them, and you can set a specific dashboard as the default view for a role so people land on the right screen at login.
The rule I use: one dashboard per audience, permissioned so each audience sees exactly one screen by default. The moment a salesperson has to choose between six dashboards, they'll look at none of them.
The agency play: one client dashboard, deployed by snapshot
If you run an agency, do not hand-build a dashboard per client. Design one standard client-facing dashboard — leads this month, booking rate, show rate, close rate, revenue collected, reviews gathered — and bake it into your snapshot. Every new sub-account then spins up with identical reporting, every client review call uses the same screen, and your account managers can read any client's numbers in ten seconds because the layout never changes.
This standardisation is also a retention tool. Clients churn when they can't see value. A dashboard that opens on "42 leads, 61% booked, $18,400 collected" makes the value argument for you before you say a word. Pair it with automated review requests and payment tracking — the revenue widget is far more compelling when GoHighLevel payments are running through the platform, because collected revenue then appears without any manual entry.
The 6–8 KPIs that matter (and the vanity metrics that don't)
For a service business — trades, clinics, gyms, professional services — the funnel is nearly always: lead → booking → show → close → revenue → review. So the dashboard should report exactly that chain:
- New leads (by source)
- Booking rate — leads who book an appointment
- Show rate — booked appointments that actually happen
- Close rate — shows that become paying customers
- Revenue — collected, not quoted
- Review count — new Google reviews this month
- Optionally: speed to lead and cost per lead if you're running ads
Everything else is decoration. Email open rates, total contacts in the database, social impressions, page views — these are vanity metrics on an owner's dashboard. They can matter diagnostically (a collapsing open rate signals a deliverability problem), but they belong on a marketing dashboard the operator checks weekly, not the screen a business owner uses to run the company.
Recommended dashboard layout
Here's the standard layout I deploy for service-business clients. Targets are typical ranges for local service businesses with decent follow-up automation in place; treat them as starting benchmarks, not gospel.
| Widget | Metric | Why it matters | Target range |
|---|---|---|---|
| Leads by source (bar chart) | New contacts this month, split by attribution source | Shows which channels deserve budget and which are dead weight | Growing month on month; no single source over 70% |
| Booking rate (number card) | Leads → appointments booked | Measures speed to lead and nurture quality | 30–50% |
| Show rate (number card) | Booked → attended | Reveals whether reminder sequences are doing their job | 70–85% |
| Close rate (number card) | Shows → won opportunities | Isolates sales performance from marketing performance | 25–40% |
| Revenue collected (number card) | Payments received this month | The only metric that pays wages; collected beats quoted | Tracking to monthly goal |
| Pipeline by stage (funnel chart) | Open opportunity value per stage | Forecasts next month and exposes stage bottlenecks | No stage holding >40% of pipeline value |
| Reviews gained (number card) | New reviews this period | Compounding local SEO and social proof asset | 5–15+ per month |
| Cost per lead (ad widget) | Spend ÷ leads by campaign | Keeps paid channels accountable to real CRM data | Stable or falling; varies by niche |
Attribution reporting: source, UTM, first vs latest touch
HighLevel stamps every contact with attribution data: session source, referrer, campaign, and UTM parameters — captured for both the first touch (how they originally found you) and the latest touch (what triggered this particular enquiry). Both views appear in attribution reporting and can drive dashboard widgets.
The distinction matters commercially. First touch tells you which channels create demand; latest touch tells you which channels convert it. A lead might discover you through a Facebook ad in March and convert off a Google search in June — first-touch credits Meta, latest-touch credits Google, and both are true. My advice: report first touch on the owner dashboard (budget decisions) and use latest touch when auditing individual campaign performance. And make sure your forms, GoHighLevel calendars and landing pages all carry UTM parameters consistently, or the source column degrades into a wall of "direct traffic".
Scheduled reports vs logging in
Here's an uncomfortable truth: most business owners will not log in to look at a dashboard, no matter how good it is. The fix is to push the numbers to them. HighLevel can email scheduled reports on a daily, weekly or monthly cadence, so the Monday-morning summary lands in the inbox whether or not anyone remembered to check. For agencies, a weekly automated client report quietly answers "what am I paying you for?" fifty-two times a year.
You can extend this with GoHighLevel Workflows for the operational layer: internal notifications when an opportunity sits in a stage too long, or a Slack/SMS alert when a high-value deal moves to won. Dashboards answer "how are we going?"; workflow alerts answer "what needs attention right now?". You need both. The platform's own feature updates at gohighlevel.com keep expanding what's schedulable, so revisit this quarterly.
Common mistakes to avoid
- Reporting on a dirty pipeline. If your team doesn't move opportunities through stages, every conversion widget is fiction. Dashboard accuracy is a pipeline-hygiene problem first and a widget problem second.
- One mega-dashboard for everyone. Twenty widgets on one screen means nobody reads any of them. Build one dashboard per audience and permission accordingly.
- Charting vanity metrics for owners. Total contacts and email opens don't pay wages. Keep the owner's screen to the lead-to-revenue chain.
- Ignoring latest-touch attribution. Judging every channel on first touch alone undervalues the retargeting and nurture activity that actually converts aged leads.
- Hand-building client dashboards. Agencies that rebuild reporting per client end up with inconsistent layouts and unbillable admin. Standardise it once in the snapshot.
- Expecting logins instead of scheduling reports. If the numbers aren't emailed automatically, assume they're not being seen.
If you want a dashboard that shows exactly where your leads and revenue come from, book a strategy call with the HL Growth Partner team.
Frequently asked questions
Can I create multiple GoHighLevel dashboards in one sub-account?
Yes. The dashboard builder supports multiple dashboards per sub-account, each with its own widgets and permission settings. The practical pattern is one dashboard per audience — owner, sales, marketing, front desk — with each role defaulting to the screen that's relevant to them.
Can clients see dashboards without seeing everything else?
Yes. Create a client user with restricted permissions and share only the client-facing dashboard with that role. Combined with menu customisation at the agency level, you can give clients a clean reporting view without exposing workflows, snapshots or other sub-accounts.
Can dashboards report on custom fields?
They can. Custom widgets can count and chart contacts or opportunities filtered by custom-field values and tags — for example, leads by service type or enquiries by suburb. This is one of the most underused features in the builder and often removes the need for spreadsheet exports entirely.
What's the difference between first-touch and latest-touch attribution?
First touch records how a contact originally found you; latest touch records the session that preceded their most recent conversion. First touch is best for channel budget decisions, latest touch for evaluating retargeting and nurture campaigns. HighLevel captures both automatically, including UTM parameters.
Why don't my dashboard numbers match reality?
Almost always a data-entry problem, not a software problem. Opportunities left in old stages, appointments never marked as showed or no-showed, and missing UTM tags all corrupt the underlying data. Fix the pipeline and calendar hygiene habits first, then re-check the widgets — the dashboard only reflects what the CRM is told.
