Sender.net is a Lithuanian email marketing platform popular with SMBs and e-commerce operators looking for an aggressive free tier (up to 15,000 emails per month) plus native SMS and web push channels. The unsubscribe mechanism uses the {$unsubscribe} merge variable auto-injected into every campaign footer, and Sender.net emits RFC 8058 headers automatically once the sending domain is authenticated. Consent is tracked per-list, with an alternative all-lists opt-out variable available. This guide covers the tag, the per-list scope, and how to verify the setup end to end.
Sender Net unsubscribe link
| Tag syntax | {$unsubscribe} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with all-lists variant |
| Config path | Settings > Email footer > Manage template |
| RFC 8058 one-click | Yes, automatic once sending domain is authenticated |
How to add the unsubscribe tag in Sender Net
Place the merge tag exactly as shown below in the email template. Sender Net 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>Auto-embedded in every campaign footer
Yes, automatic once sending domain is authenticated 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.
Sender.net WooCommerce sync writes the opt-out state back to the WooCommerce customer record only when the "Two-way sync" toggle is on. Without it, a Sender.net unsubscribe leaves the WooCommerce record marked as opted-in, which corrupts downstream integrations reading customer consent from WooCommerce.
Testing your Sender Net unsubscribe link
- Send a test message to a controlled Gmail address you own via the Sender Net 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 Sender.net unsubscribe link (step by step)
Sender.net drag-and-drop templates include the unsubscribe link in the default footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the Sender.net editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge variable
{$unsubscribe}. Sender.net replaces it at send time with a signed URL unique per subscriber. - Wrap it in an anchor with your preferred label:
<a href="{$unsubscribe}">Unsubscribe</a>. - Add the physical postal address. Sender.net reads it from Settings > Email footer.
- Send a test to a seed address and verify the rendered link routes to the Sender.net-hosted preference page.
Per-list opt-out and all-lists variant
Sender.net applies unsubscribes per list by default. A subscriber who unsubscribes from List A remains active on List B in the same account. To offer an account-wide opt-out link, use the alternative {$unsubscribe_from_all} merge variable which flips the address on every list in the account and adds it to a permanent blocklist. Multi-brand accounts often expose both links in the footer: per-list opt-out as primary, all-lists opt-out as secondary.
RFC 8058 one-click headers
Sender.net 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 Account > Sending domains. SPF and DKIM records must be verified. The free tier (15,000 emails per month) includes automatic RFC 8058 header injection for authenticated domains, matching paid tier one-click compliance.
WooCommerce integration and cross-channel
Sender.net WooCommerce sync writes the opt-out state back to the WooCommerce customer record only when the two-way sync toggle is enabled. Without it, a Sender.net unsubscribe leaves the WooCommerce record marked as opted-in, corrupting downstream integrations reading customer consent from WooCommerce. Multi-channel campaigns (email, SMS, web push) track opt-out per channel by default; cross-channel enforcement is available under account settings to sync opt-outs across all channels simultaneously.
Frequently Asked Questions
What is the Sender.net unsubscribe tag?
The tag is {$unsubscribe}. Sender.net replaces it at send time with a signed URL unique per subscriber. Use it inside an anchor: <a href="{$unsubscribe}">Unsubscribe</a>. For account-wide opt-out use {$unsubscribe_from_all}.
Does the free tier include one-click unsubscribe?
Yes. The Sender.net free tier (up to 15,000 emails per month) includes automatic List-Unsubscribe and List-Unsubscribe-Post header injection on authenticated domains, matching paid tier compliance with the Google and Yahoo bulk-sender requirements.
Does the WooCommerce integration sync unsubscribes back to the store?
Only when the two-way sync toggle is enabled under integration settings. Without it, a Sender.net unsubscribe leaves the WooCommerce record marked as opted-in, corrupting downstream integrations reading consent from WooCommerce.
Does an email unsubscribe stop SMS and web push on Sender.net?
No by default. Email unsubscribe applies only to the email channel. To sync across email, SMS, and web push simultaneously, enable cross-channel enforcement under account settings.
Can I resubscribe a contact who unsubscribed from Sender.net?
No, not through the API. Sender.net enforces permanent suppression on opt-outs. The contact must re-opt in through a Sender.net signup form, which triggers a fresh double opt-in confirmation email.
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.
