How to Track Lead Sources in GoHighLevel for Better Marketing ROI

A contact with no recorded source is the most expensive kind, because you paid to get it and can't say what paid for it. GoHighLevel lead source tracking fixes that, but only if the source is captured when the lead arrives and read back from the right report afterwards.
This guide covers the part a basic overview doesn't: wiring UTMs through embedded forms, knowing which report counts what, and turning the numbers into a marketing ROI decision.
How GoHighLevel records where a contact came from
Under the hood, GoHighLevel lead source tracking keeps two attributions per contact: a first one and a latest one.
According to HighLevel's help article on attribution traffic sources, last modified on 26 August 2026, first attribution is set at the contact's first interaction and never changes, while latest attribution is the most recent recorded interaction and updates each time.
You'll find both on the contact record, in the right-hand column under the Activity tab.
Attribution is recorded when the visitor does something that identifies them in the same session: submitting a form or survey, booking on a calendar, using the chat widget after giving contact details, or completing an order form. A visitor who browses on Monday and submits on Thursday from a different link will show a different latest source from their first, and both facts are useful.
Which source category a click lands in
HighLevel sorts traffic into categories by checking rules in a fixed order. The ones you'll meet most often in paid campaigns are below, taken from the same help article.
| Signal in the URL | Category it lands in |
|---|---|
| utm_source containing "adwords" | Paid Search |
| gclid, wbraid, gbraid or msclkid | Paid Search |
| fb_ad | Paid Social |
| linkedin_ad, twitter_ad or reddit_ad | Paid Social |
Other traffic falls into Direct Traffic, Organic Search, Social Media, Referrals, CRM UI, Third-Party or Others. The article also says utm_source=facebook is deprecated, so use fb_ad on Facebook links, and that UTM parameters are case-sensitive.
Five steps to set up GoHighLevel lead source tracking on any form
Native attribution works well on HighLevel's own funnels and websites. The gap opens when a HighLevel form is embedded on a site you don't host there, because the iframe can't read the parent page's address by default. These five steps close it, following GHL Experts' guide to embedding forms with UTM parameters, published on 14 August 2026.
- Create the custom fields. Under Settings, then Custom Fields, add text fields named utm_source, utm_medium, utm_campaign, utm_term and utm_content. The query key must match exactly, including case.
- Add them to the form as hidden fields. In the form builder, drop each field in and switch on the Hidden toggle in the right sidebar.
- Pass the URL parameters into the embed. Use the form embed script plus a small snippet that reads the page's query string and appends it to the iframe address. A localStorage snippet can carry the values across pages.
- Test with a tagged link. Open the page with utm_source and utm_campaign in the address, submit the form, then open the new contact and check the Additional Info tab for those values.
- Standardise your naming. Decide once that it's always lowercase and always the same campaign labels, and give the list to whoever builds your ads.
Step five sounds trivial and causes most of the damage later. "Facebook", "facebook" and "fb" become three sources in every report you build afterwards.
If you'd rather not touch snippets and hidden fields yourself, our team handles this as part of GoHighLevel setup, and we've built and configured more than 100 GHL accounts.
Reading the Lead Source Report without fooling yourself
The reporting side of GoHighLevel lead source tracking is a dashboard widget, not a menu item. Open the Dashboard, choose Edit dashboard, add the widget from the gallery, pick a pipeline, set your conditions and date settings, and save, as the Lead Source Report help article (modified 30 October 2026) describes.
It shows, for each source, total leads plus how many are open, won, lost and abandoned.
Two details change how you read it. It counts opportunities, not unique contacts, so a contact with three opportunities appears three times. And it groups by the opportunity's recorded source, not by UTM parameters, which are offered only as extra attribution filters.
Any opportunity with no source lands in an N/A row. A large N/A row is the clearest sign that step three above has a hole in it.
Filters worth setting
The widget can filter by pipeline, assigned user, source, attribution, tags, lead value and custom fields, and by either created date or status change date. Use created date to ask which channels brought leads in during a month. Use status change date to ask which channels closed deals in that month, since those are often different groups.
From GoHighLevel lead source tracking to marketing ROI

Photo by RDNE Stock project on Pexels
Good lead source tracking in GoHighLevel starts with volume: lead count tells you where it comes from. Won opportunities tell you where revenue comes from, and the two rankings rarely match. A channel that fills the pipeline with open and lost opportunities is costing you follow-up time, whatever its cost per lead looks like on the ad platform.
To make the comparison fair, put the ad spend per channel beside the won count and the lead value for the same period. HighLevel's report can compare opportunity values across sources where your permissions allow it, so check that your user role can see lead values before you build the view.
Source data also feeds the rest of the CRM. Segments built on source and tags power the GoHighLevel smart lists that target campaigns, and a clean source field helps when you manage leads from first touch to close. Once you trust the source, automation can route a paid-search lead to a different follow-up than a referral.
If you're still deciding on the platform, HighLevel runs a 30 day HighLevel Bootcamp trial where you can build the form and report above on your own account.
Why leads end up with the wrong source
Most bad source data comes from the journey, not the software. The GHL Experts guide lists the usual culprits: the iframe can't read the parent URL, redirects strip UTM parameters, and caching plugins block the script that passes them along.
HighLevel's own troubleshooting advice adds two more. The visitor has to stay on the final URL until they submit the form, and custom UTM parameters shouldn't be added to its Google Ads and Facebook templates.
Run your tagged test link after every site change, redirect or plugin update. It takes two minutes and saves a month of reports you can't trust.
Treat GoHighLevel lead source tracking as something you re-verify, not something you set up once, and the Lead Source Report stays worth reading.
Frequently asked questions
Does GoHighLevel keep the first source or the latest one?
Both. First attribution never changes once it's set, and latest attribution updates with each new recorded interaction. Compare them on the contact record to see how a lead found you and what brought them back.
Why does my Lead Source Report show an N/A row?
Those are opportunities with no recorded source. Check that your forms and calendars capture attribution, and that embedded forms pass the UTM values through.
Does the Lead Source Report count contacts or opportunities?
Opportunities. If one contact has several, each is counted separately, so totals can be higher than your contact count.
Can I use GoHighLevel lead source tracking on a form embedded outside HighLevel?
Yes, with hidden custom fields for the UTM values and a snippet that appends the page's query string to the form's iframe address. Test it with a tagged link before you spend on ads.
Sources
- Understanding Attribution Traffic Sources — HighLevel Support
- Lead Source Report: See Leads, Status, and Value by Source — HighLevel Support
- How to Embed GoHighLevel Forms with UTM Parameters on External Websites — GHL Experts
Cover photo by Omar Ashraf 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