Goolara Symphonie is an enterprise email marketing and marketing automation platform serving US mid-market and enterprise B2C brands with advanced segmentation, dynamic content, and on-premises deployment options. The unsubscribe mechanism uses the ##unsubscribe## merge tag auto-injected into every campaign footer, and Symphonie emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with enterprise audit trails. This guide covers the tag, the cloud/on-prem model, and how to verify the setup end to end.
Goolara Symphonie unsubscribe link
| Tag syntax | ##unsubscribe## |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with enterprise audit trails |
| Config path | Admin > Sender profiles > Footer configuration |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Goolara Symphonie
Place the merge tag exactly as shown below in the email template. Goolara Symphonie 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.
Goolara Symphonie enterprise deployment supports both cloud and on-premises installations, giving customers a choice between SaaS convenience and full data ownership. On-premises deployments require sysadmin management similar to Interspire, MailWizz, and Octeth. Enterprise audit trails capture every consent event with timestamp and IP metadata for regulatory review, matching mid-market and enterprise compliance expectations.
Testing your Goolara Symphonie unsubscribe link
- Send a test message to a controlled Gmail address you own via the Goolara Symphonie 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 Goolara Symphonie unsubscribe link (step by step)
Symphonie 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 Symphonie editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
##unsubscribe##. Symphonie 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 Admin > Sender profiles > Footer configuration.
- Send a test to a seed address and verify the rendered link routes to the Symphonie-hosted preference page.
Cloud vs on-premises deployment
Goolara Symphonie enterprise deployment supports both cloud and on-premises installations, giving customers a choice between SaaS convenience and full data ownership. On-premises deployments require sysadmin management similar to Interspire, MailWizz, and Octeth. Enterprise audit trails capture every consent event with timestamp and IP metadata for regulatory review, matching mid-market and enterprise compliance expectations. Cloud deployments benefit from managed infrastructure while retaining enterprise features.
RFC 8058 one-click headers
Goolara Symphonie 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 Admin > Sender profiles. SPF and DKIM records must be verified. On-premises deployments require sysadmins to configure MTA-side header injection matching cloud defaults.
Advanced segmentation and dynamic content
Symphonie advanced segmentation combines behavioral data, purchase history, and demographic filters to route campaigns to precisely defined audiences. Dynamic content blocks render per-recipient based on segment membership, letting enterprise brands run one campaign asset with N personalization variants. Opt-out events at the contact level suppress the contact across all segments automatically, preserving consent state across campaign programs.
Frequently Asked Questions
What is the Goolara Symphonie unsubscribe tag?
The merge tag is ##unsubscribe##. Symphonie replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="##unsubscribe##">Unsubscribe</a>.
Does Goolara Symphonie support on-premises deployment?
Yes. Symphonie supports both cloud and on-premises installations. On-premises deployments require sysadmin management for server, MTA, backup, and TLS. Cloud deployments benefit from managed infrastructure.
Does Symphonie support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Symphonie injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Admin > Sender profiles.
Does Symphonie support enterprise audit trails?
Yes. Every consent event captures timestamp and IP metadata for regulatory review. Enterprise audit trails match mid-market and enterprise compliance expectations for regulated industries (financial services, healthcare).
How does Goolara Symphonie compare to Salesforce Marketing Cloud?
Both target US enterprise B2C. Symphonie offers cloud and on-premises deployment; SFMC is cloud-only. SFMC has broader Salesforce ecosystem integration; Symphonie emphasizes segmentation depth and deployment flexibility.
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.
