Mailmodo is an Indian email platform focused on AMP for Email support, letting marketers embed interactive forms, carousels, and dynamic content directly in the inbox. Popular with SaaS teams for onboarding sequences and product marketing. The unsubscribe mechanism uses a merge variable auto-injected into every campaign footer, and Mailmodo emits RFC 8058 headers automatically. Consent is tracked account-wide with a preference center option for topic-level opt-out. This guide covers the tag, the AMP-specific unsubscribe considerations, and the deliverability best practices for interactive email.
Mailmodo unsubscribe link
| Tag syntax | {{{unsubscribe_url}}} |
| Placement | Auto-embedded in every campaign footer (AMP and HTML fallback) |
| Scope | Account-wide contact status with topic-level preference center |
| Config path | Settings > Sender identities > Footer |
| RFC 8058 one-click | Yes, automatic for marketing campaigns |
How to add the unsubscribe tag in Mailmodo
Place the merge tag exactly as shown below in the email template. Mailmodo 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>Auto-embedded in every campaign footer (AMP and HTML fallback)
Yes, automatic for marketing campaigns 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.
AMP for Email requires the unsubscribe link to also appear in the HTML fallback, or Gmail rejects the AMP version and falls back silently. Mailmodo templates include both by default, but hand-edited templates need to declare the unsubscribe tag in both the AMP script and the HTML mime part.
Testing your Mailmodo unsubscribe link
- Send a test message to a controlled Gmail address you own via the Mailmodo 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 →
Mailmodo and AMP email context
Mailmodo positions itself around AMP for Email, which lets recipients interact with content (fill forms, RSVP, browse products) directly inside the email client without clicking through to a web page. Its unsubscribe mechanism uses the {{unsubscribe_link}} merge tag in both AMP and fallback HTML versions of each campaign. The AMP version can technically support an in-email unsubscribe form, but for maximum compatibility Mailmodo defaults to a standard link routing to a hosted preference page.
AMP fallback and unsubscribe coverage
Every AMP email requires an HTML fallback for mail clients that do not support AMP (currently Gmail, Yahoo, and Mail.ru support AMP; Outlook, Apple Mail, and most others render the HTML fallback). Mailmodo ensures the unsubscribe link is present in both versions, so opt-out is always possible regardless of which version the recipient sees. Custom AMP templates imported to Mailmodo must contain the {{unsubscribe_link}} tag in both AMP and HTML sections.
RFC 8058 headers
Mailmodo adds RFC 8058 one-click unsubscribe headers on all marketing sends from authenticated domains. Domain authentication requires configuring SPF and DKIM in the Sending Domains section, which Mailmodo verifies before enabling one-click header injection. Because AMP for Email requires strict DKIM authentication regardless (Gmail refuses to render AMP without valid DKIM), most Mailmodo accounts have DKIM configured from the start, so one-click headers are typically active by the time first campaigns launch.
Common pitfalls with AMP campaigns
Two AMP-specific issues affect the unsubscribe flow. First, AMP campaigns require the sender domain to be whitelisted by Google (for Gmail AMP delivery), a manual approval process. Without whitelisting, AMP content is downgraded to HTML fallback silently, which is fine but means AMP-specific features do not appear. Second, some AMP components block the standard link tracking Mailmodo uses to record unsubscribe events. The Mailmodo AMP validator flags templates that would break tracking; running the validator before send catches most issues.
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.
