Remarkety is an e-commerce marketing automation platform serving Shopify, Magento, WooCommerce, and BigCommerce merchants with revenue-attributed automation flows for abandoned cart, post-purchase, and win-back campaigns. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag auto-injected into every campaign footer, and Remarkety emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the customer level with e-commerce store sync. This guide covers the tag, the multi-store e-commerce integration model, and how to verify the setup end to end.
Remarkety unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Customer-level opt-out with store sync |
| Config path | Settings > Email > Sender configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Remarkety
Place the merge tag exactly as shown below in the email template. Remarkety 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
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.
Remarkety e-commerce store integration syncs opt-out state to the store customer record only when the two-way sync toggle is enabled. Without it, a Remarkety unsubscribe leaves the Shopify or Magento customer record marked as opted-in, corrupting downstream integrations reading consent from the store. Enable two-way sync during initial integration setup.
Testing your Remarkety unsubscribe link
- Send a test message to a controlled Gmail address you own via the Remarkety 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 Remarkety unsubscribe link (step by step)
Remarkety drag-and-drop templates include the unsubscribe link in the default footer, but custom HTML templates and flow-triggered emails may require the tag inserted manually.
- Open your campaign or flow email in the Remarkety editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{{unsubscribe_url}}. Remarkety replaces it at send time with a signed URL scoped to the customer. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - Configure the sending domain under Settings > Email > Sender configuration.
- Send a test to a seed address and verify the rendered link routes to the Remarkety-hosted preference page.
Multi-store e-commerce integration and opt-out sync
Remarkety e-commerce store integration syncs opt-out state to the Shopify, Magento, WooCommerce, or BigCommerce customer record only when the two-way sync toggle is enabled. Without it, a Remarkety unsubscribe leaves the store customer record marked as opted-in, corrupting downstream integrations reading consent from the store (loyalty programs, customer service tools, personalization engines). Enable two-way sync during initial integration setup. Multi-store accounts running one Remarkety account across two stores need per-store sync configuration to keep opt-out state consistent across brands.
RFC 8058 one-click headers
Remarkety 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 Settings > Email > Sender configuration. SPF and DKIM records must be verified. Multi-store accounts sending from distinct brand domains need per-domain authentication verification to keep one-click compliance uniform across the store portfolio.
Revenue attribution and win-back flow enforcement
Remarkety revenue attribution tracks per-email, per-flow, and per-customer transaction outcomes, letting merchants measure the incremental revenue from each marketing send. Opt-out events update the revenue attribution model: a high-LTV customer who opts out reduces expected future revenue in forecasts, informing win-back strategy. Flow-based automations respect the opt-out flag at each send step and can be configured with exit criteria that route unsubscribed customers to alternative paths (SMS opt-in prompts, cross-channel re-engagement, direct mail).
Frequently Asked Questions
What is the Remarkety unsubscribe tag?
The merge tag is {{unsubscribe_url}}. Remarkety replaces it at send time with a signed URL scoped to the customer. Use it inside an anchor: <a href="{{unsubscribe_url}}">Unsubscribe</a>.
Which e-commerce platforms does Remarkety support?
Shopify, Magento, WooCommerce, and BigCommerce with native integrations. Each integration supports two-way sync of opt-out state to keep consent consistent between Remarkety and the store customer record.
Does Remarkety support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Remarkety injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Settings > Email > Sender configuration.
Do abandoned cart flows honor Remarkety unsubscribes?
Yes. All Remarkety flows respect the marketing opt-out flag: an unsubscribed customer does not receive cart recovery emails, only transactional order confirmations that bypass marketing consent as required by e-commerce transactional exemptions.
Can Remarkety multi-store accounts share suppression?
By default no, per-store suppression is isolated to keep brand-level opt-out pools separate. Configure cross-store sync only when the brands should share opt-out state (typically same-parent multi-brand retailers with unified customer databases).
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.
