Skip to content

How to Capture UTM Parameters in GoHighLevel

Knowing which campaigns create leads is different from knowing which campaigns create customers. Capturing campaign and landing-page information with every GoHighLevel form submission lets you connect traffic sources to opportunities, closed deals and revenue inside the CRM, instead of relying only on visit counts in analytics.

How the capture works

A small website snippet records where a visitor came from when they first arrive, using the same kinds of technical signals analytics tools examine. It groups that origin into a main channel and progressively more specific drill-downs, then keeps the result in the browser.

When the visitor later submits a GoHighLevel form, the stored values are written into hidden fields on that form and saved with the contact. The same submission can also carry click identifiers and landing-page information, giving a fuller record than UTM values alone.

Setup checklist

Install the snippet on the website first. Depending on the builder, this is usually done through site settings or a tag manager, with WordPress, Webflow and Squarespace given as examples of builders where the method differs in detail.

Next, prepare the form so there is somewhere for the data to land. Add six text fields, open each field's settings and switch the Hidden option on. Visitors do not see these fields, but the snippet can still populate them at submission.

Use this field map as a checklist:

  • Channel — the main source category, for example Paid Search
  • Channel Drilldown 1 — the first level of detail, for example the search platform
  • Channel Drilldown 2 — the next level, for example the campaign
  • Channel Drilldown 3 — the most specific level, for example the ad or keyword grouping
  • Landing Page — the page where the visitor first arrived
  • Landing Page Group — the category or group that page belongs to

After a test submission, check the contact record in GoHighLevel to confirm all six fields were populated. Also confirm the values appear in notification emails or reports if those outputs are used by the team.

Worked example

Consider a marketer promoting a file-sharing service through search ads. A prospect searches for a relevant phrase, clicks an ad, browses several pages and then requests a demo from a different page.

Because the attribution was stored on arrival, the form submission can still record Paid Search as the channel, the search platform as the first drill-down, the campaign name as the second and the brand term as the third, together with the landing page and its group. Without browser storage, moving from the landing page to the demo page could have disconnected the lead from the ad that produced it.

Why this goes beyond raw UTM values

Raw UTM capture covers only visits that carry UTM tags. Classifying every arrival also covers organic search, organic social, referral and direct traffic, so a channel report does not silently omit untagged leads.

Storing the data in the browser solves the cross-page problem described above. Capturing click IDs adds another layer: GCLID for Google, MSCLKID for Microsoft and FBCLID for Meta can be returned to the ad platform at a later revenue moment for offline conversion tracking. That gives bidding systems customer and revenue signals rather than only form-completion signals.

Landing-page capture answers a separate question — whether blog posts or other content are producing leads and customers, not just visits.

Reports to build once data is in the CRM

Leads by channel: break submissions down across organic search, paid search, paid social, organic social and other channels to see where demand actually originates and compare that picture with where budget is spent.

Leads by Meta network: separate Facebook, Instagram and Messenger results so budget can shift toward the networks producing leads.

Customers by Google Ads campaign: join the stored campaign data to closed deals to identify campaigns producing customers rather than only traffic.

Revenue by keyword: when keywords are included in Google Ads UTM values, report revenue and customer outcomes by keyword to inform both bidding and search-content priorities.

In each case, the value comes from joining the stored source fields to later CRM stages — opportunity conversion, closed-won status and revenue — rather than stopping at form submissions.

Illustrative use case

An events business running search and social campaigns could previously see traffic by campaign in analytics but could not connect that traffic to bookings. With source data stored on every booking-form submission, the team could compare leads, bookings and revenue by campaign and platform, and could judge each channel on bookings rather than on visits alone. That fuller view also surfaced referral traffic from venue websites as a meaningful source of bookings — a source that would be invisible if only paid UTM-tagged visits were captured. A team evaluating this setup should ask whether its own untagged referral and organic arrivals are currently being counted at all, since those are the leads most likely to be missing from a paid-only picture.

Getting started

Start by installing the snippet, adding the six hidden fields, and running a test submission from a tagged link. Verify the contact record, then build one channel report and one campaign-to-customer report before expanding to keyword and landing-page reporting.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Hidden field map for GoHighLevel forms
Hidden fieldWhat it recordsUse in reporting
ChannelMain source categoryLeads and customers by channel
Channel Drilldown 1First level of source detailPlatform-level breakdown
Channel Drilldown 2Second level of source detailCampaign-level breakdown
Channel Drilldown 3Third level of source detailAd or keyword-group breakdown
Landing PageFirst page visitedContent and page performance
Landing Page GroupCategory of first pageGrouped content performance

Field names are the six hidden fields required for this workflow.

Frequently asked questions

Why not just pass raw UTM values into GoHighLevel?

Raw UTM capture only records tagged paid visits. A channel attribution approach also classifies untagged arrivals such as organic search, organic social, referral and direct visits, so reporting is not limited to paid campaigns.

What happens if a visitor lands on one page and submits a form on another?

If attribution is stored in the browser on arrival, the values remain available when the form is completed on a later page. If capture depends only on the landing URL, moving to a separate form page can lose the original campaign information.

What extra value do click IDs provide?

Click identifiers such as GCLID, MSCLKID and FBCLID can be stored with the lead and later sent back to the relevant ad platform when a customer or revenue event occurs, enabling offline conversion tracking rather than optimising only for form submissions.