Skip to content

Track Affiliate Leads and Customers in GoHighLevel

A partner's link can send plenty of visitors and still leave you unable to say which of them became a contact, a customer, or revenue. The missing piece is rarely the click — it is the handoff between the click and the CRM record. This guide covers a four-step setup: tag partner links with UTM parameters, create matching hidden fields on your forms, let the tagged values populate those fields, and confirm the submission reaches GoHighLevel. It closes with a field map, a launch checklist and three report shapes you can build from the resulting contact data.

The gap between a click and a contact record

Session-based analytics answers a traffic question: how many visits did this link produce? It does not answer the commercial question, because the commercial answer is attached to a person, not a session. Which contact came from which partner, whether that contact bought, and what they were worth — those facts belong on the CRM record.

So the design goal is narrow and practical: make sure the affiliate source is written onto the contact at the moment of form submission. Everything below serves that one requirement. A useful side effect is that the same mechanism records your other acquisition sources too, which means affiliate performance can be read next to organic and paid results instead of on its own.

One constraint to accept up front: the values you store are only as good as the values you publish. Whatever you encode in the UTM parameters is what arrives in GoHighLevel, so settle the naming scheme before any link goes out.

Step 1 — Tag every partner link with a fixed UTM scheme

A tagged affiliate link is an ordinary destination URL with a query string appended. The pattern is a page path followed by utm_medium, utm_source and utm_campaign values, for example a path with utm_medium=affiliates, utm_source=bloggers and utm_campaign=john-smith.

A three-part convention keeps reporting flexible:

  • utm_medium — the program itself, set to Affiliates on every partner link.
  • utm_source — the partner category, such as Bloggers, Podcasters or YouTubers.
  • utm_campaign — the individual partner, such as John-Smith.

Separating category from individual is the decision that pays off later: one data set then supports both a partner-type comparison and a single-partner view. If hand-building query strings is error-prone, affiliate platforms can append the parameters automatically, and a UTM builder with affiliate templates can generate and share the tagged links for you.

Step 2 — Create the hidden fields on your forms

The forms that carry commercial intent — contact, quote request, demo request — each need a set of hidden fields to receive the tagged values. Create six: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group.

Hidden fields are widely supported, including in common builders such as Gravity Forms and Typeform, and step-by-step instructions exist for a large range of builders if yours is not obvious. The detail that matters most is the name: it must match exactly, because a near-miss name is the usual reason a value arrives blank.

Step 3 — Let the stored parameters fill those fields

When a visitor arrives through a tagged partner link, the parameters are kept in their browser. That persistence is what makes the method survive real browsing behaviour: the visitor can read several pages, leave, come back by another route, and the original affiliate parameters are still there when they finally submit.

At submission the affiliate information is written into the hidden fields without the visitor doing anything. Nothing depends on them recalling which link they clicked, and nothing depends on the session still being open.

Step 4 — Confirm the submission reaches GoHighLevel

Two delivery paths exist, and they need different amounts of work:

  • Native GoHighLevel forms. When the form itself lives in GoHighLevel, the captured values appear on the contact record with no additional step.
  • Third-party form builders. When the form is built elsewhere (Gravity Forms, Typeform and similar), the submission has to be passed across, typically through an automation tool such as Zapier.

Establish which path you are on before testing. A correctly tagged link and a correctly built form will still leave the contact field empty if the handoff step is absent — and that failure looks identical to a naming mistake until you check the order below.

Worked example: one link, three stored values

Take a blogger named John Smith. You hand him a link tagged with utm_medium=affiliates, utm_source=bloggers and utm_campaign=john-smith. A reader clicks it, browses two other pages, closes the tab, and returns three days later by typing your domain directly. When they submit a quote form, the original parameters are still in the browser, so the contact record arrives with Channel set to Affiliates, Channel Drilldown 1 set to Bloggers and Channel Drilldown 2 set to John Smith.

The same mechanism covers non-affiliate traffic. A visitor from an organic Google search would arrive with Channel set to Organic Search, Channel Drilldown 1 set to Google, Channel Drilldown 2 set to the Google domain they searched on, and — where it is available — Channel Drilldown 3 set to the keyword they used. Because both land in the same Channel field, a single report can compare them.

