SendPulse is a multi-channel messaging platform originally founded in Eastern Europe, offering email marketing, SMS, Web Push, Viber, WhatsApp Business, and chatbot flows from a single dashboard. Popular in emerging markets and among cost-conscious SMBs thanks to its free tier. The unsubscribe mechanism uses a merge tag auto-injected into every email campaign footer. SendPulse emits RFC 8058 one-click headers automatically once the sending domain is authenticated. Contact opt-out state is tracked per-address list, not account-wide, which requires attention when the same subscriber appears in multiple mailing lists across different campaigns.
SendPulse unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-address-list opt-out |
| Config path | Settings > Sender email > Confirm your address |
| RFC 8058 one-click | Yes, automatic once sending domain is authenticated |
How to add the unsubscribe tag in SendPulse
Place the merge tag exactly as shown below in the email template. SendPulse replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribe_url}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribe_url}}">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.
SendPulse tracks unsubscribes per mailing list, not per account. A subscriber unsubscribing from Newsletter List A keeps receiving from Promo List B when they are a member of both. To offer a global opt-out link, use the alternative {{unsubscribe_all}} merge tag which flips the address in every list on the account.
Testing your SendPulse unsubscribe link
- Send a test message to a controlled Gmail address you own via the SendPulse 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 SendPulse handles unsubscribes
SendPulse injects the unsubscribe link through the {{UnsubscribeUrl}} merge variable, replaced with a signed URL at send time. The drag-and-drop editor includes a default footer block with the variable pre-populated, and SendPulse refuses to send campaigns without an unsubscribe mechanism. For custom HTML templates uploaded to SendPulse, the variable must appear at least once, typically wrapped in an anchor tag. Clicks route to a SendPulse-hosted preference page where the subscriber confirms the opt-out and is added to the account suppression list.
Multi-channel account model
SendPulse is a multi-channel platform covering email, SMS, WhatsApp, Web Push, and chatbots. Its unsubscribe model is channel-specific by default: an email unsubscribe removes the contact from email marketing but does not affect SMS or push preferences. Account settings can enforce cross-channel opt-out, applying an email unsubscribe to all channels simultaneously. This is the preferred configuration for consumer brands where users expect a single opt-out to cover all promotional channels from the same sender.
RFC 8058 one-click headers
SendPulse added full RFC 8058 support in early 2024, automatically injecting List-Unsubscribe and List-Unsubscribe-Post headers on all marketing sends from authenticated domains. Domain authentication requires configuring SPF and DKIM records through Settings, and SendPulse verifies the records before enabling one-click headers. This is required for accounts sending significant volume to Gmail and Yahoo (5,000+ messages per day) under the February 2024 bulk-sender requirements.
Suppression list and reactivation
Unsubscribed contacts are added to an account-wide suppression list that blocks sends across all mailing lists in the SendPulse account. This suppression is enforced at send time, preventing accidental re-inclusion through CSV import or manual entry. Reactivation requires a fresh opt-in from the subscriber through a signup form or landing page; forced reactivation through the API is possible but generates a warning to protect senders from CAN-SPAM violations. The suppression list is exposed through the SendPulse API for reconciliation with external CRM systems.
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.
