How to Add an Unsubscribe Link: The Complete 2026 Guide

By Alaa

SMTPedia documents email infrastructure end to end: SMTP standards from the RFC archive, delivera...

22 min read Updated Aug 21, 2026 690 views Save

Adding a compliant unsubscribe link to your email campaigns is required by CAN-SPAM, GDPR, CASL, and LGPD, and audited by Gmail and Yahoo since their February 2024 bulk sender rules. These rules mandate RFC 8058 one-click unsubscribe for any sender crossing 5,000 emails per day to those providers. This guide covers the exact unsubscribe link and tag syntax for every documented email marketing platform: Mailchimp, HubSpot, Klaviyo, SendGrid, Mailgun, ActiveCampaign, ConvertKit, Brevo, and 200+ more, plus how to test that your link actually works and the common per-platform implementation pitfalls. For everything that sits around that link, see how to build the email footer itself.

Unsubscribe link vs unsubscribe tag: what is the difference?

The two terms are often used interchangeably. In practice they refer to different technical objects.

• Unsubscribe tag: the merge variable you place in your email template source code (for example *|UNSUB|* in Mailchimp, {{ unsubscribe_link }} in HubSpot, {% unsubscribe %} in Klaviyo). Not visible to subscribers.
• Unsubscribe link: the rendered URL that appears in the delivered email, produced when the platform substitutes the tag at send time. This is what the subscriber actually clicks.

You configure the tag; the platform generates the link. This guide gives you both: the tag syntax to place in your templates for every documented platform, and the technical details of what the rendered link does, including whether it supports RFC 8058 one-click unsubscribe required by Gmail and Yahoo.

Why unsubscribe links matter more in 2026

Three forces have converged since 2024 to make unsubscribe link compliance the single most audited piece of email infrastructure.

• Gmail and Yahoo bulk sender rules (February 2024): senders exceeding 5,000 emails per day to Gmail or Yahoo must implement one-click unsubscribe via the List-Unsubscribe-Post header (RFC 8058). Non-compliance triggers immediate deliverability degradation.
• Legal exposure at record levels: CAN-SPAM penalties reach $50,120 per violation; GDPR fines can reach €20M or 4% of global revenue; CASL fines reach CAD $10M.
• Complaint rate has become a top reputation signal: mailbox providers weight complaint rate as heavily as authentication. A missing or broken unsubscribe link drives complaint rates up 40% overnight and can blacklist your domain within days.

Getting the unsubscribe link right on every platform you use is not a checkbox item. It is the base layer of sender reputation.

SAAS and Cloud Email Marketing Applications

MailChimp unsubscribe tag

Mailchimp is the default choice for SMBs, startups, and creators shipping their first newsletter. The Mailchimp unsubscribe link renders from a single merge tag placed anywhere in your template. Mailchimp automatically adds the List-Unsubscribe-Post header and satisfies Gmail one-click compliance out of the box; no manual configuration required. If you delete a subscriber list, existing unsubscribe links in delivered emails will show a “This subscription is expired” landing page, so keep list IDs stable.

*|UNSUB|*

HTML Code for Mailchimp unsubscribe:

<a href="*|UNSUB|*">Unsubscribe from this list.</a>

Sendgrid unsubscribe tag

SendGrid (Twilio) is the transactional and marketing send engine used at scale by SaaS applications. The SendGrid unsubscribe link uses a triple-brace substitution and is generated per subscriber group (multiple unsubscribe groups can coexist under one account). SendGrid automatically emits RFC 8058 headers for Marketing Campaigns; for API-driven transactional sends via v3 mail/send you must include asm.group_id or enable global unsubscribe explicitly.

{{{unsubscribe}}}

HTML Code for Sendgrid unsubscribe:

<a href="{{{unsubscribe}}}">Unsubscribe from this list.</a>

Brevo unsubscribe tag (formerly SendinBlue)

