GoHighLevel (HighLevel) is an agency-focused all-in-one platform combining CRM, marketing automation, funnel builder, and SMS/email/voice messaging, popular with marketing agencies serving local businesses under white-label. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag auto-injected into every campaign footer, and GoHighLevel emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the sub-account level with agency multi-tenant isolation. This guide covers the tag, the sub-account architecture, and how to verify the setup end to end.
GoHighLevel unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Sub-account contact-level opt-out with multi-tenant isolation |
| Config path | Sub-account > Settings > Email services |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in GoHighLevel
Place the merge tag exactly as shown below in the email template. GoHighLevel replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribe_url}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribe_url}}">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Yes, automatic for authenticated sending domains The recipient's mailbox provider (Gmail, Yahoo) uses the List-Unsubscribe-Post header to expose the native one-click button on the message. Requires domain authentication with DKIM and DMARC.
GoHighLevel agency multi-tenant architecture isolates consent per sub-account (client) by default. An unsubscribe on Sub-account A does not suppress the contact on Sub-account B (same email may exist in multiple agency-managed sub-accounts). White-label agencies serving overlapping contact bases should configure per-sub-account vs cross-sub-account suppression rules carefully to match regulatory expectations. Email sending typically routes through Mailgun or a similar SMTP relay configured per sub-account.
Testing your GoHighLevel unsubscribe link
- Send a test message to a controlled Gmail address you own via the GoHighLevel campaign preview action
- Click the footer unsubscribe link and confirm the opt-out on the landing page
- Check the subscriber or contact record: the status should be Unsubscribed within seconds
- Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for
List-UnsubscribeandList-Unsubscribe-Post: List-Unsubscribe=One-Click
Want the full 222-platform reference?
See the pillar guide with the compliance landscape, the RFC 8058 deep dive, and the unsubscribe tag for every ESP: How to add an unsubscribe link: the complete 2026 guide →
How to add the GoHighLevel unsubscribe link (step by step)
GoHighLevel default templates include the unsubscribe link in the footer, but custom HTML templates require the tag inserted manually inside the sub-account.
- Open your sub-account in the GoHighLevel agency portal.
- Add or edit a text block in the email template footer where the unsubscribe link should appear.
- Insert the merge tag
{{unsubscribe_url}}. GoHighLevel replaces it at send time with a signed URL scoped to the sub-account contact. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - Configure the sending domain under Sub-account > Settings > Email services (typically Mailgun-backed).
- Send a test to a seed address and verify the rendered link routes to the GoHighLevel-hosted preference page.
Agency multi-tenant sub-account isolation
GoHighLevel agency multi-tenant architecture isolates consent per sub-account (client) by default. An unsubscribe on Sub-account A does not suppress the contact on Sub-account B (same email may exist in multiple agency-managed sub-accounts). White-label agencies serving overlapping contact bases should configure per-sub-account vs cross-sub-account suppression rules carefully to match regulatory expectations. Email sending typically routes through Mailgun or a similar SMTP relay configured per sub-account, meaning RFC 8058 compliance depends on per-sub-account authentication.
RFC 8058 one-click headers via sub-account SMTP
GoHighLevel added RFC 8058 one-click unsubscribe automatically ahead of the Google and Yahoo February 2024 requirements. The List-Unsubscribe and List-Unsubscribe-Post headers inject on every marketing send from sub-accounts with authenticated sending domains via connected Mailgun accounts. SPF and DKIM records must be verified per sub-account. Agency-managed accounts should audit each sub-account s domain authentication separately since RFC 8058 compliance is per-sub-account not shared.
Multi-channel messaging and cross-channel consent
GoHighLevel multi-channel messaging (email, SMS, voice) unifies consent state per sub-account contact by default. An email opt-out can propagate to SMS suppression if configured, matching TCPA cross-channel consent expectations for US-based agencies. Voice call opt-outs handled through GoHighLevel automations also flow to the sub-account contact suppression list. Configure per-channel scoping carefully to match regulatory expectations across US CAN-SPAM, TCPA, and international frameworks.
Frequently Asked Questions
What is the GoHighLevel unsubscribe tag?
The merge tag is {{unsubscribe_url}}. GoHighLevel replaces it at send time with a signed URL scoped to the sub-account contact. Use it inside an anchor: <a href="{{unsubscribe_url}}">Unsubscribe</a>.
Do GoHighLevel sub-accounts share suppression?
Not by default. Multi-tenant architecture isolates consent per sub-account. An unsubscribe on Sub-account A does not suppress the contact on Sub-account B. Configure cross-sub-account suppression rules only when regulatory expectations require unified opt-out enforcement.
Does GoHighLevel support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for sub-accounts with authenticated sending domains via connected Mailgun accounts. Audit each sub-account s domain authentication separately since RFC 8058 compliance is per-sub-account.
Do email opt-outs propagate to SMS in GoHighLevel?
Only when cross-channel opt-out is configured. TCPA cross-channel consent expectations for US-based agencies typically favor unified opt-out enforcement across email, SMS, and voice per sub-account contact.
Does GoHighLevel handle its own SMTP or route through Mailgun?
Email sending typically routes through Mailgun or a similar SMTP relay configured per sub-account. Verify the connected Mailgun account s SPF, DKIM, and DMARC alignment to complete RFC 8058 compliance.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