If the Channel field comes back empty, check in this order: first the link (was it tagged at all?), then the field name (exact match, no stray spaces?), then the handoff (does the third-party form actually pass submissions into GoHighLevel?). Most empty values are resolved at one of those three points.

Three report shapes to build from the contact data

Once source values sit on the contact record, three report shapes cover most program decisions.

Leads by Channel counts leads per channel, affiliates included. Its value is context: it shows what the partner program contributes relative to every other acquisition route, rather than in isolation.

Customers by Affiliate Type groups new customers by the kind of partner who referred them — bloggers, YouTubers, podcasters, social media influencers. This is the input for recruitment: it tells you which partner categories convert, not merely which ones send traffic.

Revenue by Affiliate ranks partners by the value they bring, which is the fairest basis for deciding where to invest effort. A practical follow-on is to ask your strongest partners how they present you, then share those findings with partners who are underperforming.

Pre-launch checklist

Work through this before you announce the program:

  1. Naming scheme agreed — medium, source and campaign values documented, with a fixed spelling and capitalisation for each.
  2. Every affiliate link tagged — no untagged link handed out, including in email signatures and social bios.
  3. All six hidden fields created — Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, Landing Page Group.
  4. Field names verified against the form builder — exact match, no trailing spaces.
  5. Delivery path confirmed — native GoHighLevel form, or third-party form plus automation step.
  6. One test submission per path — check the contact record shows the expected values, not blanks.
  7. Reports built — leads by channel, customers by affiliate type, revenue by affiliate.
  8. Return-visit behaviour checked — confirm a later direct visit still carries the original affiliate source.

Where this approach stops

This is a form-submission method. It attributes contacts who convert through a form on your site, and it depends on the visitor's browser retaining the stored parameters between their first visit and their submission. It does not replace a commission-tracking platform, and it does not by itself reconcile payouts. Treat it as the source-of-truth layer inside your CRM that tells you where contacts came from, and keep payout logic in whatever system you already use for that.

UTM value to GoHighLevel field mapping
UTM parameterExample valueGoHighLevel fieldNotes
utm_mediumaffiliatesChannelSet to Affiliates for every partner link
utm_sourcebloggersChannel Drilldown 1The partner category, e.g. Bloggers, Podcasters, YouTubers
utm_campaignjohn-smithChannel Drilldown 2The individual partner name
——Channel Drilldown 3Used for keyword where available, e.g. on organic search
Landing page URL—Landing PageCaptured from the page the visitor first landed on
Landing page group—Landing Page GroupGrouping of landing pages

Mapping reflects the example convention described in the guide; the exact values stored depend on the UTM parameters you choose to publish.

Delivery path comparison
Form locationExtra step requiredWhere data appears
Native GoHighLevel formNoneContact record in your GoHighLevel account
Third-party builder (Gravity Forms, Typeform, etc.)Send the data across, e.g. via ZapierContact record, once the automation runs

Based on the two paths described; confirm behaviour in your own account before relying on it.

Frequently asked questions

Do I need a separate tracking tool for affiliate leads if I already use GoHighLevel?

Not necessarily. If the tagged values reach the contact record, GoHighLevel holds the source data you need for reporting. The gap this method fills is the link between a tagged visit and a submitted form, which is what the hidden fields and the parameter capture provide.

What happens if a visitor clicks an affiliate link, leaves, and comes back later?

The parameters from the original visit are stored in the browser, so they remain available when the visitor eventually submits a form. The affiliate source is preserved rather than being replaced by the later direct visit.

Why would a contact record show an empty Channel field?

The usual causes are an untagged link, a hidden field whose name does not match exactly, or a third-party form whose submissions are not being passed into GoHighLevel. Check the link first, then the field names, then the handoff step.

Can I compare affiliates against non-affiliate channels?

Yes. The same capture covers all lead sources, so organic search, paid traffic and affiliate referrals all land in the same Channel field and can be compared in one report.

Should the partner category and the partner name go in the same parameter?

Keep them separate. Putting the category in utm_source and the individual in utm_campaign is what allows you to report by partner type and by individual partner from the same data set.