Brevo (formerly Sendinblue) targets SMBs and mid-market with a unified marketing plus transactional send platform. The Brevo unsubscribe link uses the same triple-brace syntax as SendGrid, injected in the drag-and-drop editor footer or manually in the HTML editor. Brevo generates List-Unsubscribe headers automatically for marketing campaigns and transactional email via API v3.

{{{unsubscribe}}}

HTML Code for Brevo (Sendinblue) unsubscribe:

<a href="{{{unsubscribe}}}">Unsubscribe from this list.</a>

Unisender unsubscribe tag (formerly Selzy)

Selzy (formerly Unisender) serves e-commerce and SMB in Eastern Europe with a strong template library and automation flows. The unsubscribe URL is exposed via a camelCase merge variable, injected in the drag-and-drop editor footer by default. Selzy handles RFC 8058 headers automatically for standard campaigns; API sends may require passing the list_ids parameter for the unsubscribe link to resolve correctly.

{{UnsubscribeUrl}}

HTML Code for Unisender (Selzy) unsubscribe:

<a href="{{UnsubscribeUrl}}">Unsubscribe from this list.</a>

MailerLite unsubscribe tag

MailerLite is popular for creators, coaches, and content-first newsletters. The unsubscribe variable uses PHP-style dollar-brace syntax. MailerLite automatically adds one-click compliant headers to every marketing send. If you use MailerLite Classic (the legacy version), the tag differs slightly and the new dashboard cannot import Classic templates without manual footer rework.

{$unsubscribe}

HTML Code for Mailer Lite unsubscribe:

<a href="{$unsubscribe}">Unsubscribe from this list.</a>

Constant Contact unsubscribe tag (embedded)

Constant Contact serves SMBs, associations, and non-profits with a strong template library and event registration integrations. Unsubscribe handling is embedded in the default footer; the merge tag lets you place the link anywhere in a custom HTML template. Constant Contact adds RFC 8058 headers automatically for all marketing campaigns. The platform enforces list-level subscriptions, so an unsubscribe only removes the contact from the current list, not the entire account.

${unsubscribe}

HTML Code for Constant Contact unsubscribe:

<a href="${unsubscribe}">Unsubscribe from this list.</a>

ConvertKit unsubscribe

ConvertKit (now marketed as Kit) targets creators and course sellers; the unsubscribe URL is exposed via a Liquid-style double-brace variable. ConvertKit handles List-Unsubscribe headers automatically for broadcasts and sequences. Unsubscribes are account-wide by default; use tag-based segmentation if you need topic-level opt-out instead of full account removal.

{{ unsubscribe_url }}

HTML Code for ConvertKit unsubscribe:

<a href="{{ unsubscribe_url }}">Unsubscribe from this list.</a>

ActiveCampaign unsubscribe tag (embedded)

ActiveCampaign combines marketing automation with a CRM; the unsubscribe URL is auto-substituted via a percent-delimited tag. All standard campaigns include the required RFC 8058 headers; automation-triggered sends inherit the same behavior. If you send transactional email from ActiveCampaign, use the %UNSUBSCRIBELINK% tag with a subscription-type argument to route opt-outs to the right list.

%UNSUBSCRIBELINK%

HTML Code for ActiveCampaign unsubscribe:

<a href="{{ unsubscribe_url }}">Unsubscribe from this list.</a>

GetResponse unsubscribe tag

GetResponse offers marketing automation with landing pages and webinars for SMBs. The unsubscribe link uses a distinctive double-brace-with-backtick syntax that must be included exactly as shown, or the campaign editor will flag the message before send. GetResponse emits List-Unsubscribe headers automatically; the platform also supports a preference center where subscribers can update topic subscriptions instead of unsubscribing fully.

{{LINK `unsubscribe`}}

HTML Code for GetResponse unsubscribe:

<a href="{{LINK `unsubscribe`}}pt=unsubscribe">Unsubscribe from this list.</a>

Mailgun unsubscribe tag

