Encharge is a SaaS marketing automation platform serving B2B SaaS companies with behavioral email marketing, product-driven segmentation, and lifecycle automation triggered by product usage events. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag placed in email templates, and Encharge emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with product event enrichment. This guide covers the tag, the SaaS automation model, and how to verify the setup end to end.
Encharge unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with product event tracking |
| Config path | Settings > Sender profiles > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Encharge
Place the merge tag exactly as shown below in the email template. Encharge 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.
Encharge SaaS-focused design uses product event data (feature usage, activation milestones, subscription state) to drive email automation. Product usage-based emails may qualify as transactional or legitimate interest under B2B GDPR interpretation. Configure per-campaign classification to distinguish transactional onboarding (bypasses opt-out) from promotional upsells (respects opt-out).
Testing your Encharge unsubscribe link
- Send a test message to a controlled Gmail address you own via the Encharge 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 Encharge unsubscribe link (step by step)
- Open your campaign in the Encharge editor.
- Add or edit a text block in the footer.
- Insert the merge tag
{{unsubscribe_url}}. - Wrap it in an anchor:
<a href="{{unsubscribe_url}}">Unsubscribe</a>. - Configure the sender identity under Settings > Sender profiles > Footer.
- Send a test to a seed address and verify the rendered link routes to the Encharge-hosted preference page.
SaaS product event automation
Encharge SaaS-focused design uses product event data (feature usage, activation milestones, subscription state) to drive email automation. Product usage-based emails may qualify as transactional or legitimate interest under B2B GDPR interpretation. Configure per-campaign classification to distinguish transactional onboarding (bypasses opt-out) from promotional upsells (respects opt-out). Behavioral segmentation excludes opted-out contacts from marketing while lifecycle communications continue.
RFC 8058 one-click headers
Encharge 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 > Sender profiles. SPF and DKIM records must be verified.
Behavioral segmentation and lifecycle flows
Encharge behavioral segmentation lets SaaS teams target based on product engagement, subscription tier, feature adoption, and account lifecycle stage. Flows trigger automatically on product events (signup, activation, feature use, cancellation risk). Integration with common SaaS tools (Segment, Stripe, HubSpot, Intercom) feeds event data into automation without engineering effort.
Frequently Asked Questions
What is the Encharge unsubscribe tag?
The merge tag is {{unsubscribe_url}}. Encharge replaces it at send time with a signed URL scoped to the contact.
Do product event emails need unsubscribe links?
Transactional lifecycle emails (activation, onboarding) qualify for exemption. Promotional upsells and marketing broadcasts respect opt-out and include unsubscribe.
Does Encharge support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Encharge injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send.
Does Encharge integrate with Segment or Stripe?
Yes. Native integrations with Segment (event data), Stripe (subscription state), HubSpot (CRM), and Intercom (support conversations) feed data into automation flows.
How does Encharge compare to Customer.io or Vero?
All three target behavioral SaaS email. Encharge emphasizes marketing automation depth. Customer.io focuses on event-driven messaging. Vero targets API-first workflow. Vendor choice depends on team preferences.
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.
