GoHighLevel install

Video guidesLink copied

Install GoHighLevel trackingLink copied

Payment plan and subscription automationLink copied

Custom events for forms and calendarsLink copied

Copy the tracking snippet from your dashboardLink copied

In your TrueMetriks dashboard, go to Settings > Tracking, pick the GoHighLevel tab, and click Copy on the Tracking snippet.

<script async src="https://q.yourdomain.com/t/s-ghl/abcd1234.js"></script>

Checkout URL pattern. This is the word the tracker looks for in your URL to identify a checkout page. The default is checkout. If your funnels use a different word in their checkout URLs, change it in this field and click Save.

The card also has three expandable options - one for payment plans and subscriptions, one for firing custom events for your forms and calendars, and one for Typeform or Calendly. The first two are covered below.

Open the funnel in GoHighLevelLink copied

In the GoHighLevel left sidebar, click Sites.

At the top of the Sites page, click the Funnels tab.

Click the funnel you want to track. You will repeat this for every funnel in your account - the snippet is the same.

Paste the snippet into Head tracking codeLink copied

Inside the funnel, click the Settings tab. Scroll down to Tracking & scripts and paste the snippet you copied into the Head tracking code field. Then click Save.

Repeat for each funnel.

Turn OFF Optimize JavaScriptLink copied

Stay in the funnel's Settings tab and scroll down to Performance & compliance. Make sure Optimize JavaScript is switched off.

This one setting breaks tracking, and it is switched on per funnel, so a funnel that worked yesterday can stop working the moment somebody turns it on.

What it does to you. GoHighLevel's own description is "custom javascript and html codes added will be lazy loaded". Your tracking snippet is custom JavaScript, so it gets lazy loaded with everything else, and instead of running as the page opens it runs many seconds later. On a real customer funnel we measured the snippet loading 10,628ms after the page opened. With the setting off, the same funnel loaded it in 401ms.

What breaks in those ten seconds. The visitor is on your page and TrueMetriks is not running yet, so:

• Plenty of people land, read, and click through before the tracker ever starts, and those visits are never recorded at all.
• A visitor who moves on quickly can be counted as two separate people, because the click that identified them arrived before the tracker was ready. Their landing page and their thank-you page end up in two different sessions.
• The ad click id can be missed, so the sale is not credited to the ad that produced it, and the conversion sent back to Facebook, Google Ads or TikTok carries no click id.

None of this looks like a broken install. The snippet is in the right place and the funnel works fine, you just get thin, split, badly attributed data.

Leave it off and keep it off. Check it on every funnel you track, and check it again if your numbers suddenly drop or your sessions start splitting in two. Image Optimization and GDPR compliant fonts in the same panel do not affect tracking, so set those however you like.

Payment plans and subscriptions (webhook)Link copied

If you sell payment plans or subscriptions, add one GoHighLevel automation that POSTs to the TrueMetriks webhook URL each time a payment lands.

Grab the webhook URLLink copied

Back in your TrueMetriks dashboard, on the same GoHighLevel install card, expand Click here if you have payment plans or subscriptions and click Copy on the webhook URL.

https://q.yourdomain.com/api/webhooks/ghl/abcd1234efgh5678ijkl90mn

Open Automation in GoHighLevelLink copied

In the GoHighLevel left sidebar, click Automation.

Create a workflow from scratchLink copied

Top right, click + Create Workflow, then + Start from Scratch in the dropdown.

Add the Payment Received triggerLink copied

In the new workflow, add a trigger and pick Payment Received from the list. Leave the trigger name as Payment Received (or change it if you want), then click Save Trigger.

Add the Webhook actionLink copied

Below the trigger, add an action and pick Webhook (the normal one - not Custom Webhook). Configure it like this:

• Method: POST
• URL: paste the webhook URL you copied from your dashboard

Then fill in CUSTOM DATA with the keys in the table below and click Save Action. Leave Headers empty.

