How to Add a We-Connect Unsubscribe Link: The Complete 2026 Guide

Get your emails compliant and user-friendly by adding the We-Connect.Io unsubscribe link, discover the simple steps that ensure seamless opt-outs.
Alaa
By Alaa
SMTPedia documents email infrastructure end to end: SMTP standards from the RFC archive, delivera...
4 min read Updated Jul 28, 2026 100 views

We-Connect is a LinkedIn automation platform primarily used for LinkedIn outreach and connection requests, with email follow-up sequences to warm LinkedIn contacts. The email unsubscribe mechanism uses the {{unsubscribe_link}} merge variable placed manually in the email body of follow-up sequences. We-Connect tracks opt-outs at the workspace level and syncs to LinkedIn contact records where possible. RFC 8058 compliance depends on the connected mailbox authentication. This guide covers the tag, the LinkedIn-plus-email hybrid flow, and how to verify the setup end to end.

Quick reference

We Connect Io unsubscribe link

Tag syntax{{unsubscribe_link}}
PlacementManual placement in the email follow-up body
ScopeWorkspace-wide opt-out with LinkedIn contact sync
Config pathSettings > Email follow-ups > Unsubscribe management
RFC 8058 one-clickDepends on connected mailbox (Google Workspace, Microsoft 365) authentication

How to add the unsubscribe tag in We Connect Io

Place the merge tag exactly as shown below in the email template. We Connect Io 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 the email follow-up body

!
RFC 8058 one-click: partial (see details)

Depends on connected mailbox (Google Workspace, Microsoft 365) authentication 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

We-Connect email follow-ups are secondary to the LinkedIn outreach flow, but must still comply with CAN-SPAM and GDPR since the emails reach recipient inboxes. Cold email best practices apply: place the unsubscribe link in the P.S. of the message body, monitor complaint rates, and honor opt-outs across both LinkedIn and email channels via cross-channel enforcement.

Testing your We Connect Io unsubscribe link

  1. Send a test message to a controlled Gmail address you own via the We Connect Io 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 →

We-Connect email follow-up sequences require manual placement of the unsubscribe tag in the email body since cold outreach best practices place opt-out in the P.S. rather than a footer.

  1. Open your email follow-up sequence step in We-Connect.
  2. Edit the message body where the unsubscribe link should appear (typically P.S. line for cold outreach).
  3. Insert the merge variable {{unsubscribe_link}}. We-Connect replaces it at send time with a signed URL scoped to the LinkedIn contact.
  4. Wrap in an anchor with a natural label: P.S. Prefer not to hear from me? <a href="{{unsubscribe_link}}">Opt out here</a>.
  5. Configure email follow-up settings under Settings > Email follow-ups > Unsubscribe management.
  6. Send a test to a seed address and verify the rendered link routes to the We-Connect-hosted opt-out confirmation page.

LinkedIn plus email hybrid flow

We-Connect email follow-ups are secondary to the LinkedIn outreach flow, but must still comply with CAN-SPAM and GDPR since the emails reach recipient inboxes. Cold email best practices apply: place the unsubscribe link in the P.S. of the message body, monitor complaint rates weekly, and honor opt-outs across both LinkedIn and email channels via cross-channel enforcement. A prospect who opts out of email should also stop receiving LinkedIn automation messages from the same sender, since they signaled disinterest in the sender relationship.

RFC 8058 and mailbox authentication

We-Connect email follow-ups send from personal Gmail Workspace or Microsoft 365 mailboxes connected to the user account. RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers inject when the connected mailbox has SPF, DKIM, and DMARC aligned. Personal Gmail accounts without workspace authentication do not qualify for one-click compliance. Since We-Connect email volume per sender is typically lower than pure email outreach platforms, RFC 8058 compliance is less critical for total sender reputation, but still recommended for inbox placement.

Workspace-wide opt-out and LinkedIn sync

We-Connect applies opt-outs at the workspace level: a LinkedIn contact who unsubscribes from email is skipped in every future email follow-up sequence in the same workspace. LinkedIn contact sync is best-effort: opt-outs write back to the LinkedIn contact record where the LinkedIn API permits, but LinkedIn does not expose a formal marketing opt-out field the way HubSpot or Salesforce do. Cross-channel enforcement is available under workspace settings to also stop LinkedIn outreach automation for opt-out contacts.

Frequently Asked Questions

What is the We-Connect email unsubscribe tag?

The tag is {{unsubscribe_link}}. We-Connect replaces it at send time with a signed URL scoped to the LinkedIn contact. Use it inside an anchor: <a href="{{unsubscribe_link}}">Unsubscribe</a>, placed in the P.S. of the email body.

Does an email opt-out stop LinkedIn outreach on We-Connect?

Only when cross-channel enforcement is enabled under workspace settings. By default, email opt-out stops future email follow-ups but LinkedIn outreach continues on the same contact. Enable cross-channel enforcement to sync opt-outs across both channels.

Does We-Connect support one-click unsubscribe for Gmail and Yahoo?

Only when the connected mailbox is authenticated. We-Connect injects List-Unsubscribe and List-Unsubscribe-Post headers when the connected Gmail Workspace or Microsoft 365 mailbox has SPF, DKIM, and DMARC aligned.

Do LinkedIn contact opt-outs sync back to LinkedIn?

Best-effort only. LinkedIn does not expose a formal marketing opt-out field the way HubSpot or Salesforce do, so We-Connect writes opt-outs to internal contact notes and the workspace suppression list. Cross-referencing with LinkedIn Sales Navigator or Recruiter Lite is manual.

Is We-Connect suitable for pure email outreach without LinkedIn?

Not the primary use case. We-Connect email follow-ups are secondary to LinkedIn outreach. For pure email cold outreach, dedicated platforms like Lemlist, SmartLead, or Instantly.ai offer more sophisticated deliverability and sequence tooling.


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.