How to Track Close Rates and Win Ratios in GoHighLevel

Written by Niyamul Islam Sajal, COO & GHL Certified AdminBlog
GoHighLevel close rate tracking: a sales manager reviewing a pipeline dashboard on a laptop

GoHighLevel close rate tracking comes down to two counts you already have, won and lost opportunities, and one decision most teams skip: what the rate is divided by. Get that wrong and the same pipeline can report 5% or 25%.

The platform won't hand you a finished percentage, so this guide shows where each input lives, which date to filter by, and how to split the result by source and salesperson.

Close rate vs win rate: two different numbers

Close rate divides deals won by every lead that came in. Win rate divides deals won by qualified opportunities only. Outreach's breakdown of win rate versus close rate puts the first at won deals divided by total leads, and the second at won deals divided by deals that passed qualification.

Its worked example uses the same 50 won deals both ways.

MeasureWon dealsDivided byResult
Close rate501,000 leads5%
Win rate50200 qualified opportunities25%

The first number tells you about lead quality and volume. The second tells you how well your reps sell once a lead is worth their time. Good GoHighLevel close rate tracking keeps both, and labels each one so nobody compares them by accident.

Inside GoHighLevel, the practical split is simple. Treat the total number of opportunities in a pipeline as your lead count. Your qualified count is whatever you decide it is, usually the opportunities that reached a particular stage.

GoHighLevel close rate tracking in five steps

Each step below fixes one thing that makes pipeline reporting unreliable, and each one feeds the rest of your GoHighLevel close rate tracking. Do them in order, because the later steps depend on the earlier ones being clean.

1. Decide what counts as won, lost and abandoned

Every opportunity carries a status, and the reports read that status, not the stage it sits in. In GoHighLevel, Won and Lost are statuses rather than pipeline stages, so a deal that never gets its status updated is invisible to every won or lost figure.

Agree a rule with your team. A deal is Won when money or a signed agreement is in. It is Lost when the prospect says no or goes silent past a set number of days. Anything you've given up on without a clear no can be Abandoned, which HighLevel counts separately.

If you also run automations that move deals, our guide to automatically moving deals between stages covers how to keep statuses current without relying on memory.

2. Put won and lost counts on a dashboard

HighLevel's documentation lists 17 opportunity widgets for dashboards and reports. The ones you need are Won Opportunities, Lost Opportunities, Opportunity Count and Opportunity Counts by Status, a donut chart that shows how everything splits.

There's no GoHighLevel win rate widget and no formula supplied among the GoHighLevel opportunity widgets. You calculate it yourself: won divided by won plus lost for a win rate on closed deals, or won divided by Opportunity Count for a close rate.

Put the three count widgets side by side on one GoHighLevel dashboard and write the division in the dashboard title or a note. Five minutes of labelling saves an argument at every monthly review of your GoHighLevel close rate tracking.

3. Choose the date property deliberately

This is where most reports quietly go wrong. Each widget can filter by Created On, Updated On or Status Change, and the default for most is Created On.

Status Change is the date an opportunity was last marked Won or Lost. It isn't the date the deal first reached that status, and if someone reopens a lost deal the date resets. The documentation warns that historical figures can drift over time for that reason.

For a stable record, filter by Created On and add a Status condition. You'll see how a month's leads eventually turned out, which is slower to settle but doesn't change behind your back. Use Status Change only for a quick read on what closed this month.

4. Split the numbers by source, owner and pipeline

An overall rate hides the useful part. Opportunity Counts by Status and Opportunity Counts Over Time both support grouping by Status, Assignee, Source, Pipeline, Stage and Lost Reason.

Group by Assignee and you see which rep converts. Group by Source and you see which channel brings buyers rather than browsers. For the second, the GoHighLevel lead source report widget is built for it: a table with Total Leads, Open, Won, Lost and Abandoned for each source, which gives you the counts for a per-channel rate at a glance.

Two cautions. The report counts opportunities rather than unique contacts, so one person with two opportunities appears twice. And opportunities with no source land under N/A, which is why capturing the lead source at entry is worth getting right first.

5. Make lost reasons required

A win rate tells you that deals are dying. Lost reasons tell you why. The Lost Opportunities By Reason donut turns every loss into a category you can count.

Lost deals saved without a reason show up as a blank or None slice, and that slice quickly becomes the biggest one. Making Lost Reason a required field on the pipeline stops it.

Reading stage-to-stage conversion with the Funnel widget

The Funnel widget answers a different question: where in the pipeline do deals stall? HighLevel explains that the Funnel counts cumulatively, so an opportunity in a later stage, or one that's Won, also counts toward every earlier section.

It offers two views. Cumulative Conversion measures each section against the start of the funnel. Next-Step Conversion measures it against the section just before. If a lot of deals reach the proposal stage but few move past it, Next-Step Conversion shows exactly that drop.

Two setup details trip people up. Stage visibility is switched on per stage in Opportunities, then Pipelines, using separate icons for the Funnel and Stages Distribution widgets. And viewers need the Dashboard Stats permission, so a rep who sees a blank widget may simply lack it.

Why GoHighLevel close rate tracking totals won't match between reports

GoHighLevel close rate tracking depends on reps updating deals: salesperson on a call at a desk

Photo by Andrea Piacquadio on Pexels

Two reports built on the same pipeline can show different won counts, and neither is wrong. Different date properties, filters and stage visibility settings produce different totals, and the Funnel widget evaluates the reporting period by last status change date, not created date.

For GoHighLevel close rate tracking that people trust, compare the settings before you compare the numbers. Fix one date property, one pipeline and one definition of qualified, then write them down so the next person builds reports the same way.

We've built and configured 100+ GHL accounts, and agreeing statuses before rebuilding dashboards around them is a step we don't skip. If you want to see these widgets working before committing time, the HighLevel Bootcamp 30 day trial gives you an account to build them in.

Teams that would rather not build them at all can hand the dashboards and pipeline clean-up to our GoHighLevel automation team.

Frequently asked questions

Does GoHighLevel have a win rate widget?

Not by that name. The opportunity widget list has won, lost and count widgets, and you divide them yourself. The documentation mentions a this-month win rate in its overview but gives no widget or formula for it.

Why did last month's won count change?

Almost certainly because the report filters by Status Change. Reopening a lost deal or re-marking one updates that date retroactively. Filter by Created On with a Status condition for figures that stay put.

Can I see the GoHighLevel win rate for one salesperson?

Yes. Group the status widgets by Assignee, or filter to one Assigned User. The For You versions of the This Month widgets filter to whoever is logged in.

Should close rate include unqualified leads?

Close rate does by definition. If you want a measure of how well reps sell, use win rate on qualified opportunities, and state which one each dashboard shows. Our sales pipeline build guide shows how to mark the qualifying stage.

Sources

Cover photo by Serpstat on Pexels

Need help implementing this in GoHighLevel?

Our team builds, automates, and scales GoHighLevel systems for agencies every day. Book a free call and we'll map out exactly what to ship next.

Book a free call