How to track lead sources in GoHighLevel (UTMs, Meta Pixel and Conversions API)

By / Published Nov 18, 2026 / Updated Nov 18, 2026

Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.

GoHighLevel tracks lead sources on its own: every time someone submits a HighLevel form, survey, calendar, chat widget or order form, it saves a First Attribution and a Latest Attribution on the contact, with the channel (Paid Search, Paid Social, Organic, Direct and so on) and any UTMs in the page URL. To make that data accurate you tag your ads with HighLevel's exact UTM templates (utm_source=adwords for Google, utm_source=fb_ad for Meta), keep the form on the page the ad lands on, and then report on it with Attribution filters in dashboard widgets.

When I take on a client the first thing I want to know is where their leads actually come from. With my daycare client, "the first thing I did was I looked at their traffic numbers online so I looked at their Google analytics I looked at their Google my business profile", and it turned out "the issue stemmed from lead conversion and lead capture", not traffic. You can't make that call without clean source data. Below: how HighLevel decides a source, why so many leads land in "Others", UTMs through embedded forms and iframes, Meta Pixel plus Conversions API without double counting, Google Ads offline conversions, GA4, dashboards and a troubleshooting table. Everything is checked against HighLevel's help docs and changelog on Nov 18, 2026.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Short version

  • 01Every contact gets First Attribution (never changes) and Latest Attribution (updates on each new tracked visit). Find them on the contact's Activity tab.
  • 02HighLevel's UTMs are case-sensitive. Google: utm_source=adwords plus the gclid. Meta: utm_source=fb_ad (utm_source=facebook is deprecated). Add nothing extra to HighLevel's templates.
  • 03"Others" means the lead came in by call, SMS, email, WhatsApp or Facebook message, with no tracked web visit. Fix it with a number pool for calls and by sending people to a form, calendar or chat widget.
  • 04The form must be submitted on the landing page. If the visitor clicks to a second page first, the UTMs are lost. Use a popup or put the form on the landing page.
  • 05Meta: use the funnel's Events tab with Conversions API on, not a pasted pixel script as well. HighLevel dedupes browser and server events with a shared event ID. Pick one way per event.
  • 06Google Ads: HighLevel sends offline conversions only, with the Add to Google Ads workflow action, and only for contacts that have a gclid, gbraid or wbraid.

Set up lead source tracking in GoHighLevel, in order

  1. 01

    Capture leads with HighLevel's own tools

    Use HighLevel forms, surveys, calendars, the chat widget or order forms, on a HighLevel funnel or embedded with the full embed code. Those are the events that record attribution. On a site with its own forms, install External Tracking (Settings > External Tracking) instead.

  2. 02

    Tag every ad with HighLevel's UTM templates

    Google Ads: put HighLevel's tracking template at account level. Meta: in each ad, Tracking > Build a URL parameter with source fb_ad, medium {{adset.name}}, campaign {{campaign.name}}, content {{ad.name}} and campaign_id {{campaign.id}}. Copy and paste them, they're case-sensitive.

  3. 03

    Keep the form on the landing page

    The ad's final URL has to be the page where the form gets submitted. Use a popup or an on-page form section if the page has a "get started" button.

  4. 04

    Add calls and messages

    Set up a number pool under Settings > Phone System > Phone numbers > + Add Number > Add Number Pool > Visitors Activity, and paste its script on the site, so phone leads get a source too.

  5. 05

    Send conversions back to the ad platforms

    Meta: the funnel's Events tab with Conversions API, or the Facebook Conversion API workflow action. Google: create an offline conversion action, then the Add to Google Ads workflow action. GA4: the Add to Google Analytics action.

  6. 06

    Build the report

    Dashboard > Edit > add a Contact or Opportunity widget, Conditions > Add Filter > Attribution > First or Latest, then filter or group by Session Source, Medium or UTM fields. Add the Lead Source Report widget for value by source.

  7. 07

    Test with a real click

    Open the live ad link (not a preview) or a URL with your UTMs, submit the form, and check the contact's attribution, the workflow's Execution Logs, Meta Events Manager and Google Ads.

How GoHighLevel records attribution: first vs latest

