SalesBlink is a cold outreach automation platform combining email sequences, LinkedIn outreach, and CRM tracking for SDRs, agencies, and B2B sales teams. The unsubscribe mechanism uses the {{unsubscribe}} merge variable placed manually in the email body, with automatic reply-based opt-out detection. SalesBlink tracks opt-outs at the workspace level with CRM sync options for HubSpot, Pipedrive, and Salesforce. RFC 8058 compliance depends on the sending mailbox authentication. This guide covers the tag, the multi-mailbox rotation model, and how to verify the setup end to end.
SalesBlink unsubscribe link
| Tag syntax | {{unsubscribe}} |
| Placement | Manual placement in the email body |
| Scope | Workspace-wide opt-out with CRM sync |
| Config path | Settings > Unsubscribes > Configuration |
| RFC 8058 one-click | Depends on connected mailbox (Google Workspace, Microsoft 365) authentication |
How to add the unsubscribe tag in SalesBlink
Place the merge tag exactly as shown below in the email template. SalesBlink replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribe}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribe}}">Unsubscribe from this list</a>Manual placement in the email body
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.
SalesBlink multi-mailbox rotation across dozens of sending mailboxes creates inconsistent RFC 8058 compliance if some mailboxes are not authenticated. Audit each rotating mailbox SPF, DKIM, and DMARC alignment before enabling rotation for high-volume outbound. A mixed pool of authenticated and unauthenticated mailboxes creates inconsistent one-click compliance across the campaign.
Testing your SalesBlink unsubscribe link
- Send a test message to a controlled Gmail address you own via the SalesBlink 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 SalesBlink unsubscribe link (step by step)
SalesBlink cold outreach templates require the unsubscribe merge variable inserted manually in the email body. There is no auto-injected footer since cold outreach templates aim for personal-feel formatting.
- Open your sequence or template in the SalesBlink editor.
- Add the merge variable
{{unsubscribe}}at the end of the email body, typically after your signature. - Wrap it in an anchor:
<a href="{{unsubscribe}}">Unsubscribe</a>. Or embed as a short phrase:Reply STOP or click here to unsubscribe: {{unsubscribe}}. - Configure workspace-level unsubscribe handling under Settings > Unsubscribes > Configuration.
- Enable CRM sync for HubSpot, Pipedrive, or Salesforce so opt-out state writes back to the CRM contact.
- Send a test through each rotating mailbox and verify the rendered link routes to the SalesBlink-hosted preference page.
Multi-mailbox rotation and RFC 8058
SalesBlink multi-mailbox rotation across dozens of sending mailboxes creates inconsistent RFC 8058 compliance if some mailboxes are not authenticated. Audit each rotating mailbox SPF, DKIM, and DMARC alignment before enabling rotation for high-volume outbound. A mixed pool of authenticated and unauthenticated mailboxes creates inconsistent one-click compliance across the campaign, hurting deliverability for the unauthenticated portion while the authenticated portion looks fine. This is a common cold outreach gotcha analogous to Smartlead, Instantly, and Lemlist rotation configurations.
CRM sync with HubSpot, Pipedrive, Salesforce
SalesBlink CRM integrations write opt-out state back to the CRM contact record when an outreach recipient unsubscribes or replies with an opt-out keyword. Configure the sync direction and field mapping carefully: a bidirectional sync means a CRM-side opt-out also suppresses further SalesBlink sends, which is usually the desired B2B behavior. Missing this sync creates situations where a prospect who unsubscribes from a SalesBlink sequence still receives outreach from a manual CRM-triggered email.
Reply-based opt-out detection
SalesBlink reply-based opt-out detection scans incoming replies for common unsubscribe phrases (stop, unsubscribe, remove, take me off) and auto-suppresses the contact. This complements the link-based unsubscribe path for prospects who reply with a natural-language opt-out instead of clicking the link. Configure keyword sensitivity carefully to avoid false positives (a prospect saying stop by, would love to meet should not trigger opt-out). Language-specific keyword sets support German, French, and Spanish outreach.
Frequently Asked Questions
What is the SalesBlink unsubscribe tag?
The merge variable is {{unsubscribe}}. SalesBlink replaces it at send time with a workspace-scoped signed URL. Place it manually in the email body since cold outreach templates typically avoid auto-injected footers.
Does SalesBlink support one-click unsubscribe for Gmail and Yahoo?
Depends on the sending mailbox authentication. Google Workspace and Microsoft 365 mailboxes with proper SPF, DKIM, and DMARC alignment inherit RFC 8058 headers. Unauthenticated mailboxes fall out of one-click compliance regardless of SalesBlink UI settings.
Does SalesBlink detect reply-based opt-outs?
Yes. SalesBlink scans incoming replies for common unsubscribe phrases and auto-suppresses the contact. Language-specific keyword sets support German, French, and Spanish outreach.
How does SalesBlink handle multi-mailbox rotation compliance?
Each rotating mailbox must be independently authenticated with SPF, DKIM, and DMARC. A mixed pool of authenticated and unauthenticated mailboxes creates inconsistent one-click compliance across the campaign. Audit each mailbox before enabling rotation.
Which CRMs does SalesBlink sync opt-outs to?
HubSpot, Pipedrive, and Salesforce native integrations. Configure bidirectional sync so CRM-side opt-outs also suppress further SalesBlink sends, preventing outreach from manual CRM-triggered emails to unsubscribed prospects.
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.
