Ongage is an email marketing operations platform serving mid-market and enterprise senders with campaign management, multi-vendor SMTP routing, and deliverability tooling on top of any underlying SMTP provider (SendGrid, Amazon SES, SparkPost). The unsubscribe mechanism uses the [ongage_unsubscribe_link] merge tag placed in email campaigns, and Ongage emits RFC 8058 headers automatically for authenticated sending domains. Suppression is tracked at the recipient level with cross-vendor enforcement. This guide covers the tag, the multi-vendor model, and how to verify the setup end to end.
Ongage unsubscribe link
| Tag syntax | [ongage_unsubscribe_link] |
| Placement | Manual placement in campaign templates |
| Scope | Recipient-level opt-out with cross-vendor suppression |
| Config path | Admin > Templates > Footer configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Ongage
Place the merge tag exactly as shown below in the email template. Ongage replaces it at send time with a signed URL scoped to the recipient and campaign.
[ongage_unsubscribe_link]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[ongage_unsubscribe_link]">Unsubscribe from this list</a>Manual placement in campaign templates
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.
Ongage multi-vendor SMTP routing means underlying delivery flows through customer-selected SMTP vendors (SendGrid, Amazon SES, SparkPost, others). RFC 8058 header injection happens at the Ongage application layer before handoff to the SMTP vendor. Cross-vendor suppression list is critical to prevent re-sending to opted-out recipients when switching SMTP vendors or running multi-vendor campaigns.
Testing your Ongage unsubscribe link
- Send a test message to a controlled Gmail address you own via the Ongage 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 Ongage unsubscribe link (step by step)
- Open your campaign template in the Ongage admin.
- Add or edit a text block in the footer.
- Insert the merge tag
[ongage_unsubscribe_link]. - Wrap it in an anchor:
<a href="[ongage_unsubscribe_link]">Unsubscribe</a>. - Configure the sender identity under Admin > Templates > Footer configuration.
- Send a test to a seed address and verify the rendered link routes to the Ongage-hosted preference page.
Multi-vendor SMTP routing
Ongage multi-vendor SMTP routing means underlying delivery flows through customer-selected SMTP vendors (SendGrid, Amazon SES, SparkPost, others). RFC 8058 header injection happens at the Ongage application layer before handoff to the SMTP vendor. Cross-vendor suppression list is critical to prevent re-sending to opted-out recipients when switching SMTP vendors or running multi-vendor campaigns.
RFC 8058 one-click headers
Ongage 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 at the Ongage layer on every marketing send from domains authenticated under Admin > Templates. SPF and DKIM records must be verified on the sending domain, and the underlying SMTP vendor must be configured to preserve headers set by Ongage.
Deliverability tooling and campaign management
Ongage deliverability tooling provides bounce classification, sender reputation monitoring, inbox placement testing, and IP warm-up guidance across the customer-selected SMTP vendors. Campaign management adds segmentation, personalization, and A/B testing on top of vendor delivery. Enterprise use cases benefit from switching SMTP vendors without changing campaign workflows.
Frequently Asked Questions
What is the Ongage unsubscribe tag?
The merge tag is [ongage_unsubscribe_link]. Ongage replaces it at send time with a signed URL scoped to the recipient.
Which SMTP vendors does Ongage support?
SendGrid, Amazon SES, SparkPost, and others. Ongage handles campaign management on top; underlying delivery flows through the customer-selected vendor.
Does Ongage support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Ongage injects List-Unsubscribe and List-Unsubscribe-Post headers before handoff to the SMTP vendor.
Does cross-vendor suppression work?
Yes. Suppression tracks at the Ongage layer and applies across all connected SMTP vendors. Prevents re-sending to opted-out recipients when switching vendors.
How does Ongage compare to MessageGears?
Both target enterprise marketing operations. Ongage emphasizes multi-vendor SMTP routing on top of any provider. MessageGears focuses on on-premises data-driven sending. Vendor choice depends on delivery architecture 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.