HighLevel stores two attribution records on every contact. First Attribution is the session of their first tracked interaction, like the first form they filled out, and it never changes. Latest Attribution is the most recent tracked interaction, so if that same person later buys through a two-step order form, Latest updates and First stays put. You'll find both on the contact record, Activity tab, bottom right.

Attribution only gets recorded when someone does one of these in a session: submits a form or survey, books on a calendar, submits contact details in the chat widget, or submits a one-step or two-step order form. Forms on outside sites count too when External Tracking picks them up. A contact you add by hand gets CRM UI, not a channel.

Use First for "which channel finds us new people" and Latest for "which channel brought them back to buy". A contact can easily be Organic Search on First and Paid Social on Latest, and that's not a bug.

If this is trueSession Source
utm_source contains adwords, or the URL has gclid, gbraid, wbraid (Google) or msclkid (Microsoft), or any utm_ tag with google.com as referrerPaid Search
utm_source contains fb_ad, linkedin_ad, twitter_ad or reddit_ad, or a ctwa_clid (click-to-WhatsApp)Paid Social
Referrer is a social siteSocial Media
Referrer is a search engine (Google, Yahoo, Bing, DuckDuckGo)Organic Search
Referrer is any other siteReferral
No referrer and no tracking parametersDirect Traffic
Lead came from a call, SMS, email, WhatsApp or Facebook message, or anything not covered aboveOthers
Contact created by hand in the CRMCRM UI
Contact created by a third-party tool like ZapierThird-Party

HighLevel's rules, applied in this order, from Understanding Attribution Source (modified Aug 26, 2026), read Nov 18, 2026.

Session Source, Medium, UTM Source and the Source field are four different things

This trips everyone up, so get it straight before you build reports. Session Source is HighLevel's channel bucket from the table above. Medium is how they converted: a form, survey, calendar, API and so on. UTM Source is the raw utm_source value from the URL. And the plain Source field (Contact Source) is something else again.

Contact Source comes from the Source element you can drop into a HighLevel form or survey. It's hidden from the person filling it in and writes a fixed value, and adding ?source=google-profile to the form link overrides it for that submission. HighLevel's own doc says it's not the same as attribution or utm_source. It's handy for things UTMs don't cover, like one form shared on the Google Business Profile, a QR code and a flyer.

The Facebook Ad Reporting doc also lists custom values you can drop into notifications or copy into custom fields with an Update Contact Field action: {{contact.attributionSource.utmCampaign}}, utmMedium (the ad set), utmContent (the ad), campaignId, fbclid, gclid and referrer. Test which touch they return on your account before you build reports on them.

Why your leads show as "Others" (and how to fix it)

"Source shows as other" is one of the most common attribution complaints on Reddit. In HighLevel, Others means the contact came in through an incoming call, SMS, email, WhatsApp or Facebook message, or some route that isn't a tracked web session. It doesn't mean HighLevel lost the data. It never had a web visit to read.

The fixes, in the order I'd do them. Calls: set up a number pool so the number on the site swaps per visitor, then calls get tied to the visit (HighLevel's Facebook reporting doc also notes inbound click-to-call works, but calls straight to a number pool number don't get first attribution). Messages: send people from ads to a form, calendar or chat widget, and use the chat widget on the site, since a chat with contact details records attribution and a plain DM doesn't. Paid traffic that lands as Direct: check your UTMs, because a typo, a capital letter or utm_source=facebook drops paid clicks into Direct or Others.

Also check where the contact came from in the first place. Contacts created by Zapier and similar tools show Third-Party, and contacts added by hand show CRM UI. If a client's leads come through a third-party form tool, send the UTMs in the payload and map them to custom fields, or switch to External Tracking (more below).

UTM parameters: native forms vs embedded forms vs iframes

Native: a HighLevel form on a HighLevel funnel or website reads the page URL directly. This is the most reliable setup. If the ad points at a funnel step with the form on it, you're done.