Fill in Custom Data on every workflow, including one built on GoHighLevel's own Payment Received trigger, and always map product to the merge field that holds the product name. Payment Received does send the amount, currency and transaction id on its own, but it identifies the product by an internal id rather than by its name, so without that one mapping your reports show a long code instead of what was sold.

Fill in Custom Data with these exact keysLink copied

The key names on the left are not free-form: TrueMetriks reads the sale from these keys, so they must be spelled exactly as shown. This matters most on a workflow that carries no standard payment data at all, such as one started by an Inbound webhook trigger (your payment processor, a Zap, or your own backend posts into GoHighLevel) where you build the sale yourself from custom values, but the same keys apply on every workflow.

The left column is the key (fixed, copy it exactly). The right column is whichever merge field in your workflow holds that piece of data.

Two rules that stop wrong revenueLink copied

1. amount must never arrive empty. If the merge field you mapped to amount has no value for that payment, TrueMetriks falls back to the next money-like field in the payload and can record that number as your sale.

2. Send only one money field. Delete every other key that holds a number of money from the Custom Data list, for example revenue, total, cash_collected, payments, or a lifetime-value field. A running total is not the sale. This is the single most common cause of a purchase showing a much larger figure than the payment that was actually taken: a workflow mapped amount to a field that came through empty, and a revenue key next to it carried the customer's total cash collected to date, so that total was recorded as the sale.

Keep the list to the keys in the table above and the amount in your reports will always be the amount that was charged.

Publish the workflowLink copied

Top right, flip the toggle from Draft to Publish, then click Save.

For reference, your published automation should look like this:

Fire custom events for forms and calendarsLink copied

Custom events let you fire an extra, named Facebook event for one specific form or calendar, matched by its name, so you can build an audience or optimize a campaign around that one source. By default your standard Lead and Schedule still fire and record alongside it, and you can optionally switch that off so only your custom event fires for that one matched form or calendar (see Also fire the standard event below). For example: a newsletter_lead event only for your newsletter form, or a strategy_call_booking event only for your strategy-call calendar.

Video guide

Open the custom events option and click CreateLink copied

On the GoHighLevel install card in your dashboard, expand Click here if you want to fire custom events for your GoHighLevel forms and calendars, then click Create.

Fill in the Create custom event popupLink copied

• Standard event. Pick Lead for a form or Schedule for a calendar. This is the most important choice: Lead is for forms, Schedule is for calendars.
• Custom event name. Type any name you want, for example newsletter_lead. This is the name the event shows under in Facebook. Use letters, numbers and underscores.
• Fire when. Leave it on Always, or choose New customers only / Returning customers only to fire just for first-time or repeat contacts. See New vs returning customers for what those mean.
• Source filter. This is where you tell TrueMetriks which form or calendar to match. Type the name of the form (for Lead) or the calendar (for Schedule). The match is case-insensitive and a "contains" match. Leave it blank to fire the custom event on every Lead (or every Schedule) instead of one specific source.
• Also fire the standard event. This checkbox only appears once you have typed a Source filter. Leave it on (the default) to fire and record both the standard event and your custom event, exactly as before. Turn it off to fire and record only your custom event for that matched source: the standard Lead or Schedule will not fire to Facebook and will not show up in your TrueMetriks reports. Use this when one specific form should count as its own conversion instead of a Lead, for example a registration form counted as complete_registration.

Where to find the form or calendar nameLink copied

For a form, open Sites > Forms in GoHighLevel and edit the form. The name shown at the top is the source - copy it into the Source filter.

For a calendar, open Calendars in GoHighLevel, edit the calendar, and look at Calendar name under Basic details. Copy that into the Source filter.

Paste the name into the Source filter exactly as it appears, then click Create.

What you get after clicking CreateLink copied

The event appears under Facebook > Custom events in your dashboard, tagged GoHighLevel with the source it matches. From here you can edit when it fires or remove it.

