Skip to content

Track Facebook Ads in GoHighLevel: Setup Checklist and Reporting Guide

You can connect Facebook advertising activity to GoHighLevel contacts by capturing campaign identifiers on arrival and carrying them through the lead form. The workflow below explains the fields, the UTM pattern, and three reports that turn the stored values into decisions about leads, customers and revenue.

What you are building

The goal is to know, inside GoHighLevel, how many leads and customers originated from Facebook advertising and which campaign produced them. That requires a chain: the ad click carries identifiers, the website preserves them, the form submits them, and the CRM contact stores them. If any link is missing, reporting will be incomplete.

Setup checklist

Work through these checks in order:

  • Install the attribution code in the website header, using the method for your website builder.
  • Add hidden fields to every lead-capture form, including GoHighLevel Forms and any external form builder in use.
  • Tag every Facebook destination URL with UTM parameters before launch.
  • Test a click-to-form journey and confirm the contact in GoHighLevel contains the expected channel values.
  • Build the three reports below before changing budgets, so you have a baseline.

Hidden-field map

Add these five hidden fields to each form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Think of Channel as the broad category and each drilldown as a finer level of detail. The same field set should be used consistently so contacts can be grouped and compared later.

UTM pattern for Facebook Ads

UTM parameters are extra text appended to a destination URL so analytics tools can identify where a visitor came from. A practical Facebook pattern is: UTM Medium = Paid social, UTM Source = Facebook, UTM Campaign = campaign name, UTM Term = ad set name, and UTM Content = specific ad. For example, a destination ending in /integrations/gohighlevel could carry utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. Use one naming convention across campaigns; free UTM builder tools can help assemble the URLs.

How the data reaches the contact

When a visitor arrives from a Facebook ad, the attribution tool reads the UTM parameters and stores them in a browser cookie. If the visitor leaves and returns later, the values are still available. On form submission, the tool writes the stored values into the hidden fields, and the form builder passes them onward. With GoHighLevel's built-in form builder, the values are added to the new contact automatically; with another form tool, send them into GoHighLevel alongside name and email.

Example of captured values

In a worked example, a click on a brand campaign ad could produce Channel = Paid Social, Channel Drilldown 1 = Facebook, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = North America Ad Group and Channel Drilldown 4 = Green Ad, depending on the UTM values used. The tool can also capture the landing page URL and landing page group, such as /features, which shows which site content helped generate the lead.

Reporting in GoHighLevel

Once contacts carry these fields, reporting can use GoHighLevel's native tools or a connected reporting tool such as Microsoft Power BI or Google Data Studio for more advanced views. The stored fields are what make campaign-level reporting possible; without them, GoHighLevel only knows that a contact exists, not where it came from.

Report 1: Leads by channel

This view groups leads by Channel across all sources, not only Facebook. It helps you compare Facebook against paid search, organic search and organic social, and decide where effort should shift to obtain leads at a lower cost.

Report 2: Customers by network

Facebook ads may also appear on Instagram, WhatsApp and Messenger. Those environments behave differently, so customers by network shows which placement is producing customers and where to focus spend.

Report 3: Revenue by campaign

This report breaks monthly revenue down by originating campaign. In the illustrative example, the Brand Campaign generated $52,000 in new revenue in September; if spend for that campaign was lower than that figure, the return is positive and continued investment is supported. Always compare the revenue figure with the actual campaign spend for the same period.

Why this approach is useful

Beyond Facebook, the same setup captures paid search, organic search and organic social, so one field set covers the full lead mix. It also normalises inconsistent UTM values, for example utm_source=facebook versus utm_source=facebook.com, into the same Paid Social channel, and it retains values across return visits. Before starting, confirm the current offer and setup effort: {{OWNER_TRIAL_TERMS}}. The recommended tool is Attribution Analytics.

Frequently asked questions

What is the shortest setup sequence?

Add the attribution code to your website header, add five hidden fields to each lead-capture form, tag Facebook destinations with UTM parameters, then let the form submission carry the captured values into GoHighLevel with the contact details.

How should the hidden fields be used?

Use Channel for the broad channel, then Channel Drilldown 1 to 4 for progressively more specific source, campaign, ad-set and ad detail. Keep the same UTM naming pattern across campaigns so reports stay comparable.

Why store the data in a cookie?

Because the values are stored in a browser cookie when the visitor arrives, they can survive a later return visit before the form is completed, rather than depending only on the current page view.

Which reports are most useful first?

Leads by channel gives a broad mix view, customers by network separates Facebook-owned placements such as Instagram, WhatsApp and Messenger, and revenue by campaign connects monthly revenue to the originating campaign for a return check against spend.