Embedded on another site: use the whole embed code from the form's Integrate tab (Sites > Forms > open the form > Integrate > Copy Embed Code). It's an iframe plus HighLevel's form_embed.js script. I checked the live script on Nov 18, 2026: it reads the parent page's URL parameters and passes the utm_ values into the form iframe. Paste only the iframe and that handoff is gone. React builders like Lovable often drop the script, which is the same problem, and the fix is on Connect GHL to any website. Test it: open the page with ?utm_source=test&utm_campaign=test, submit, and check the contact's attribution.

The site's own form: install External Tracking (Settings > External Tracking, paste the script before the closing body tag on every page). It catches standard HTML forms like Gravity Forms, WPForms and Contact Form 7 and records UTMs, page URL and session data. Forms inside an iframe aren't supported by the original version. The new External Tracking in Labs adds two-snippet iframe tracking (Settings > External Tracking > Installation > Tracking code > iFrame forms: one snippet on the page that hosts the form, one on the parent page). Nested iframes, like some Wix HTML embeds, still can't be tracked.

Hidden fields: HighLevel's documented workaround for putting your own value into a form is a Custom HTML/JavaScript element that sets a custom field and fires an input event, for example document.getElementsByName('your_field_id')[0].value = myData followed by dispatchEvent(new Event("input")). Get the field's ID by inspecting the form in preview. Use it when you need something HighLevel's attribution doesn't keep, like a click ID from another ad network. For normal UTMs you shouldn't need it.

One more catch from HighLevel's attribution doc: the form has to be submitted on the final URL the ad sends people to. If the visitor clicks "get a quote" and lands on a second page to submit, the UTMs aren't recorded. Put the form on the landing page or open it in a popup.

The exact UTM templates for Google and Meta ads

Google Ads, as the tracking template at account level (HighLevel recommends account level over campaign or ad group), from HighLevel's Google Ad Reporting doc:

{lpurl}?utm_source=adwords&utm_medium={adname}&utm_campaign={campaignname}&utm_content={adgroupname}&utm_keyword={keyword}&utm_matchtype={matchtype}&campaign_id={campaignid}&ad_group_id={adgroupid}&ad_id={creative}

Make sure the gclid reaches the page too (Google Ads auto-tagging adds it), because it's what the offline conversion upload needs. HighLevel also has an optional Google Ads script that reapplies this template hourly as a fail-safe (Tools and Settings > Bulk Actions > Scripts). That doc is from 2022, so check the menu in your Google Ads account.

Meta, in each ad: Tracking > Build a URL parameter. Campaign Source fb_ad, Campaign Medium {{adset.name}}, Campaign Name {{campaign.name}}, Campaign Content {{ad.name}}, then Add Parameter with the name campaign_id and value {{campaign.id}}. HighLevel recommends this even for lead form ads.

Three Meta rules from that doc (updated Nov 18, 2026) that people break all the time. Give every campaign, ad set and ad a unique name. Don't rename them mid-flight, because HighLevel keeps the original name, so make a new one instead. And don't use emojis or special characters in names. Also, Meta doesn't add the parameters when you preview an ad, so don't test from the preview.

Meta Pixel and Conversions API without double counting

There are two places HighLevel sends Meta events from, and double counting nearly always comes from using both for the same event, or pasting the pixel twice.

1. The funnel or website Events tab. Open the funnel or website, go to the Events tab, click Add event, enter the Pixel ID, choose funnel level or specific pages, and turn on Conversions API with an access token from Events Manager. Since Mar 19, 2026 this sends PageView, ViewContent, InitiateCheckout, AddPaymentInfo and Purchase through the browser pixel and CAPI together, and HighLevel says the pair is deduplicated in Events Manager. Purchase uses the real order ID as its event ID. HighLevel's warning in that release: add events from the Events tab only. Events tab tracking plus a pixel script pasted in Settings gives inconsistent results.

2. The Facebook Conversion API workflow action. Automation > Workflows, trigger Form Submitted, Survey Submitted, Customer Booked Appointment (use this one for calendar widget bookings, not the general Appointment trigger) or Order Form Submission, then the Facebook Conversion API action with Event Type Funnel Event, the Access Token and the Pixel ID (the Dataset ID in Events Manager). If the dataset was made in Ad Manager (Ad Manager > Settings > Meta > Conversions > + Create new dataset), pick the Ad Manager connection and HighLevel handles the token. When you create the dataset in Meta, tick Event ID under the parameters, as HighLevel's setup doc says. HighLevel's CAPI doc, updated Nov 17, 2026, says it handles deduplication for supported funnel events by sending an event ID to Meta.

