Maropost is a Canadian multi-channel commerce and marketing platform serving mid-market and enterprise B2C brands with email, SMS, mobile app messaging, and e-commerce integration. The unsubscribe mechanism uses the %UNSUBSCRIBE% merge tag auto-injected into every campaign footer, and Maropost emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with cross-channel subscription state and CASL enforcement. This guide covers the tag, the commerce integration model, and how to verify the setup end to end.
Maropost unsubscribe link
| Tag syntax | %UNSUBSCRIBE% |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with cross-channel state |
| Config path | Marketing Cloud > Settings > Sender identity |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Maropost
Place the merge tag exactly as shown below in the email template. Maropost replaces it at send time with a signed URL scoped to the recipient and campaign.
%UNSUBSCRIBE%For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="%UNSUBSCRIBE%">Unsubscribe from this list</a>Auto-embedded in every campaign footer
Yes, automatic for authenticated sending 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.
Maropost multi-channel commerce platform unifies consent state across email, SMS, and mobile app channels. Configure per-channel scoping carefully: an email opt-out can propagate to SMS and push suppression if cross-channel enforcement is enabled. Canadian data residency options align with CASL and PIPEDA expectations. Maropost also owns e-commerce platforms (Neto, Findify), so opt-outs may sync to e-commerce customer records depending on account configuration.
Testing your Maropost unsubscribe link
- Send a test message to a controlled Gmail address you own via the Maropost 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 Maropost unsubscribe link (step by step)
Maropost default templates include the unsubscribe link in the footer, but custom HTML templates require the tag inserted manually.
- Open your campaign or template in the Maropost Marketing Cloud editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
%UNSUBSCRIBE%. Maropost replaces it at send time with a signed URL scoped to the contact. - Wrap it in an anchor:
<a href="%UNSUBSCRIBE%">Unsubscribe</a>. - Configure the sender identity under Marketing Cloud > Settings > Sender identity.
- Send a test to a seed address and verify the rendered link routes to the Maropost-hosted preference page.
Multi-channel commerce platform and cross-channel consent
Maropost multi-channel commerce platform unifies consent state across email, SMS, and mobile app channels. Configure per-channel scoping carefully: an email opt-out can propagate to SMS and push suppression if cross-channel enforcement is enabled. Canadian data residency options align with CASL and PIPEDA expectations. Maropost also owns e-commerce platforms (Neto, Findify), so opt-outs may sync to e-commerce customer records depending on account configuration. Configure integration scope at setup to match business expectations.
RFC 8058 one-click headers
Maropost 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 marketing send from domains authenticated under Marketing Cloud > Settings > Sender identity. SPF and DKIM records must be verified. Canadian data residency defaults align with CASL enforcement expectations for domestic senders.
CASL enforcement and Canadian regulatory context
Maropost CASL enforcement matches Canadian regulatory expectations with express/implied consent tracking at the contact level. Contacts approaching implied consent 2-year expiration should be converted to express consent via re-permission campaigns. Analogous to Envoke and AdMail.net Canadian regulatory-first patterns. CASL fines can reach CAD 10 million per violation for corporate senders, making platform-level enforcement particularly valuable for Canadian mid-market and enterprise B2C brands.
Frequently Asked Questions
What is the Maropost unsubscribe tag?
The merge tag is %UNSUBSCRIBE%. Maropost replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="%UNSUBSCRIBE%">Unsubscribe</a>.
Does Maropost unify consent across channels?
Yes when cross-channel enforcement is configured. Multi-channel platform (email, SMS, mobile app) can propagate opt-outs across channels. Configure per-channel scoping to match TCPA, CASL, and GDPR expectations.
Does Maropost support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Maropost injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Marketing Cloud > Settings > Sender identity.
Do Maropost opt-outs sync to Neto or Findify?
Depending on account configuration. Maropost owns Neto and Findify e-commerce platforms, so opt-outs may sync to e-commerce customer records if the integration is enabled. Configure integration scope at setup.
Is Maropost data hosted in Canada?
Yes as default option. Canadian data residency aligns with CASL and PIPEDA expectations for domestic senders. Regulated industries and public sector customers benefit from Canadian sovereignty over marketing data.
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.