TrueMetriks also creates a matching Custom Conversion inside Facebook Ads Manager (Events Manager > your pixel > Custom conversions). It starts Inactive and turns Active once the first matching event lands. Give it 30 to 60 seconds before you test.

Test itLink copied

Submit the form (or book the calendar) you filtered on. In Facebook Events Manager > Test events you will see both the standard event and your custom event arrive together - Lead plus your custom name for a form, Schedule plus your custom name for a calendar.

Custom coded forms and calendarsLink copied

If you built your own form or your own booking widget on a GoHighLevel page instead of using GoHighLevel's, TrueMetriks still tracks the visitor but it never learns that they submitted anything, so no Lead or Schedule conversion is recorded. One line of your own JavaScript fixes that.

When you need thisLink copied

Only when the form or the booking widget is custom coded: your own HTML and JavaScript, or a third-party embed that is not a GoHighLevel form and not a GoHighLevel calendar.

A normal GoHighLevel form or calendar needs none of this. Those record their Lead and Schedule automatically, and adding the code below to one of them would count the same conversion twice. Only use it where you built the form or the booking widget yourself.

The symptom, if you are not sure: the person shows up in your dashboard with their email and phone and you can see their session, but no Lead (or no Schedule) ever appears for them.

Add the helper to your pageLink copied

Paste this once into the funnel's Head tracking code, underneath your TrueMetriks snippet. A custom code block on the page works too, as long as it comes after the snippet.

<script>
function tmSendConversion(eventName, contact) {
  if (window.__tmCaptureIdentity) window.__tmCaptureIdentity(contact);
  if (window.tmFireEvent) window.tmFireEvent(eventName, {}, contact);
}
</script>

Optimize JavaScript must be off for any of this to work. With it on your snippet is lazy loaded, so it is not there yet when your form submits and the conversion is lost.

Fire Lead from your custom formLink copied

In your own success handler, after the submission has actually gone through:

// Form submitted successfully
if (!window.__tmLeadSent) {
  window.__tmLeadSent = true;
  tmSendConversion("Lead", {
    email: "[email protected]",
    phone: "+15551234567",
    first_name: "Jane",
    last_name: "Doe"
  });
}

Replace the example values with the ones the person actually typed into your form.

Fire Schedule from your custom calendarLink copied

Exactly the same shape in your confirmed-booking handler, with the event name changed to Schedule:

if (!window.__tmScheduleSent) {
  window.__tmScheduleSent = true;
  tmSendConversion("Schedule", {
    email: "[email protected]",
    phone: "+15551234567",
    first_name: "Jane",
    last_name: "Doe"
  });
}

What to put in the contact detailsLink copied

• email is the one that matters. It is what ties the conversion to the visitor's session and to the ad click that brought them in. Send the real address they typed. A merge tag that has not been filled in, such as {{contact.email}} arriving as literal text, is ignored.
• phone should carry the country code, for example +15551234567.
• first_name and last_name are optional and can be left out.
• Every field is optional in the sense that an event with no email still records, but it cannot be matched back to the person nearly as reliably, so send the email whenever you have it.
• Lead and Schedule are the only two names to use here. They are the same conversions the dashboard and Facebook already understand, so they show up in your reports and fire to every connected ad platform exactly like a native GoHighLevel form would.

Two rules that stop double countingLink copied

1. Fire it once, and only when the submission actually succeeded. Put the call in your success path, after your own save or booking request comes back OK, never on the button click. A hand-fired conversion has no safety net here: two calls are two conversions in your reports and two conversions sent to your ad platforms. The if (!window.__tmLeadSent) guard in the examples is what stops an impatient double click sending it twice, so keep it in.

2. Do not also send the same form through a receiving webhook. If you have a GoHighLevel workflow POSTing this same submission to a TrueMetriks webhook URL, pick one or the other. Doing both records the conversion twice.

How to testLink copied

After installing the snippet (and the webhook, if you set one up), the next step is verifying everything is firing correctly. See Test your integration for the full walkthrough.

Something not firing? See Troubleshooting.