Skip to content

How to track Google Ads campaigns in GoHighLevel

Google Ads can tell you how many clicks and conversions it recorded. It cannot tell you, on its own, which campaign produced a named lead inside your CRM, or which keyword eventually turned into revenue. This guide shows a four-step setup that carries Google Ads campaign information into GoHighLevel with each form submission, so lead and customer reporting can be broken down by channel, campaign, ad group and keyword.

What the setup achieves

The goal is simple: every time someone submits a lead form on your site, the record that lands in GoHighLevel should already say where that person came from. Campaign-level detail arrives through UTM parameters on your ad URLs; a small script reads those parameters and writes them into hidden form fields; the CRM then stores them next to the lead's name, email and phone.

Once that chain is working, you can answer questions that ad-platform dashboards handle poorly: which campaigns produce customers rather than clicks, how paid search compares with other channels, and which keywords are attached to actual revenue.

Step 1: Tag your Google Ads URLs with UTM parameters

UTM parameters are extra text appended to the destination URL of an ad. They travel with the visitor and let downstream tools identify the campaign that sent them.

A tagged URL keeps the original page path and adds key-value pairs, for example a page path followed by utm_medium=paidsearch, utm_source=google and utm_campaign=brand-campaign. The values are yours to choose, but a consistent convention is what makes reporting possible later. A practical default:

  • UTM Medium: paid search
  • UTM Source: Google
  • UTM Campaign: the Google Ads campaign name
  • UTM Term: the ad group name
  • UTM Content: the specific ad

Free UTM builders exist online if you would rather not assemble the strings by hand. Whatever convention you pick, apply it to every ad and keep it stable over time.

Step 2: Add hidden fields to your lead forms

Hidden fields are form inputs that visitors never see but that still submit values. Add them to every lead capture form so the campaign data has somewhere to land.

The fields to create are: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Most form builders let you drag a hidden field type into the form; documentation for individual builders covers the exact clicks.

Step 3: Let the script populate the fields

With the tags and fields in place, a tracking script on your site identifies how each visitor arrived, using the same kinds of signals analytics platforms examine, and sorts them into channels such as paid search, paid social and organic search. When the visitor submits a form, the script writes the matching values into the hidden fields.

A worked example makes the mapping concrete. Suppose a Sydney law firm runs a brand campaign in paid search. A visitor from that campaign could arrive with these values written into the form:

  • Channel = Paid Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Brand Campaign (the campaign name)
  • Channel Drilldown 3 = Sydney lawyers (the searched keyword)

Separately, the script records the first landing page, such as a services page for contract law, and the landing page group, such as services.

Step 4: Confirm the data reaches GoHighLevel

On submission, the campaign values travel into GoHighLevel together with the details the lead typed in, such as name, email and phone. Inside the CRM, those stored values become the basis for reporting on lead volume and customer generation by campaign.

Before trusting any report, verify one real submission end to end: submit a test form from a tagged ad URL and confirm that Channel, the drilldowns and the landing page fields all arrive populated.

Field and control map

Use this map to check your configuration. Each UTM parameter has a natural home in the hidden field set, and the landing page values are captured independently of the tags.

  • utm_medium feeds Channel (for example, Paid Search)
  • utm_source feeds Channel Drilldown 1 (for example, Google)
  • utm_campaign feeds Channel Drilldown 2 (the campaign name)
  • utm_term feeds Channel Drilldown 3 (the ad group or keyword)
  • utm_content identifies the specific ad
  • Landing Page and Landing Page Group are recorded from the visitor's first page view

If a report column is empty, work backwards along this map: the tag may be missing from the ad, the hidden field may be missing from the form, or the form may not be passing values into the CRM.

What the tracking script does

The tracking script is a small piece of code placed on the website. It inspects how each visitor arrived, categorises them into a channel, and then passes that channel information into GoHighLevel alongside whatever the lead entered in the form. In the CRM record you can see the channel, the campaign name, the ad group name and the landing page details side by side. This guide describes the workflow as documented for the marketing attribution software tracking script, a third-party tool. If you use a different attribution tool, confirm that it writes the same six hidden fields before following the reporting steps below.

Three reports worth building

The value of the setup shows up in reporting. Three report types cover most of the questions a marketing team asks.

Leads by channel. Because every lead carries a recorded source, not just the paid search ones, you can chart monthly lead volume per channel. The comparison is relative: how much of your lead flow arrives via Google Ads versus paid social, organic search or other channels, and whether that mix shifts month to month. Treat the comparison as an input to budget conversations, not as a verdict on its own.

Customers by campaign. This view counts, per month, how many customers each Google Ads campaign produced. Read it as a trend line: when you change bids, creative or targeting, the customer count for that campaign should move in a direction you can explain. A campaign that wins clicks but never appears in this report is a candidate for review.

Revenue by keyword. This view totals monthly revenue against the keywords you bid on, which shows where revenue concentrates. Pair it with the spend behind each keyword to judge return: if a keyword produced $15k in sales and the ad spend behind it was lower than that, the return is positive. The report shows attribution, not incrementality, so it cannot tell you what would have happened without the ad.

Pre-launch checklist

Work through these checks before relying on the numbers:

  1. Every active ad carries the same UTM convention.
  2. All six hidden fields exist on every lead form, not just the main one.
  3. A test submission from a tagged URL shows populated Channel and drilldown values in the CRM.
  4. Landing Page and Landing Page Group populate even when no UTM tags are present.
  5. Report definitions match the field names you actually used, so campaign names line up across months.
  6. Someone owns the job of re-checking the setup after form or ad changes.

Where to go next

Tagging ad URLs, adding hidden fields and letting the script fill them gives GoHighLevel a campaign record for every lead. From there, lead, customer and revenue reporting by channel, campaign and keyword becomes a matter of building the views you need. If you plan to use the marketing attribution software script for this workflow, check its current trial and setup terms on the provider's own site before you begin; this guide does not restate them.

UTM parameter to hidden field mapping
Source valueHidden fieldExample value
utm_mediumChannelPaid Search
utm_sourceChannel Drilldown 1Google
utm_campaignChannel Drilldown 2Brand Campaign
utm_termChannel Drilldown 3Sydney lawyers
utm_content(identifies the specific ad)—
First page viewLanding Pagesydneylaw.com/services/contract-law
First page viewLanding Page Groupservices

Example values follow the convention described in the guide; the utm_content parameter identifies the ad but is not shown mapped to a specific hidden field.

Frequently asked questions

Do I need UTM parameters if Google Ads already reports conversions?

Ad-platform conversion data and CRM data answer different questions. UTM parameters carry the campaign, ad group and ad identity into the form submission, so the lead record in GoHighLevel can be tied to a specific campaign and keyword rather than only to a platform-level conversion count.

Which hidden fields must exist on the form?

Six: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. If any is missing, the corresponding value has nowhere to be stored.

What does each drilldown level represent?

Following the recommended convention, the first drilldown holds the source (Google), the second holds the campaign name, and the third holds the ad group or keyword. The values come from whatever you placed in the UTM parameters, so consistency matters more than the exact labels.

Can I report on channels other than Google Ads?

Yes. The script categorises all visitors into channels, so lead reports can compare paid search with paid social, organic search and other sources in the same view.

How do I tell whether the setup is broken?

Submit a test form from a tagged ad URL and inspect the resulting CRM record. An empty Channel points to a missing or malformed tag; an empty drilldown points to a missing hidden field; a record with no campaign data at all points to the form not passing values through.