How to Add a Mautic Unsubscribe Link: The Complete 2026 Guide

Master the art of adding a Mautic unsubscribe link effortlessly and discover why it’s crucial for your email campaigns and compliance.
Alaa
By Alaa
SMTPedia documents email infrastructure end to end: SMTP standards from the RFC archive, delivera...
4 min read Updated Jul 28, 2026 91 views

Mautic is an open-source marketing automation platform popular with developers, agencies, and organizations wanting self-hosted control over marketing data. The unsubscribe mechanism uses the {unsubscribe_url} merge token in email templates, and Mautic supports RFC 8058 header injection through the transport configuration (typically an SMTP relay or Amazon SES). Consent is tracked at the contact level with per-segment opt-out granularity. Self-hosted deployment requires PHP, MySQL or MariaDB, and outbound SMTP configuration. This guide covers the tag, the transport model, and how to verify the setup end to end.

Quick reference

Mautic unsubscribe link

Tag syntax{unsubscribe_url}
PlacementAuto-embedded via default footer template
ScopeContact-level opt-out with per-segment granularity
Config pathConfiguration > Email settings > Mailer transport
RFC 8058 one-clickManual configuration at mailer transport level

How to add the unsubscribe tag in Mautic

Place the merge tag exactly as shown below in the email template. Mautic 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>
Default footer

Auto-embedded via default footer template

!
RFC 8058 one-click: manual header required

Manual configuration at mailer transport level 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.

!
Watch out for this

Mautic self-hosted deployments require the operator to configure RFC 8058 headers at the mailer transport level (SMTP relay Configuration Set for SES, custom headers for other SMTP providers). Mautic itself does not inject headers directly; it hands off to the configured transport. Missing this configuration silently falls out of one-click compliance regardless of Mautic UI settings.

Testing your Mautic unsubscribe link

  1. Send a test message to a controlled Gmail address you own via the Mautic campaign preview action
  2. Click the footer unsubscribe link and confirm the opt-out on the landing page
  3. Check the subscriber or contact record: the status should be Unsubscribed within seconds
  4. Verify the RFC 8058 headers in Gmail: open the message, click three dots, then Show original. Look for List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click
S

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 →

Mautic default footer includes the unsubscribe link, but custom email templates may require the merge token inserted manually.

  1. Open your Mautic email or template in the Content editor.
  2. Add or edit a text block in the footer where the unsubscribe link should appear.
  3. Insert the merge token {unsubscribe_url}. Mautic replaces it at send time with a signed URL scoped to the contact.
  4. Wrap it in an anchor: <a href="{unsubscribe_url}">Unsubscribe</a>.
  5. Configure the mailer transport under Configuration > Email settings to enable RFC 8058 List-Unsubscribe headers (SMTP relay or SES Configuration Set).
  6. Send a test to a seed address and verify the rendered link routes to the Mautic-hosted unsubscribe confirmation page.

Self-hosted deployment and transport configuration

Mautic self-hosted deployments require the operator to configure RFC 8058 headers at the mailer transport level (SMTP relay Configuration Set for SES, custom headers for other SMTP providers). Mautic itself does not inject headers directly; it hands off to the configured transport. Missing this configuration silently falls out of one-click compliance regardless of Mautic UI settings. Popular transport combinations: Amazon SES + Configuration Set for cost, SendGrid + Custom Headers for turnkey compliance, self-managed Postfix + config for full control.

Contact-level opt-out and segment enforcement

Mautic tracks unsubscribes at the contact level with per-segment opt-out granularity. A contact who opts out via one campaign is added to the Do Not Contact list (Mautic terminology) and blocked from all future marketing sends. Segment-level opt-out lets contacts leave one segment while remaining on others through the preference center. Marketing automation workflows respect the Do Not Contact flag at every step, exiting contacts who unsubscribe mid-flow. Contact ownership stays with the operator via the self-hosted database.

Open-source community and enterprise support

Mautic distinguishes from proprietary marketing automation with its open-source foundation (LAMP stack, Symfony framework) and active community. Enterprise support is available through Acquia (which now stewards the Mautic project) for organizations wanting managed hosting, security patches, and priority support. Community edition is free and self-supported, popular with agencies and organizations with dedicated technical teams. Both editions share the same core codebase and merge token syntax.

Frequently Asked Questions

What is the Mautic unsubscribe tag?

The merge token is {unsubscribe_url}. Mautic replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="{unsubscribe_url}">Unsubscribe</a>.

Does Mautic support one-click unsubscribe for Gmail and Yahoo?

Only when the mailer transport is configured for RFC 8058 headers. Mautic itself does not inject headers; it hands off to the configured transport. Configure SMTP relay or SES Configuration Set for List-Unsubscribe headers.

What is the Do Not Contact list in Mautic?

The account-level suppression list. Contacts who unsubscribe or are marked as bounced hard get added and blocked from all future marketing sends. Marketing automation workflows respect the Do Not Contact flag at every step.

Is Mautic Community edition suitable for production?

Yes with proper technical resources. Community edition is used in production by many agencies and organizations. Enterprise support via Acquia is available for managed hosting, security patches, and priority support if community self-support is not feasible.

Can I migrate from HubSpot or Marketo to Mautic?

Yes technically. Contact data, segments, and workflow logic can be migrated. Suppression list export from HubSpot or Marketo imports into the Mautic Do Not Contact list to preserve opt-out history. Merge tag syntax differs and requires template conversion.


About the Author

Alaa - SMTPedia 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.