How to Add a Hexospark Unsubscribe Link: The Complete 2026 Guide

Just follow these simple steps to seamlessly add the Hexospark unsubscribe link and ensure your emails remain compliant and user-friendly.
Alaa
By Alaa
SMTPedia documents email infrastructure end to end: SMTP standards from the RFC archive, delivera...
3 min read Updated Jul 28, 2026 50 views

Hexospark is a cold outreach automation platform serving sales teams and agencies with LinkedIn and email outreach, contact enrichment, and multi-channel sequence automation. The unsubscribe mechanism uses the {unsubscribe_link} merge tag placed in email templates, and Hexospark emits RFC 8058 headers automatically for authenticated sending domains. Suppression is tracked at the contact level with cross-channel enforcement. This guide covers the tag, the multi-channel outreach model, and how to verify the setup end to end.

Quick reference

Hexospark unsubscribe link

Tag syntax{unsubscribe_link}
PlacementManual placement in cold outreach templates
ScopeContact-level opt-out with cross-channel suppression
Config pathSequences > Templates > Footer configuration
RFC 8058 one-clickYes, automatic for authenticated sending domains

How to add the unsubscribe tag in Hexospark

Place the merge tag exactly as shown below in the email template. Hexospark replaces it at send time with a signed URL scoped to the recipient and campaign.

{unsubscribe_link}

For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:

<a href="{unsubscribe_link}">Unsubscribe from this list</a>
Default footer

Manual placement in cold outreach templates

RFC 8058 one-click: automatic

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.

!
Watch out for this

Hexospark multi-channel LinkedIn plus email outreach means opt-out event routing requires care: an email unsubscribe should also stop LinkedIn touchpoints for the same contact under GDPR unified consent interpretation. Configure cross-channel suppression to honor the contact intent. LinkedIn outreach has separate LinkedIn ToS constraints on automation; verify per-account rate limits.

Testing your Hexospark unsubscribe link

  1. Send a test message to a controlled Gmail address you own via the Hexospark campaign preview action
  2. Click the footer unsubscribe link and confirm the opt-out on the landing page
  3. Check the subscriber or contact record: the status should be Unsubscribed within seconds
  4. Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click
S

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 →

  1. Open your outreach sequence template in the Hexospark editor.
  2. Add or edit a text block in the footer.
  3. Insert the merge tag {unsubscribe_link}.
  4. Wrap it in an anchor: <a href="{unsubscribe_link}">Unsubscribe</a>.
  5. Configure the sender identity under Sequences > Templates > Footer configuration.
  6. Send a test to a seed address and verify the rendered link routes to the Hexospark-hosted preference page.

LinkedIn plus email multi-channel

Hexospark multi-channel LinkedIn plus email outreach means opt-out event routing requires care: an email unsubscribe should also stop LinkedIn touchpoints for the same contact under GDPR unified consent interpretation. Configure cross-channel suppression to honor the contact intent. LinkedIn outreach has separate LinkedIn ToS constraints on automation; verify per-account rate limits and connection request limits to avoid LinkedIn platform sanctions.

RFC 8058 one-click headers

Hexospark 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 send from domains authenticated under Sequences > Templates. SPF and DKIM records must be verified. Cold outreach senders benefit from RFC 8058 to maintain inbox placement.

Contact enrichment and sequence automation

Hexospark contact enrichment integrates with sales databases and LinkedIn profile scraping to populate contact records automatically. Sequence automation routes contacts through multi-touch cadences (email 1, LinkedIn connect, email 2, LinkedIn message, email 3) based on engagement signals. Opt-out events at any touchpoint exit the entire sequence and prevent re-entry across future campaigns targeting the same contact.

Frequently Asked Questions

What is the Hexospark unsubscribe tag?

The merge tag is {unsubscribe_link}. Hexospark replaces it at send time with a signed URL scoped to the contact.

Does email opt-out stop LinkedIn on Hexospark?

If cross-channel suppression is configured, yes. GDPR unified consent interpretation expects opt-out to honor across channels. Configure the setting explicitly.

Does Hexospark support one-click unsubscribe for Gmail and Yahoo?

Yes, automatically for authenticated domains. Hexospark injects List-Unsubscribe and List-Unsubscribe-Post headers on every send.

Does LinkedIn automation risk account sanctions?

Yes if rate limits exceeded. LinkedIn ToS restricts automation; verify per-account connection and message rate limits to avoid restriction or ban.

How does Hexospark compare to Reply.io or We-Connect?

All three integrate LinkedIn and email. Hexospark emphasizes contact enrichment. Reply.io has broader multi-channel including phone. We-Connect focuses on LinkedIn-first. Vendor choice depends on channel priorities.


About the Author

Alaa - SMTPedia 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.