CleverReach is a German email marketing platform serving DACH SMBs and mid-market with drag-and-drop editor, automation flows, integrated CRM connectors, and German data residency. The unsubscribe mechanism uses the {UNSUBSCRIBE} merge tag auto-injected into every campaign footer, and CleverReach emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the recipient list level with DSGVO double opt-in enforcement. This guide covers the tag, the list-level opt-out model, and how to verify the setup end to end.
CleverReach unsubscribe link
| Tag syntax | {UNSUBSCRIBE} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with DSGVO double opt-in |
| Config path | My Account > Sender identity > Footer template |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in CleverReach
Place the merge tag exactly as shown below in the email template. CleverReach 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 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.
CleverReach enforces DSGVO double opt-in by default matching German UWG requirements. Imported contact lists without documented double opt-in are quarantined until confirmed. Multi-list accounts should note that opt-out is per-list by default, not global: a contact who unsubscribes from List A remains subscribed to List B unless account-wide suppression is enabled. Configure suppression scope based on your regulatory interpretation and audience overlap.
Testing your CleverReach unsubscribe link
- Send a test message to a controlled Gmail address you own via the CleverReach 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 CleverReach unsubscribe link (step by step)
CleverReach 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 CleverReach editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{UNSUBSCRIBE}. CleverReach replaces it at send time with a signed URL scoped to the recipient list. - Wrap it in an anchor:
<a href="{UNSUBSCRIBE}">Abmelden</a>for German,Unsubscribefor English. - Configure the sender identity under My Account > Sender identity.
- Send a test to a seed address and verify the rendered link routes to the CleverReach-hosted preference page.
List-level opt-out and multi-list accounts
CleverReach opt-out is per-list by default, not global: a contact who unsubscribes from List A remains subscribed to List B unless account-wide suppression is enabled. Multi-list accounts should decide during setup whether business logic requires unified opt-out (typical for single-brand senders) or per-list scoping (typical for multi-product publishers where lists represent distinct newsletters). Configure suppression scope based on your regulatory interpretation and audience overlap.
RFC 8058 one-click headers
CleverReach 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 My Account > Sender identity. SPF and DKIM records must be verified. One-click unsubscribe defaults to the specific list the send originated from, matching CleverReach per-list opt-out model.
DSGVO double opt-in enforcement
CleverReach enforces DSGVO double opt-in by default matching German UWG requirements. Imported contact lists without documented double opt-in are quarantined until confirmed. German and Austrian senders migrating from single opt-in ESPs must run a re-permission campaign. This is stricter than US CAN-SPAM but matches DACH regulatory expectations. The Deutsch-native admin UI simplifies configuration for German-speaking teams.
Frequently Asked Questions
What is the CleverReach unsubscribe tag?
The merge tag is {UNSUBSCRIBE}. CleverReach replaces it at send time with a signed URL scoped to the recipient list. Use it inside an anchor: <a href="{UNSUBSCRIBE}">Abmelden</a>.
Is CleverReach opt-out per-list or global?
Per-list by default. A contact who unsubscribes from List A remains subscribed to List B unless account-wide suppression is enabled. Configure based on regulatory interpretation and audience overlap.
Does CleverReach support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. CleverReach injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under My Account > Sender identity.
Does CleverReach enforce DSGVO double opt-in?
Yes by default matching German UWG requirements. Imported contact lists without documented double opt-in are quarantined until confirmed. DACH senders migrating from single opt-in ESPs must run a re-permission campaign.
How does CleverReach compare to Kajomi or Maileon?
All three are DACH-focused ESPs with DSGVO double opt-in defaults. CleverReach focuses on drag-and-drop simplicity for SMB. Kajomi differentiates with integrated CRM. Maileon targets larger accounts with omnichannel features. Vendor choice depends on feature depth needs.
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.