Where it goes wrong: a Lead event you typed into a thank-you page script has no event ID that HighLevel knows about, so if a workflow also sends Lead by CAPI for the same submission, Meta can count it twice. Same if the base pixel sits in both the funnel settings and a page's tracking code, which HighLevel's tracking code doc flags as a cause of duplicate events. My rule: one browser source and one server source per event, and nothing hand-pasted on top of the Events tab. If you're on the old setup and move to the Events tab, HighLevel switches off each legacy event (SubmitApplication, OrderFormPurchase) only when you've configured its replacement, as of Jun 11, 2026.

Two more things. The workflow action doesn't create Facebook attribution. If the contact has no fbclid or Paid Social attribution, the event goes to Meta but can't be tied to an ad. And if the site has a cookie banner, HighLevel doesn't send pixel events for visitors who haven't accepted advertising cookies.

For lead form ads (Instant Forms), sending lead quality back to Meta works differently, with Lead Events on Pipeline Stage Change. That setup, and Meta's volume rules for Conversion Leads, are on Facebook lead ads.

GA4: page views on funnels and conversion events from workflows

For page views, paste the GA4 Google tag (or GTM) once in the funnel or website settings under Head tracking code, so it runs on every page. Page-level code is for events that should only fire on one page, and it isn't copied when you duplicate a step. Scripts won't show in View Page Source because HighLevel adds them in the browser, so check with Tag Assistant or GA4's Realtime report. More on where tracking code goes is in Build a funnel.

For events that happen in the CRM, like a booked appointment or a won deal, use the Add to Google Analytics workflow action. Set Action Type to Google Analytics 4, then the Measurement ID and an API Secret, both from GA4 Admin > Data Streams > your stream (the secret is under Measurement Protocol API secrets). Give it an event name and an optional value. No spaces around the pasted secret, and allow 24 to 48 hours before the event shows in GA4.

Attribution in reporting: UTM filters on dashboard widgets

HighLevel's attribution filters only work on Contact and Opportunity widgets. Go to Dashboard, open the dashboard in Edit mode, add or edit a Contact or Opportunity widget, then Conditions > Add Filter > Attribution and pick First Attribution or Latest Attribution. That step has to come first, because the UTM fields only appear after it. Then click +AND and add Session Source, Medium, UTM Source, UTM Medium, UTM Campaign, UTM Campaign ID, UTM Keyword, UTM Content, UTM Matchtype, UTM Ad ID or UTM Ad Group ID.

Text fields like UTM Source and UTM Campaign use Contains, and ID fields use Is or Is not. To group a chart by Session Source or Medium, keep everything in one filter group, because adding an OR group makes those grouping options disappear. For a client table, switch the widget to Table and pick the attribution columns under Select Columns. Click a saved widget to see the records behind it and export them.

Add the Lead Source Report widget too (Edit dashboard > Add widget > Lead Source Report). It groups opportunities by source with Open, Won, Lost and Abandoned counts and their value, and since Oct 6, 2026 you can click any count to see the deals behind it. It counts opportunities, not contacts. Filter Source by "Is empty" to find deals with no source and fix them.

For my daycare client, when I wanted to show the ad results, it was right inside HighLevel: "I can verify that through the reporting tab here so if I go to Facebook ads". That's the report clients actually look at. Build the dashboard once, put it in a snapshot, and every new client starts with it.

Troubleshooting lead source tracking

Go down this table before you open a support ticket. Most of these are in HighLevel's own attribution, CAPI and Google Ads docs, read Nov 18, 2026.

