GoHighLevel Trigger Links: Setup & Tracking (2026)
GoHighLevel Trigger Links: Setup & Tracking (2026)
By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 13 August 2026 · 8 min read
GoHighLevel trigger links are tracked redirect URLs you create inside a sub-account, drop into an email or SMS, and then use as a workflow trigger the moment a contact clicks. The link sits on a LeadConnector redirect domain, records the click against the contact record, and fires whatever automation you have attached to it. That is the whole mechanism: a redirect that knows who clicked and tells your workflow about it.
Most agencies underuse them, building a full nurture sequence and then having no idea which contacts cared about pricing versus the case study. Below is how I set them up in client sub-accounts, what the tracking captures, where the limits sit for SMS in Australia, and the segmentation recipes that earn their keep.
What trigger links are and where they live
A trigger link is a short URL owned by your sub-account that redirects to a destination you specify. You create it under Marketing > Trigger Links. Each one needs a name (internal only, used when you select it in Workflows), a redirect URL (where the contact actually lands) and optionally a custom slug on your LeadConnector link domain.
Once saved, the link becomes available in two places. First, in the email and SMS builders as a merge-field style insert, so you do not have to paste the raw URL. Second, in Workflows as the Trigger Link Clicked trigger, where you pick the specific link by name.
The difference between a trigger link and a normal link
A pasted raw URL still registers a generic click for email reporting. What it does not give you is a named, reusable event you can attach automation to. A trigger link makes the click an addressable object: this contact clicked this specific named link, at this timestamp. That is what makes branching possible.
Redirect domains
By default your links resolve on a LeadConnector-owned domain. In client sub-accounts I set up a branded link subdomain instead, such as go.clientdomain.com.au. A shared redirect domain used by thousands of sub-accounts accumulates reputation damage from other people's sending; your own subdomain does not, and that shows up directly in SMS delivery rates.
How GoHighLevel trigger links track clicks
When a contact clicks, the request hits the redirect service with a contact identifier appended to the URL. GoHighLevel resolves that identifier to a contact record, writes a click event, then issues the redirect to the destination. The contact experiences a fraction-of-a-second hop. Your system keeps the record.
What is captured
The click event stores the contact, the link name, the timestamp, and where relevant the source message, and it appears in the contact timeline. GoHighLevel does not natively store device, browser or geolocation against the click in a way you can filter on inside the sub-account, so do not promise a client that detail without a third-party analytics layer.
The contact identification requirement
This is the part people get wrong. Attribution only works where GoHighLevel knows who the recipient is: a workflow email, a workflow SMS, a bulk campaign to known contacts, or a conversation message. Paste the same URL into a Facebook post, a public web page or a printed QR code and there is no contact attached. The redirect works and the aggregate count increments, but no workflow fires.
Using Trigger Link Clicked in Workflows
In Workflows, add the trigger, choose Trigger Link Clicked, then select your link from the dropdown. You can add filters as with any trigger, so you can restrict it to contacts holding a particular tag or in a given pipeline stage.
Standard action stack after a click
The pattern I use in nearly every build is the same four actions in order. Add a tag that names the interest, such as interest-pricing. Update a custom field that holds a numeric engagement score, incrementing it. Add an internal notification to the assigned user if the score crosses a threshold. Then branch with an if/else condition to decide whether the contact drops into a sales sequence or continues nurturing. Keep tag naming consistent across every sub-account.
Re-entry settings matter
By default a workflow will not re-enter a contact who has already been through it, which for a trigger link workflow is usually wrong. If someone clicks your pricing link three times in a fortnight, that repeat behaviour is the signal. Turn Allow Re-entry on for scoring workflows and off for one-time actions such as sending a welcome pack.
Wait steps and the click race
A common build error is placing a trigger link in an email, then adding a plain time-delay wait followed by a "did they click" check. Use a separate workflow triggered by the click, or a Wait step configured with a trigger link condition, so the contact releases the moment they click rather than sitting idle.
Trigger links against other segmentation signals
Trigger links are one of several ways to record intent. They are not always the right one. This table is how I decide.
| Signal | What it proves | Effort to set up | Best use |
|---|---|---|---|
| Trigger link click | Contact was interested enough to open a specific asset | Low — one link, one workflow | Interest scoring, topic segmentation, warm list identification |
| Tag added manually | A human decided something about the contact | Very low, but relies on staff discipline | Sales qualification notes, account status |
| Form or survey submission | Contact supplied structured data and consented | Medium — build form, map fields | Lead capture, qualification, booking prerequisites |
| Email opened | Almost nothing since Apple Mail Privacy Protection | None — automatic | Rough deliverability sanity check only |
| Pipeline stage change | A sales process actually advanced | Medium — requires pipeline hygiene | Revenue reporting, forecast, stage-based automation |
The practical hierarchy: form submissions beat clicks, clicks beat opens, and nothing beats a pipeline stage change backed by a real conversation. Use trigger links to decide who deserves the phone call, not to declare someone sales-ready.
Trigger links in emails against SMS
In email
Inside the drag-and-drop builder, select a button or text link and choose the trigger link from the link type dropdown rather than pasting a URL. This keeps the reference dynamic, so changing the destination later updates every email using that link. It is the single biggest maintenance win in the GoHighLevel email builder.
A trigger link on an unauthenticated redirect domain, sent through a poorly warmed Mailgun setup, lands in Promotions or worse. Sort your sending domain, DKIM and SPF before you obsess over click data, as covered in my guide to GoHighLevel email deliverability and Mailgun setup.
In SMS
SMS is where trigger links earn their money and cause the most trouble. A short branded redirect keeps the message under the segment limit and gives you attribution raw URLs cannot. But Australian carriers filter shortened links aggressively, particularly on generic shared domains, and public shorteners such as bit.ly are routinely blocked outright.
Three rules for SMS in Australia. Use a branded redirect subdomain, never a shared one. Register the link domain in your A2P 10DLC campaign if you send to United States numbers, and keep sender details consistent domestically. Always include an opt-out instruction, because Spam Act and ACMA requirements are not optional and a click is not consent. Registration steps are in the GoHighLevel A2P 10DLC registration guide.
UTM parameters and custom values inside trigger links
The redirect URL field accepts query parameters, so you can append UTMs to feed Google Analytics or your reporting layer. A typical destination looks like https://client.com.au/pricing?utm_source=ghl&utm_medium=email&utm_campaign=winback-aug26.
Using custom values so you do not rebuild links
Hard-coding a campaign name into forty links is how snapshots become unmaintainable. Instead, store the changeable part as a custom value at sub-account level and reference it in the redirect URL. When you roll the snapshot into a new client, you update one custom value rather than auditing every link.
You can also append contact merge fields to pre-fill a landing page form. Test this carefully: values containing spaces or apostrophes need encoding, and an unencoded parameter breaks the redirect for some contacts and not others.
Interest-based segmentation recipes
Three-topic interest sort
Send one email with three links, each a separate trigger link: a pricing page, a case study, and a how-it-works explainer. Three workflows, one per link, each adding a distinct tag. Within a week you know which third of the list wants commercials, which wants proof and which wants education.
Dormant list reactivation
Send a low-friction message with a single trigger link and no form. Anyone who clicks gets tagged reactivated-2026 and moves into a live pipeline stage; anyone silent after three touches gets suppressed. That is the backbone of a properly run GoHighLevel database reactivation campaign.
Score-then-route
Assign point values by link: explainer one point, case study three, pricing five. Store the running total in a numeric custom field. When it crosses ten, the workflow creates an opportunity and notifies the assigned user, which slots neatly into a broader GoHighLevel pipeline automation setup. Contacts below ten stay in nurture.
Conversation AI handoff
A pricing link click is a good moment to start a conversation rather than send another email. Trigger a Conversation AI bot with an opening question referencing what they looked at; the specificity lifts reply rates.
Reporting on click data
Aggregate and unique click totals per link appear in the Trigger Links list, and email campaign statistics show click-through rates per send. For contact-level detail you filter Smart Lists by the tag you applied on click, which is why the tagging step is not optional even when you only wanted a notification.
For anything more sophisticated, push the click event to a reporting tool via an outbound webhook on the click workflow. That is the only reliable route to cross-campaign attribution. Feature availability differs by plan, so check the current GoHighLevel help documentation and the GoHighLevel pricing page before promising a client a reporting build.
Limitations you should know before you build
HighLevel trigger links are deliberately simple, and that simplicity comes with edges. There is no per-contact unique URL in the sense of a genuinely distinct link string per recipient, so a contact who forwards an email to a colleague will have the colleague's click recorded against the original contact. Treat click data as directional, not forensic.
Deleting a trigger link breaks every message that references it, including emails already sitting in inboxes. Rename freely, delete almost never.
Common mistakes to avoid
- Leaving links on the shared LeadConnector redirect domain instead of a branded subdomain, then wondering why SMS delivery is poor on Australian carriers.
- Pasting the trigger link into social posts or a website button, where no contact is attached, then reporting the raw click count as engagement.
- Forgetting to enable re-entry on scoring workflows, so a contact's second and third clicks are silently discarded.
- Deleting or replacing a trigger link mid-campaign, breaking every email already sitting in a recipient's inbox.
- Treating a click as consent to be called or SMSed, which is not how the Spam Act or ACMA expectations work in Australia.
- Hard-coding UTM campaign names into dozens of links instead of pulling them from custom values, making the snapshot painful to reuse.
If you want your GoHighLevel trigger links, tagging and follow-up workflows built properly the first time, book a strategy call with the HL Growth Partner team.
Frequently asked questions
Where do I create GoHighLevel trigger links?
Go to Marketing, then Trigger Links, inside the sub-account. Add a name for internal reference, the destination URL the contact will land on, and optionally a custom slug on your redirect domain. Once saved the link appears in the email and SMS builders and in the Trigger Link Clicked workflow trigger dropdown.
Do trigger links work if I post them on social media?
The redirect works and the aggregate click count increments, but no contact is attached, so no workflow fires and nothing is recorded on any contact record. Trigger links only attribute clicks when they are sent to a known contact through a workflow email, workflow SMS, bulk campaign or conversation message. For social and paid traffic, use UTM parameters and your normal analytics tool.
Will Australian carriers block trigger links in SMS?
Shortened links on generic shared domains are frequently filtered on Australian routes, and public shorteners such as bit.ly are commonly blocked outright. Using a branded redirect subdomain on the client's own domain, with consistent sender identification and a clear opt-out instruction, substantially reduces filtering and keeps you aligned with ACMA requirements.
Can I add UTM parameters to a trigger link?
Yes. The destination URL field accepts query parameters, so you can append utm_source, utm_medium and utm_campaign values that pass through to the landing page and into Google Analytics. Store the campaign name as a sub-account custom value and reference it in the URL so you only update it in one place when reusing the snapshot.
How do I stop a workflow ignoring repeat clicks?
Enable Allow Re-entry in the workflow settings. By default GoHighLevel will not re-enter a contact who has already passed through the workflow, so second and third clicks are discarded. Turn re-entry on for engagement scoring workflows and leave it off for one-time actions such as delivering a lead magnet.