Mailgun is a developer-first SMTP and HTTP API used for transactional email. Two unsubscribe variables exist: %unsubscribe_url% applies at the entire domain level, while %tag_unsubscribe_url% scopes unsubscribes to emails carrying a specific tag (useful for separating product notifications from marketing). Mailgun adds the List-Unsubscribe header when the variable is present in the message body; for RFC 8058 one-click support, enable the “Unsubscribes” feature in the domain settings.

%unsubscribe_url% (for the entire domain) or %tag_unsubscribe_url% (for just emails with this tag, less usual to use this tag)

HTML Code for Mailgun unsubscribe:

<a href="%unsubscribe_url%">Unsubscribe from this list.</a>

AWeber unsubscribe tag

AWeber is one of the oldest email marketing platforms; the unsubscribe URL is exposed via a dot-notation subscriber attribute. AWeber includes the unsubscribe link in every broadcast footer by default and emits RFC 8058 headers automatically. If you send from a custom HTML template that overrides the default footer, insert the merge tag manually or the campaign will be blocked from sending.

{{ subscriber.unsubscribe_link }}

HTML Code for AWeber unsubscribe:

<a href="{{ subscriber.unsubscribe_link }}">Unsubscribe from this list.</a>

Zoho unsubscribe tag

Zoho Campaigns targets Zoho CRM users with unified contact management. The unsubscribe tag uses a custom bracketed syntax and must be wrapped in dollar signs. Zoho emits the required RFC 8058 headers for marketing campaigns; if you use Zoho Mail (the mailbox service) for transactional sends, unsubscribe headers must be added at the SMTP header level in your application code.

$[LI:UNSUBSCRIBE]$

HTML Code for Zoho unsubscribe:

<a href="$[LI:UNSUBSCRIBE]$ ">Unsubscribe from this list.</a>

Flodesk unsubscribe tag

Flodesk targets creators and small businesses with visual-first email design. The unsubscribe URL is exposed via a subscriber camelCase property. Flodesk handles List-Unsubscribe headers automatically; the unsubscribe link is embedded in every default footer and cannot be removed. Flodesk enforces account-wide unsubscribes with no per-segment opt-out granularity.

{{ subscriber.unsubscribeUrl }}

HTML Code for Flodesk unsubscribe:

<a href="{{ subscriber.unsubscribeUrl }}">Unsubscribe from this list.</a>

Mailjet unsubscribe tag

Mailjet serves both marketing and transactional email with SMTP relay and API delivery. The unsubscribe variable adapts to recipient locale by default; use the language-suffixed variant when you need a fixed language regardless of recipient. Mailjet emits RFC 8058 headers automatically for Marketing sends; for API v3 transactional messages set the List-Unsubscribe header explicitly in the message envelope.

[[UNSUB_LINK_LOCALE]] or [[UNSUB_LINK_FR]] (for smtp relay)

HTML Code for Mailjet unsubscribe:

<a href="[[UNSUB_LINK_LOCALE]]">Unsubscribe from this list.</a>

Pardot unsubscribe tag (Salesforce)

Pardot (rebranded Salesforce Marketing Cloud Account Engagement) targets B2B marketing teams inside the Salesforce ecosystem. Unsubscribe handling routes through the Email Preference Center; the {{Unsubscribe}} merge field renders the appropriate link based on the recipient’s account settings. Pardot supports RFC 8058 headers only on accounts configured with a custom tracker domain and TLS certificate.

{{Unsubscribe}}

HTML Code for Pardot unsubscribe:

<a href="{{Unsubscribe}}">Unsubscribe from this list.</a>

Salesforce Marketing Cloud unsubscribe tag

Salesforce Marketing Cloud (formerly ExactTarget) serves enterprise multi-brand marketing programs. The %%profile_center_url%% merge field renders a URL to the Subscriber Profile Center where recipients can manage granular preferences per publication. RFC 8058 one-click headers are supported when the account is configured with a private domain and TLS certificate; the default shared domain does not support one-click.

%%profile_center_url%%