ProblemLikely causeFix
Leads show as OthersThey came in by call, SMS, email, WhatsApp or DM, not a tracked web formNumber pool for calls, send ad traffic to a form, calendar or chat widget
Facebook ad leads show as DirectUTMs missing, typo, wrong case, or utm_source=facebookRebuild the URL parameters with fb_ad exactly as HighLevel's template
UTMs missing on an embedded formOnly the iframe was pasted, or the script didn't load (React sites)Paste the full embed code with form_embed.js and test with ?utm_source=test
UTMs missing even on a funnelThe form was submitted on a second pageForm on the landing page, or a popup
Site's own form not capturedForm is in an iframe or has no name attributesExternal Tracking, with the Labs iframe snippets if needed
Meta shows double Leads or PurchasesEvents tab plus a pasted script, or pixel at funnel and page levelEvents tab only, one browser and one server source per event
CAPI event not in Events ManagerWrong Pixel/Dataset ID or token, domain not allowed, workflow not publishedCheck Diagnostics and the domain allow list, then test with a real submission
Add to Google Ads says SkippedNo gclid, gbraid or wbraid, or the conversion name doesn't matchTest from a real ad click and copy the exact conversion name
Google Ads report shows 0 leadsFirst attribution isn't Paid Search with utm_source=adwords and a gclidAccount-level tracking template and auto-tagging
UTM fields missing in a widgetNot a Contact or Opportunity widget, or no Attribution condition yetAdd Attribution > First or Latest first
Pixel events missing for some visitorsCookie banner: they didn't accept advertising cookiesExpected. Server events from workflows still run

Common lead source problems in GoHighLevel and the fix for each.

How to test without fooling yourself

HighLevel's docs disagree on whether the workflow Test button sends a usable Conversions API event, and its CAPI doc updated Nov 17, 2026 says to publish the workflow and do the real action instead. So I test with real actions: open the live URL with UTMs from a phone, submit the form, then check the contact's Activity tab, the workflow's Execution Logs, Events Manager's Test Events and Diagnostics, and Google Ads conversions a day later.

Use a new email and phone for each test. If the details match an existing contact, HighLevel updates that contact, and Latest Attribution changes while First stays the same, which looks like tracking is broken when it isn't.

How to sell this to a local business

Most local businesses running ads can't tell you which ad made the phone ring. That's the opener. Look at their site: if the form is a plain contact plugin with no UTMs and their ads go to the home page, they can't see it either.

Sell it as "you'll know which ads bring in customers": HighLevel forms or External Tracking, UTMs on every ad, a number pool for calls, conversions sent back to Meta and Google, and one dashboard with source and value. You could build this for a local business and charge a setup fee plus a monthly fee you set. Then pair it with fast follow-up, because a tracked lead nobody calls back is still a lost lead. That piece is on GoHighLevel workflows.

Start the 30-day trial and set up tracking on your first funnel →
Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Other ways to start

My bonuses come with every one of these.

Best if you're new and want live help setting up

30-day trial + a free live setup bootcamp

Best if you're not sure which plan you need

Compare all 3 plans first

Best if you'll resell HighLevel as your own software

Go straight to the $497 Founder plan

FAQ

How does GoHighLevel track lead sources?

It saves First and Latest Attribution on each contact when they submit a HighLevel form, survey, calendar, chat widget or order form, or a form caught by External Tracking. It reads the page URL and referrer and sorts the lead into Paid Search, Paid Social, Organic, Social, Referral, Direct, Others, CRM UI or Third-Party.

What does "Others" mean as a lead source in GoHighLevel?

The lead came from an incoming call, SMS, email, WhatsApp or Facebook message, or another route without a tracked web visit. Use a number pool for calls and send ad traffic to a form, calendar or chat widget.

What UTM parameters does GoHighLevel need?

For Google, utm_source=adwords with HighLevel's full tracking template plus the gclid. For Meta, utm_source=fb_ad, utm_medium={{adset.name}}, utm_campaign={{campaign.name}}, utm_content={{ad.name}} and campaign_id={{campaign.id}}. They're case-sensitive.

Do embedded GoHighLevel forms capture UTMs?

Yes, when you paste the full embed code. The form_embed.js script passes the parent page's UTMs into the form. An iframe pasted on its own loses them. Test with ?utm_source=test on the page.

How do I stop Meta Pixel and Conversions API double counting in GoHighLevel?

Set up events in the funnel's Events tab with Conversions API on and don't also paste a pixel script. HighLevel sends a shared event ID so Meta dedupes the browser and server events. Don't send the same event again from a workflow or a page script.

