GoHighLevel Google Analytics and Looker Studio: Tracking Leads to Revenue

Why can't most GoHighLevel accounts connect leads to revenue?

GoHighLevel collects a lot of data: form submissions, calls, appointments, pipeline stages, and invoices. The problem is that the data lives in different places and is tagged inconsistently. One campaign is tagged Facebook, another fb, another is not tagged at all. Forms fire no analytics event. Pipeline stages mean different things to different people.

The result is a familiar conversation: the owner knows leads are coming in but cannot say which channel is worth another dollar. Fixing that is not about a fancier dashboard. It is about four foundations: GA4 installed correctly, conversion events for every lead action, a UTM standard everyone follows, and a reliable way to get GHL pipeline data next to your marketing data.

This is the work George Chapin has done for 20+ years in CRM and analytics, including building an omnichannel UTM and attribution framework and executive dashboards in GA4, Looker Studio, Power BI, and Sigma. The steps below are the same ones we use on client builds.

How do you add Google Analytics 4 to GoHighLevel funnels and websites?

There are two common approaches for pages built in GoHighLevel, plus a couple of details that trip people up:

• Direct: paste your GA4 Google tag (gtag.js) into the head tracking code in your funnel or website settings. Quick, but every event beyond page views needs custom code.
• Google Tag Manager (recommended): paste the GTM head and body snippets into the funnel or website tracking code fields, then manage GA4 and ad platform tags in GTM. Easier to maintain across many funnels and pages.
• Chat widget: HighLevel documents how to use GA4 to track website and chat widget activity, which is worth enabling if chat is a lead source.
• Cross-domain: if your main site and your GHL funnels live on different domains, configure cross-domain measurement, or a visitor who clicks from one to the other will look like a new session with a lost source.

Which GA4 conversion events should you track for forms, calls, and bookings?

Track every action that creates a lead, using GA4's recommended lead events where they fit. Google's lead generation events include generate_lead (a form or offline submission), qualify_lead, working_lead, close_convert_lead (the lead became a customer), and close_unconvert_lead. Using those names populates GA4's lead acquisition reporting.

On the page side, fire generate_lead when a GHL form or survey is submitted, when a calendar booking is confirmed, and when someone taps a click-to-call link. Mark them as key events in GA4 so they count as conversions.

The part most setups miss is what happens after the page. GoHighLevel workflows include a Google Analytics 4 action that sends a custom event using your GA4 Measurement ID and a Measurement Protocol API secret, with an optional numeric event value. That lets you send pipeline milestones such as appointment showed, estimate sent, or job won, with revenue as the value, triggered from the CRM itself. HighLevel notes that these events can take 24 to 48 hours to appear in GA4, so do not panic on day one.

What UTM standards should a GoHighLevel account use?

UTM tags are how GA4 and GHL know where a lead came from. Without a written standard, every person who builds a campaign invents their own, and your reports split one channel into five. When George built an omnichannel UTM framework, the point was simple: one naming convention for every channel, enforced everywhere.

• Lowercase everything. GA4 treats Facebook and facebook as different sources.
• utm_source is the platform (google, facebook, gbp, nextdoor, email). utm_medium is the channel type (cpc, paid_social, organic_social, email, sms, referral). utm_campaign is the offer or season (spring_ac_tuneup_2026).
• Tag Google Business Profile links (website and booking buttons) so map-pack leads do not show up as direct traffic.
• Tag SMS and email links sent from GHL, or your own follow-up campaigns will inflate direct traffic.
• Capture first-touch UTMs onto the contact record in GHL (its attribution fields or hidden form fields) so revenue can be tied back to source later.
• Keep the standard in a shared sheet with a link builder, and audit it monthly.

How do you get GoHighLevel data into Looker Studio?

Looker Studio connects to GA4 natively, so everything you send to GA4 (page events plus GHL workflow events) is available right away. GoHighLevel also offers Google Analytics widgets inside its own dashboards and custom reports if you want some web data in the CRM view.

For CRM data itself (contacts, opportunities, pipeline value, appointments), we have not found a native GoHighLevel connector for Looker Studio, and there is an open request for better export and API reporting on HighLevel's ideas board. Your options are:

• Google Sheets as a bridge: scheduled exports or a workflow that writes rows to a sheet, then connect the sheet to Looker Studio. Cheap and transparent, but fragile at volume.
• Windsor.ai: offers a no-code GoHighLevel to Looker Studio connector covering data such as pipelines, conversations, orders, and transactions.
• Coupler.io: offers a GoHighLevel connector with scheduled refreshes (as often as every 15 minutes, per its site) to Looker Studio, Sheets, and other destinations, plus a GoHighLevel dashboard template.
• API to a database: for larger accounts, pull GHL data through the API into a warehouse such as BigQuery and report from there. More setup, most control.

Which dashboard metrics actually matter?

A good GoHighLevel dashboard answers one question: which marketing produces revenue, and where are leads leaking? These are the metrics we build first:

• Leads by source: new contacts by utm_source and medium, including calls and Google Business Profile.
• Speed-to-lead: time from lead creation to first human response by call or text. Slow response is where local businesses lose jobs they already paid to generate.
• Booking rate: share of leads that book an appointment or estimate, by source.
• Missed-call rate: inbound calls not answered, and how many were recovered by text-back.
• Pipeline value: open opportunity value by stage and by source.
• Revenue by source: won value tied back to first-touch source, so you can compare cost per lead with revenue per lead.

What does a working reporting setup look like week to week?

Keep it to one page an owner will actually open. The top row shows leads, bookings, and revenue for the week against the prior period. The middle shows those numbers by source. The bottom shows the leaks: slow responses, missed calls, and leads stuck in a stage.

Then use it. A 15-minute weekly review of that page, with one decision at the end (shift budget, fix a follow-up, call back stale leads), is worth more than a 20-tab report nobody reads.

What are the most common GoHighLevel tracking mistakes?

• GA4 installed on the main website but not on GHL funnels, or installed twice and counting every page view double.
• Form submissions tracked as views of a thank-you page that people can reach without submitting.
• No UTM tags on Google Business Profile, SMS, or email links, so big channels look like direct traffic.
• Pipeline stages that are not kept current, which makes revenue by source meaningless.
• Pasting the GA4 API secret with a stray space, which HighLevel specifically warns will break the workflow action.