BACKclick is a German B2B email marketing platform serving mid-market DACH brands with self-hosted and cloud deployment options for enterprise data residency requirements. The unsubscribe mechanism uses the [UNSUBSCRIBE] merge tag in email templates, and BACKclick emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with double opt-in enforcement by default, matching German UWG regulatory expectations. Self-hosted deployments give enterprises full data control for banking, healthcare, and government customers. This guide covers the tag, the deployment models, and how to verify the setup end to end.
Backclick unsubscribe link
| Tag syntax | [UNSUBSCRIBE] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with double opt-in default |
| Config path | Account > Sender configuration > Footer template |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Backclick
Place the merge tag exactly as shown below in the email template. Backclick 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.
BACKclick self-hosted deployments require the customer IT team to configure RFC 8058 headers at the sending infrastructure level, since the platform is running on customer infrastructure. Cloud deployments handle this automatically. Confirm which deployment model your account uses before assuming RFC 8058 compliance; misconfigured self-hosted deployments fall out of one-click compliance silently.
Testing your Backclick unsubscribe link
- Send a test message to a controlled Gmail address you own via the Backclick 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 BACKclick unsubscribe link (step by step)
BACKclick 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 BACKclick editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[UNSUBSCRIBE]. BACKclick replaces it at send time with a signed URL scoped to the contact record. - Wrap it in an anchor with your preferred label:
<a href="[UNSUBSCRIBE]">Abmelden</a>for German audiences. - Add the required legal Impressum block below the footer as required by German TMG law.
- Send a test to a seed address and verify the rendered link routes to the BACKclick-hosted preference page.
Self-hosted vs cloud deployment models
BACKclick self-hosted deployments require the customer IT team to configure RFC 8058 headers at the sending infrastructure level, since the platform is running on customer-controlled infrastructure. Cloud deployments handle RFC 8058 automatically for authenticated domains. Confirm which deployment model your account uses before assuming RFC 8058 compliance; misconfigured self-hosted deployments fall out of one-click compliance silently. Regulated industries (banking, healthcare, government) typically choose self-hosted for data residency and control, accepting the additional IT overhead.
German UWG double opt-in enforcement
BACKclick enforces double opt-in by default in DACH markets to match German UWG (Act Against Unfair Competition) and Austrian TKG requirements. Legacy accounts migrated from other ESPs with single opt-in contacts must run a re-permission campaign before sends can go out. Imported contacts without documented double opt-in are quarantined until confirmed. This is analogous to Maileon and CleverReach DACH-focused compliance patterns. Skip this step and campaign sends fail at pre-flight validation.
Enterprise integrations and audit trails
BACKclick offers native integrations with SAP CRM, Salesforce, and Microsoft Dynamics for enterprise DACH customers who use these systems as CRM masters. Consent state syncs bidirectionally: a contact who unsubscribes via BACKclick flows back to the CRM contact record automatically. GDPR data subject requests (DSRs) trigger cascading deletion across BACKclick suppression and the CRM. Audit trails per-contact are exportable for compliance reviews and regulatory audits in banking and healthcare verticals.
Frequently Asked Questions
What is the BACKclick unsubscribe tag?
The tag is [UNSUBSCRIBE]. BACKclick replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="[UNSUBSCRIBE]">Abmelden</a> for German audiences.
Does BACKclick self-hosted require special RFC 8058 setup?
Yes. Self-hosted deployments require the customer IT team to configure RFC 8058 headers at the sending infrastructure level. Cloud deployments handle this automatically. Confirm your deployment model and verify RFC 8058 header injection status before high-volume sends.
Does BACKclick require double opt-in?
Yes by default in DACH markets. This matches German UWG and Austrian TKG regulatory requirements. Legacy accounts with single opt-in contacts must run a re-permission campaign before campaign sends can proceed. Imported contacts without confirmed opt-in are quarantined until confirmed.
Do BACKclick opt-outs sync to Salesforce and SAP CRM?
Yes via native integrations. A contact who unsubscribes via BACKclick flows back to the CRM contact record automatically. GDPR DSR deletion in the CRM cascades to BACKclick suppression, keeping compliance workflows consistent.
Are BACKclick audit trails suitable for regulated industries?
Yes. Per-contact audit trails are exportable for compliance reviews and regulatory audits. Banking and healthcare customers running self-hosted deployments get full audit control matching their regulatory requirements.
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.