Can GoHighLevel send offline conversions to Google Ads?

Yes. Create an offline conversion action in Google Ads or in Ad Manager > Settings > Google Ads > Conversions, then use the Add to Google Ads workflow action. The contact needs a gclid, gbraid or wbraid from a real ad click.

How do I filter a GoHighLevel dashboard by UTM?

Edit a Contact or Opportunity widget, add Conditions > Attribution > First or Latest Attribution, then add UTM Source, UTM Campaign or other UTM fields with +AND. Other widget types don't support attribution filters.

Sources / last checked Nov 18, 2026

  • HighLevel help docs: attribution and reporting. Understanding Attribution Source (modified Aug 26, 2026), How to add attribution and UTM parameters as filters on custom widgets (Sep 16, 2026), Lead Source Report (Oct 30, 2026), Source Field in Forms and Surveys (Sep 8, 2026), How to set up Facebook Ad Reporting (Nov 18, 2026), How to set up Google Ad Reporting (Sep 30, 2022), Google Ad Precautionary Tracking Script (Sep 14, 2022), Sites Traffic Source Analytics (Oct 23, 2025), Chat Widget Attribution (Feb 17, 2021) and How to Set Up Call Tracking (Number Pool) (Nov 12, 2026), read Nov 18, 2026.
  • HighLevel help docs: forms and tracking code. Embedding HighLevel Forms on Non-HighLevel Websites (Sep 8, 2026), Tracking External Forms (Aug 26, 2026), Field Mapping and iFrame Form Tracking in External Tracking (Oct 27, 2026, Labs), Populate Custom Fields using Custom HTML/JavaScript (Aug 7, 2024), URL Parameters in Funnels and Websites (Sep 11, 2026) and Add Tracking Code to Funnels and Websites (Oct 9, 2026), read Nov 18, 2026. HighLevel's live form_embed.js, read Nov 18, 2026.
  • HighLevel help docs: Meta. Facebook Conversions API Trigger in Workflows (modified Nov 17, 2026), How to set up a Funnel Event Pixel for Facebook Conversion API (Jun 30, 2026) and How InitiateCheckout and AddPaymentInfo Work in Meta Pixel Tracking (Oct 30, 2026), read Nov 18, 2026. The older Facebook Conversion API Workflow Trigger Not Working article now returns a 404.
  • HighLevel help docs: Google. Workflow Action - Add To Google Ads (Feb 6, 2026), Ad Manager - Create & Manage Google Ads Offline Conversions (Oct 9, 2026), How To Set Up Google Ads Offline Conversion Actions (Mar 24, 2026), Google Analytics 4 Tracking (Mar 4, 2026), Workflow Action - Add To Google Analytics (Feb 24, 2025) and Google Analytics (GA4) Debug Checklist (Mar 6, 2026), read Nov 18, 2026.
  • HighLevel changelog. Facebook tracking events with Pixel and CAPI (May 28, 2024), Meta Pixel tracking update for funnels and websites (Mar 19, 2026), Meta Pixel legacy event suppression (Jun 11, 2026), Meta Pixel InitiateCheckout change (Oct 12, 2026), dataset support for Meta conversions (Jun 12, 2025), Google Ads conversion action flow in Ad Manager (Jun 4, 2025), currency and conversion value in the Google Ads action (Apr 14, 2025), Google Lead Form attribution fix (May 5, 2026) and Lead Source Report drill-down (Oct 6, 2026) on ideas.gohighlevel.com/changelog, read Nov 18, 2026.
  • My video. My daycare client walkthrough (Dec 2023), where I start with their Google Analytics and check the Facebook ads numbers in HighLevel's reporting tab. Its title has an income figure, so it's quoted, not embedded. I don't have a dedicated tracking video, so there's no video on this page.
Hamza Baig (Hamza Automates)

Author

Hamza Baig / Hamza Automates

Founder, Hexona Systems

I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.

Platinum SaaSpreneur
2024
Diamond SaaSpreneur
2025, 2026
LevelUp speaker
2026
YouTube subscribers, Oct 2026
34,200

Keep reading

Start your 30-day free trial →

30 days free + 1:1 setup call + my bonus / affiliate link