HTML Code for Salesforce Marketing Cloud unsubscribe:

<a href=”%%profile_center_url%%”>Unsubscribe from this list.</a>

Elasticemail unsubscribe tag

{unsubscribe}

HTML Code for Elasticemail unsubscribe:

<a href="{{Unsubscribe}}">Unsubscribe from this list.</a>

Ongage unsubscribe tag

{{unsubscribe}}

HTML Code for Ongage unsubscribe:

<a href="{{unsubscribe}}">Unsubscribe from this list.</a>

Pepipost unsubscribe tag

[UNSUB] or [UNSUBSCRIBEURL]

HTML Code for Pepipost unsubscribe:

<a href="[UNSUB]">Unsubscribe from this list.</a>

Newsman unsubscribe tag

##NEWSMAN:unsubscribe##

HTML Code for Newsman unsubscribe:

<a href="##NEWSMAN:unsubscribe##">Unsubscribe from this list.</a>

Sarbacane unsubscribe tag

{{unsubscribe}}

HTML Code for Sarbacane unsubscribe:

<a href="{{unsubscribe}}">Unsubscribe from this list.</a>

Mail250 unsubscribe tag

[UNSUBSCRIBEURL]

HTML Code for Mail250 unsubscribe:

<a href="[UNSUBSCRIBEURL]">Unsubscribe from this list.</a>

OneSignal unsubscribe tag

[unsubscribe_url]

HTML Code for OneSignal unsubscribe:

<a href="[unsubscribe_url]">Unsubscribe from this list.</a>

WoodPecker unsubscribe tag

{{UNSUBSCRIBE}} 

HTML Code for WoodPecker unsubscribe:

<a href="{{UNSUBSCRIBE}}">Unsubscribe from this list.</a>

Emarsys unsubscribe tag

Emarsys has an embedded unsubscribe tag system. But you can do the following:

List-Unsubscribe: <mailto:list-unsubscribe-stage+2188885_1039207_196YmQy0K@emarsys.net>, <https://list-unsubscribe-stage.eservice.emarsys.com/api/unsubscribe/2483458851456063207196YmQy0K>

Dotmailer unsubscribe tag (formerly dotdigital): embedded

Dotdigital has an embedded unsubscribe tag system

Messagebird unsubscribe tag (formerly SparkPost): embedded

Sparkpost has an embedded unsubscribe system

Hubspot unsubscribe tag: embedded

HubSpot combines CRM, marketing, sales, and service in a single platform; unsubscribe handling is embedded in every marketing email by default. The {{ unsubscribe_link }} and {{ unsubscribe_link_all }} merge tokens let you distinguish per-subscription and account-wide unsubscribes. HubSpot generates RFC 8058 headers automatically for Marketing Hub sends; transactional emails via Marketing Hub also carry the required headers when the subscription type is marked “one-to-one”.

Amazon SES unsubscribe tag

Amazon SES is AWS’s transactional and marketing send service, popular for its low pricing at scale. SES does not inject an unsubscribe link automatically; you build the URL in your application and pass it in the message body. To satisfy Gmail one-click, add the List-Unsubscribe and List-Unsubscribe-Post headers via the SES SendEmail API (or use the built-in Subscription Management feature which handles the headers and hosts the unsubscribe page for you).

https://your-app.com/unsubscribe?token={{ token }}

Add these SES message headers for RFC 8058 compliance:

List-Unsubscribe: <https://your-app.com/unsubscribe?token=abc123>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

Postmark unsubscribe tag

Postmark targets transactional and lifecycle email with a focus on deliverability. Postmark exposes unsubscribe URLs per broadcast list; the merge variable references a specific list, so you can maintain separate suppression pools per product surface. Postmark emits List-Unsubscribe and List-Unsubscribe-Post headers automatically for broadcast messages; for pure transactional (no list attached), add the headers manually via the Message Streams API.

{{{ pm:unsubscribe }}}

HTML Code for Postmark unsubscribe:

