SharpSpring Mail (now part of Constant Contact after the 2021 acquisition) is a marketing automation platform serving agencies and mid-market B2B customers with lead scoring, dynamic content, and CRM integration. The unsubscribe mechanism uses the {{unsubscribe_link}} merge tag auto-injected into every campaign footer, and SharpSpring Mail emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with agency multi-tenant client separation. This guide covers the tag, the agency architecture, and how to verify the setup end to end.
SharpSpring Mail+ unsubscribe link
| Tag syntax | {{unsubscribe_link}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with agency multi-tenant separation |
| Config path | Settings > Email > Sender configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in SharpSpring Mail+
Place the merge tag exactly as shown below in the email template. SharpSpring Mail+ 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>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.
SharpSpring Mail agency multi-tenant architecture isolates consent per client tenant by default. An unsubscribe on Client A does not suppress the contact on Client B (same email may exist in multiple agency-managed tenants). Agencies managing overlapping contact bases across clients should carefully configure per-tenant vs cross-tenant suppression rules to match regulatory expectations. Constant Contact acquisition integration paths may vary by legacy account.
Testing your SharpSpring Mail+ unsubscribe link
- Send a test message to a controlled Gmail address you own via the SharpSpring Mail+ 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 SharpSpring Mail unsubscribe link (step by step)
SharpSpring Mail default templates include the unsubscribe link in the footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the SharpSpring Mail editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{{unsubscribe_link}}. SharpSpring Mail replaces it at send time with a signed URL scoped to the contact and tenant. - Wrap it in an anchor:
<a href="{{unsubscribe_link}}">Unsubscribe</a>. - Configure the sender identity under Settings > Email > Sender configuration.
- Send a test to a seed address and verify the rendered link routes to the SharpSpring-hosted preference page.
Agency multi-tenant architecture and cross-tenant suppression
SharpSpring Mail agency multi-tenant architecture isolates consent per client tenant by default. An unsubscribe on Client A does not suppress the contact on Client B (same email may exist in multiple agency-managed tenants). Agencies managing overlapping contact bases across clients should carefully configure per-tenant vs cross-tenant suppression rules to match regulatory expectations. Constant Contact acquisition integration paths may vary by legacy account, so agencies with pre-2021 SharpSpring accounts should verify current documentation.
RFC 8058 one-click headers
SharpSpring Mail 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 domains authenticated under Settings > Email > Sender configuration. SPF and DKIM records must be verified per tenant. Agency-managed accounts should audit each client tenant s domain authentication separately since RFC 8058 compliance is per-tenant not shared.
Lead scoring and dynamic content enforcement
SharpSpring Mail lead scoring and dynamic content workflows respect the contact opt-out flag at every send step. A contact who unsubscribes exits the workflow automatically and can be routed to alternative paths (sales rep manual outreach, cross-tenant re-engagement in an agency setup). Dynamic content blocks personalized by lead score do not fire for opted-out contacts. CRM sync with connected CRMs writes opt-out state back to the CRM contact record automatically per-tenant configuration.
Frequently Asked Questions
What is the SharpSpring Mail unsubscribe tag?
The merge tag is {{unsubscribe_link}}. SharpSpring Mail replaces it at send time with a signed URL scoped to the contact and tenant. Use it inside an anchor: <a href="{{unsubscribe_link}}">Unsubscribe</a>.
Do SharpSpring Mail agency clients share suppression?
Not by default. Multi-tenant architecture isolates consent per client tenant. An unsubscribe on Client A does not suppress the contact on Client B. Configure cross-tenant suppression rules only when regulatory expectations require unified opt-out enforcement.
Does SharpSpring Mail support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. SharpSpring Mail injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified per tenant.
What happened after Constant Contact acquired SharpSpring?
Constant Contact acquired SharpSpring in 2021. Product integration paths vary by legacy account. Agencies with pre-2021 SharpSpring accounts should verify current documentation and confirm consent handling has not shifted during integration cycles.
Do SharpSpring Mail workflows respect lead score opt-outs?
Yes. Lead scoring and dynamic content workflows respect the contact opt-out flag at every send step. Dynamic content blocks personalized by lead score do not fire for opted-out contacts.
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.
