Intercom is a customer messaging and support platform serving SaaS and e-commerce companies with in-app messaging, email campaigns, chatbot automation, and help desk integration. The unsubscribe mechanism uses the {{ unsubscribe_url }} merge tag placed manually in email campaigns, and Intercom emits RFC 8058 headers automatically on outbound email campaigns from authenticated sending domains. Consent is tracked at the user level with granular subscription topic preferences. This guide covers the tag, the subscription topic model, and how to verify the setup end to end.
Intercom unsubscribe link
| Tag syntax | {{ unsubscribe_url }} |
| Placement | Manual placement in email campaigns |
| Scope | User-level opt-out with subscription topic granularity |
| Config path | Settings > Channels > Email > Subscription topics |
| RFC 8058 one-click | Yes, automatic for outbound email campaigns from authenticated domains |
How to add the unsubscribe tag in Intercom
Place the merge tag exactly as shown below in the email template. Intercom 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 outbound email campaigns from authenticated 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.
Intercom subscription topic granularity lets users opt out of specific message categories (product updates, marketing, transactional) rather than all Intercom communications. This differs from binary marketing opt-in ESPs. Configure subscription topics carefully at account setup to match the message categories your team actually sends. In-app messages and chatbot conversations bypass email unsubscribe per Intercom s in-product communication exemption.
Testing your Intercom unsubscribe link
- Send a test message to a controlled Gmail address you own via the Intercom 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 Intercom unsubscribe link (step by step)
Intercom 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 Intercom > Outbound > Series or Newsletters.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{{ unsubscribe_url }}. Intercom replaces it at send time with a signed URL scoped to the user. - Wrap it in an anchor:
<a href="{{ unsubscribe_url }}">Unsubscribe</a>. - Configure subscription topics under Settings > Channels > Email > Subscription topics.
- Send a test to a seed address and verify the rendered link routes to the Intercom-hosted subscription preferences page.
Subscription topics and granular consent
Intercom subscription topic granularity lets users opt out of specific message categories (product updates, marketing, transactional) rather than all Intercom communications. This differs from binary marketing opt-in ESPs. Configure subscription topics carefully at account setup to match the message categories your team actually sends. Users can select or deselect individual topics from the Intercom-hosted subscription preferences page, giving fine control over which communications continue. In-app messages and chatbot conversations bypass email unsubscribe per Intercom s in-product communication exemption.
RFC 8058 one-click headers
Intercom 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 outbound email campaign from domains authenticated under Settings > Channels > Email. SPF and DKIM records must be verified. One-click unsubscribe defaults to opting the user out of the current campaign s subscription topic, not all topics, matching Intercom s granular consent model.
Chatbot automation and in-product exemption
Intercom chatbot conversations, in-app messages, and help desk replies bypass email unsubscribe per the in-product communication exemption. Users opted out of marketing email still receive in-product messages triggered by their app usage. Configure Outbound message routing carefully to respect the intended communication channel: an in-product-only campaign should not fall back to email for opted-out users, and an email campaign should not accidentally trigger in-app messages for users who prefer email-only.
Frequently Asked Questions
What is the Intercom unsubscribe tag?
The merge tag is {{ unsubscribe_url }}. Intercom replaces it at send time with a signed URL scoped to the user. Use it inside an anchor: <a href="{{ unsubscribe_url }}">Unsubscribe</a>.
What are Intercom subscription topics?
Granular message categories (product updates, marketing, transactional) that users can opt in or out of individually via the Intercom-hosted subscription preferences page. Differs from binary marketing opt-in ESPs.
Does Intercom support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. One-click defaults to opting the user out of the current campaign s subscription topic, not all topics, matching Intercom s granular consent model.
Do in-app messages bypass Intercom unsubscribe?
Yes per the in-product communication exemption. Users opted out of marketing email still receive in-app messages triggered by their app usage. Chatbot conversations and help desk replies also bypass email unsubscribe.
How does Intercom differ from HubSpot for SaaS?
Intercom focuses on in-app messaging and support with email campaigns as a secondary channel. HubSpot focuses on marketing automation and CRM with in-app messaging as a secondary. SaaS teams often use both: Intercom for in-app/support, HubSpot for marketing outreach.
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.