<a href="{{{ pm:unsubscribe }}}">Unsubscribe from this list.</a>

Loops unsubscribe tag

Loops.so is a modern email platform for SaaS product marketing, popular with startups shipping their first email programs. Loops uses a Handlebars-style unsubscribe variable; the rendered URL routes to a Loops-hosted preference center where recipients can manage per-audience subscriptions. Loops adds RFC 8058 one-click headers automatically for every send, marketing and transactional alike, and supports mailing group segmentation so subscribers can opt out of one audience without leaving the account.

{{ unsubscribeUrl }}

HTML Code for Loops unsubscribe:

<a href="{{ unsubscribeUrl }}">Unsubscribe from this list.</a>

Resend unsubscribe tag

Resend is a developer-first email API launched in 2023 that has grown rapidly for transactional and product email in the JavaScript ecosystem. Resend supports Broadcast lists with automatic unsubscribe handling; use the {{{RESEND_UNSUBSCRIBE_URL}}} merge tag inside a broadcast to render the recipient’s unsubscribe URL. Resend emits RFC 8058 headers automatically for broadcasts; for transactional messages sent via the plain /emails endpoint, add the List-Unsubscribe headers manually in the send request.

{{{RESEND_UNSUBSCRIBE_URL}}}

HTML Code for Resend unsubscribe:

<a href="{{{RESEND_UNSUBSCRIBE_URL}}}">Unsubscribe from this list.</a>

Bronto unsubscribe tag (formerly Oracle NetSuite)

Bronto email platform closed down on May 31st, 2022

Self-Hosted Email Marketing Applications

Mailwizz unsubscribe tag

Mailwizz has several unsubscribe tags, but the most used ones are:

[UNSUBSCRIBE_URL] (most commonly) OR [DIRECT_UNSUBSCRIBE_URL]

HTML Code for Mailwizz unsubscribe:

<a href="[UNSUBSCRIBE_URL]">Unsubscribe from this list.</a>

Mautic unsubscribe tag

{unsubscribe_url}

HTML Code for Mautic unsubscribe:

<a href="{unsubscribe_url}">Unsubscribe from this list.</a>

Mumara unsubscribe tag

%%unsubscribelink%%

HTML Code for Mumara unsubscribe:

<a href="%%unsubscribelink%%">Unsubscribe from this list.</a>

Sendy unsubscribe tag

[unsubscribe]

HTML Code for Sendy unsubscribe:

<a href="[unsubscribe]">Unsubscribe from this list.</a>

Mailpoet unsubscribe tag

'.$unsubscribeUrl.'

HTML Code for Mailpoet unsubscribe:

<a href="'.$unsubscribeUrl.'">Unsubscribe from this list.</a>

Klaviyo unsubscribe tag

Klaviyo is the dominant e-commerce email and SMS platform, especially strong on Shopify. The unsubscribe tag uses Klaviyo’s custom braced syntax; it renders a URL to a Klaviyo-hosted preference page where recipients can update consent or unsubscribe fully. Klaviyo adds RFC 8058 headers to all marketing sends by default; make sure your sending domain is authenticated with DKIM and DMARC or the headers will be dropped in transit.

{% unsubscribe %}

HTML Code for Klaviyo unsubscribe:

<a href="{% unsubscribe %}">Unsubscribe from this list.</a>

Generate an unsubscribe link and RFC 8058 headers in PHP

Custom PHP implementations need to do three things: generate a signed unsubscribe URL, expose an endpoint that accepts a one-click POST, and inject the correct List-Unsubscribe and List-Unsubscribe-Post headers on outbound messages. The examples below use HMAC-SHA256 rather than MD5 (which is unsuitable for token authentication in 2026) and cover the full flow.

1. Generate a signed unsubscribe URL:

