Esendex is a UK-based multi-channel messaging platform serving mid-market and enterprise customers with SMS, email, WhatsApp, and voice messaging in one unified API and dashboard. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag placed manually in email campaigns, and Esendex emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the recipient level with cross-channel subscription state. This guide covers the tag, the multi-channel consent model, and how to verify the setup end to end.
esendex unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Manual placement in email campaigns |
| Scope | Recipient-level opt-out with cross-channel state |
| Config path | Settings > Email > Sender configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in esendex
Place the merge tag exactly as shown below in the email template. esendex 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>Manual placement in email campaigns
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.
Esendex multi-channel platform unifies consent state across email, SMS, WhatsApp, and voice. An email opt-out does not automatically suppress SMS or WhatsApp sends unless cross-channel opt-out is configured. UK PECR and GDPR may require different consent bases per channel (opt-in for marketing SMS, opt-in for marketing email, transactional SMS by contract). Configure per-channel consent scoping carefully to match regulatory expectations.
Testing your esendex unsubscribe link
- Send a test message to a controlled Gmail address you own via the esendex 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 Esendex unsubscribe link (step by step)
Esendex email campaigns require the unsubscribe merge tag inserted manually in the campaign body since campaigns use flexible templates rather than a fixed footer.
- Open your email campaign in the Esendex dashboard.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{{unsubscribe_url}}. Esendex replaces it at send time with a signed URL scoped to the recipient. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - Configure the sender identity and per-channel consent scoping under Settings > Email > Sender configuration.
- Send a test to a seed address and verify the rendered link routes to the Esendex-hosted preference page.
Multi-channel consent state and per-channel scoping
Esendex multi-channel platform unifies consent state across email, SMS, WhatsApp, and voice. An email opt-out does not automatically suppress SMS or WhatsApp sends unless cross-channel opt-out is configured. UK PECR and GDPR may require different consent bases per channel (opt-in for marketing SMS, opt-in for marketing email, transactional SMS by contract). Configure per-channel consent scoping carefully to match regulatory expectations. This granular per-channel control differs from unified opt-out ESPs like Dotdigital and Braze which propagate opt-outs across all channels by default.
RFC 8058 one-click headers
Esendex 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 email send from domains authenticated under Settings > Email. SPF and DKIM records must be verified. One-click unsubscribe defaults to email-only opt-out, not cross-channel opt-out, matching Esendex per-channel scoping model.
SMS and WhatsApp channel considerations
Esendex SMS and WhatsApp channels have distinct opt-out mechanisms: SMS uses STOP keyword reply detection with UK short code compliance, WhatsApp uses the WhatsApp Business API opt-out flow. Neither uses RFC 8058 headers (which are email-specific). Configure per-channel opt-out enforcement in the Esendex API to keep suppression consistent across channels for the same recipient. Enterprise deployments often integrate Esendex with CRM (Salesforce, Dynamics) to sync multi-channel consent state to the CRM contact record.
Frequently Asked Questions
What is the Esendex unsubscribe tag?
The merge tag is {{unsubscribe_url}}. Esendex replaces it at send time with a signed URL scoped to the recipient. Use it inside an anchor: <a href="{{unsubscribe_url}}">Unsubscribe</a>.
Do email opt-outs propagate to SMS in Esendex?
Only when cross-channel opt-out is configured. UK PECR and GDPR may require different consent bases per channel. Configure per-channel consent scoping carefully to match regulatory expectations.
Does Esendex support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. One-click defaults to email-only opt-out, not cross-channel opt-out, matching Esendex per-channel scoping model.
How does SMS STOP compliance work in Esendex?
SMS uses STOP keyword reply detection with UK short code compliance. When a recipient replies STOP, Esendex adds the phone number to SMS suppression automatically. WhatsApp uses the WhatsApp Business API opt-out flow separately.
Can Esendex sync multi-channel consent to Salesforce?
Yes with CRM integration. Enterprise deployments often integrate Esendex with Salesforce and Dynamics to sync multi-channel consent state to the CRM contact record for unified consent tracking across marketing, sales, and service.
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.
