Iterable is a modern enterprise cross-channel marketing platform popular with growth-stage B2C brands, streaming services, and e-commerce operators that need email, SMS, mobile push, and in-app messaging from a single data model. The unsubscribe mechanism uses the Handlebars-style merge tag in email templates, and Iterable emits RFC 8058 one-click headers automatically once the sending domain is authenticated. Message channels are tracked separately: email opt-out does not stop SMS or push. This guide covers the tag, the channel-split consent model, and the workflow interaction with unsubscribed users.
Iterable unsubscribe link
| Tag syntax | {{unsubscribeUrl}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-channel consent (email, SMS, push tracked separately) |
| Config path | Settings > Project settings > Unsubscribe options |
| RFC 8058 one-click | Yes, automatic for marketing sends with authenticated domain |
How to add the unsubscribe tag in Iterable
Place the merge tag exactly as shown below in the email template. Iterable replaces it at send time with a signed URL scoped to the recipient and campaign.
{{unsubscribeUrl}}For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="{{unsubscribeUrl}}">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Yes, automatic for marketing sends with authenticated domain 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.
Iterable Message Channels (email, SMS, push) track consent independently. A user unsubscribing from marketing email still receives promo push and SMS unless they also opt out of those channels. Add a channel-level preference center linking from the email footer, or use a single "unsubscribe from all channels" workflow action.
Testing your Iterable unsubscribe link
- Send a test message to a controlled Gmail address you own via the Iterable 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 →
The Iterable message channel model
Iterable organizes marketing communications into message channels (Email, Push, SMS, WhatsApp) and message types within each channel (Newsletter, Product Announcement, Weekly Digest). Users can opt out of specific message types independently, or opt out of an entire channel. This granular model gives Iterable users fine control: a subscriber can keep receiving order confirmations by email while opting out of Product Announcements. Every marketing campaign is associated with a message type, and opted-out users are automatically excluded.
The Handlebars unsubscribe tag
Iterable templates use the {{unsubscribeUrl}} Handlebars variable to render the unsubscribe URL. For hosted preference centers, {{hostedUnsubscribeUrl}} generates a URL to the full preference page. Custom HTML campaigns imported to Iterable must contain at least one of these variables, and Iterable refuses to send campaigns without an opt-out mechanism. Enterprise deployments often use the preference center URL, which lets subscribers manage all message types in one place.
RFC 8058 headers
Iterable implements RFC 8058 one-click unsubscribe headers on all authenticated sending domains. The List-Unsubscribe and List-Unsubscribe-Post headers are added automatically to marketing sends. Iterable customer success guides enterprise deployments through DKIM and SPF authentication as part of onboarding, so most Iterable accounts satisfy the Google and Yahoo February 2024 bulk-sender requirements from launch. Transactional message types (Order Confirmation, Password Reset) can be flagged as transactional and skip unsubscribe headers.
Cross-channel opt-out coordination
A user who unsubscribes from an email message type does not automatically opt out of the same message type on other channels (Push, SMS). Iterable exposes cross-channel preference synchronization as an optional configuration: turning it on means an email opt-out cascades to push and SMS for the equivalent message type. This is preferred for consumer brands where users expect a single opt-out to affect all channels; enterprise B2B users often prefer independent per-channel control. The configuration lives under Project Settings and applies account-wide.
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.