<?
$user_id   = (int) $user['id'];
$secret    = getenv('UNSUBSCRIBE_SECRET'); // 32+ random bytes
$signature = hash_hmac('sha256', (string) $user_id, $secret);
$link      = "https://example.com/unsubscribe.php?id={$user_id}&sig={$signature}";
echo '<a href="' . htmlspecialchars($link, ENT_QUOTES, 'UTF-8') . '">Unsubscribe</a>';['id']&validation_hash="['id'].$SECRET_STRING)
<a href="<?=$link?>">Unsubscribe</a>

After that, you can proceed with script processing:

function unsubscribe() {

    ['id'] . $SECRET_STRING );

    if( $_GET['validation_hash'] != $expected )
        

    ['id']);
}

RFC 8058 and the List-Unsubscribe header

A visible unsubscribe link in the email footer satisfies CAN-SPAM. But since February 2024, Gmail and Yahoo require an additional layer of compliance for high-volume senders: one-click unsubscribe via HTTP headers, standardized in RFC 8058. This is what actually powers the “Unsubscribe” button that Gmail shows at the top of promotional emails, before the user even opens the message.

The three headers that matter

• List-Unsubscribe (RFC 2369): provides one or more mechanisms to unsubscribe (mailto or HTTPS URL). Present since 1998.
• List-Unsubscribe-Post (RFC 8058): signals that the HTTPS endpoint accepts one-click POST requests. This is the critical addition for Gmail and Yahoo compliance.
• List-Unsubscribe (mailto:): fallback mechanism for enterprise mail clients (Outlook, Thunderbird).

What a compliant header set looks like

List-Unsubscribe: <https://example.com/unsubscribe?u=abc123>, <mailto:unsub@example.com?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

When these headers are present, Gmail shows a native “Unsubscribe” link next to the sender name. Clicking it triggers a POST request to the HTTPS URL. Your server must respond with a 2xx status and process the unsubscribe immediately: no confirmation page, no login flow.

Which platforms handle RFC 8058 automatically

Most modern SaaS platforms generate the RFC 8058 headers automatically. You do not need to configure anything: Mailchimp, HubSpot, Klaviyo, Brevo, ActiveCampaign, SendGrid, Mailgun, Postmark, Amazon SES. Self-hosted platforms (Mailwizz, Mautic, Mailpoet) may require explicit configuration in your MTA or plugin settings. Custom PHP implementations must add these headers manually in the SMTP message construction step.

How to test your unsubscribe link actually works

Every unsubscribe link should be tested before your first send at scale. Here’s the 3-step process that covers both the visible link and the RFC 8058 header:

Step 1: Send-to-self and click

• Send a test campaign to an email address you control
• Open the email and click the unsubscribe link in the footer
• Verify the landing page loads (HTTP 200) and displays a confirmation message
• Check your platform’s suppression list; the address should appear within seconds

Step 2: Verify the List-Unsubscribe header

View the email source (in Gmail: Show original) and look for the header. It should look like:

List-Unsubscribe: <https://your-domain.com/unsub?token=...>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

If List-Unsubscribe-Post is missing, one-click unsubscribe won’t work in Gmail; a critical gap for any sender above 5,000 daily emails to Gmail addresses.

Step 3: Test the endpoint accepts POST

Copy the URL from the List-Unsubscribe header and simulate the POST request:

curl -X POST -d "List-Unsubscribe=One-Click" https://your-domain.com/unsub?token=abc123

Expected response: HTTP 200 or 202. If you get 405 Method Not Allowed, your endpoint is not RFC 8058 compliant; this is the #1 real-world implementation failure. Fix it by allowing POST on the unsubscribe route.

Common failures to watch for

• Endpoint blocks Googlebot or Yahoo user agents: Gmail and Yahoo pre-validate your endpoint. If your firewall or bot detection blocks them, they will drop the one-click option silently.
• Redirect chains on the unsubscribe URL: the endpoint must respond directly to POST. Redirects break the one-click flow.
• HTTPS certificate issues: expired or self-signed certificates fail silently. Use Let’s Encrypt or your ESP’s default HTTPS endpoint.
• Token-based URLs that require session state: one-click does not carry cookies. All authentication must be in the URL token itself.

Global compliance quick reference

Unsubscribe link requirements vary by jurisdiction. This table summarizes the key rules for the 5 biggest email markets:

Beyond legal requirements, technical compliance with Gmail and Yahoo bulk sender rules (February 2024) applies globally to any sender crossing 5,000 daily emails to those providers. Full details in the email unsubscribe laws guide.

Complementary platforms: quick unsubscribe tag reference

The table below covers the additional platforms not detailed in the sections above, sorted alphabetically. Click any platform name for its full setup guide with platform-specific UI paths, one-click compliance status, and testing steps.

Unsubscribe link FAQ

Do I have to include an unsubscribe link in every email?

Yes for any commercial marketing email, required under CAN-SPAM, GDPR, CASL, LGPD, and the Spam Act 2003. Transactional emails (order confirmations, password resets) are exempt from CAN-SPAM but not from GDPR; you must still allow opt-out of marketing content mixed into transactional messages.

What’s the difference between an unsubscribe link and an unsubscribe tag?

A tag is the merge variable you place in your template (e.g., *|UNSUB|*, {{ unsubscribe_link }}). A link is the rendered URL that appears in the delivered email. You configure the tag; the platform generates the link at send time.

How do I make my unsubscribe link one-click compliant with Gmail?

Your emails must include both the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058), and your endpoint must accept POST requests without authentication cookies. Most SaaS platforms (Mailchimp, HubSpot, SendGrid, Klaviyo) generate these headers automatically. Self-hosted platforms may require configuration.

Can I customize the unsubscribe landing page?

Most platforms allow customization: brand colors, logo, “Are you sure?” prompts, preference center options. However, the actual unsubscribe action must complete within the same session: you cannot require multiple clicks, account creation, or CAPTCHA challenges.

What happens when someone unsubscribes?

Their address is added to your platform’s suppression list. All future sends to that address are automatically blocked. Some platforms allow per-list unsubscribes (via preference centers); others enforce account-wide global suppression. See our suppression lists guide for cross-ESP portability details.

How often should I test my unsubscribe link?

At minimum, before every new campaign, after any change to your unsubscribe endpoint code, and monthly for high-volume programs (5K+ daily). Automated monitoring via ESP webhooks catches suppression failures fast.

Do all platforms in this guide support RFC 8058 one-click?

Most major SaaS platforms do automatically (Mailchimp, HubSpot, Klaviyo, ActiveCampaign, Brevo, ConvertKit, SendGrid, Mailgun, Postmark, Amazon SES). Self-hosted platforms (Mailwizz, Mautic, Postal, Mailpoet) support it with configuration. Some smaller regional platforms do not. Check the individual platform guides linked in the sections above for details.

Wrapping Up

This guide has covered the exact unsubscribe link and tag syntax for every documented email marketing platform, from industry leaders like Mailchimp, HubSpot, Klaviyo, SendGrid, and Mailgun, to self-hosted solutions like Mailwizz and Mautic. Shipping a correctly-rendering link is only step one; the link must also be RFC 8058 one-click compliant to survive Gmail and Yahoo’s 2024 bulk sender rules.

Three checks before every send: (1) is the tag syntax right for the platform? (see the tag reference sections above); (2) does the rendered link work when clicked? (send-to-self test); (3) does the email carry the List-Unsubscribe-Post header for one-click? (view source in Gmail, testing procedure in the section above). Missing any of the three degrades sender reputation faster than most other deliverability failures.

Bookmark this page as your unsubscribe reference across all platforms. For deeper dives, explore the individual platform guides linked throughout each tag section; each covers the platform-specific UI paths, common gotchas, and testing steps. See also RFC 8058, suppression lists best practices, and global unsubscribe laws for the full compliance picture.

Stay connected via Google News

Follow us for the latest updates and guides.

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.

Next

Email Deliverability 101: How to Reach the Inbox in 2026 (Complete Guide)