Piano is a subscription commerce and audience management platform serving publishers, media, and content brands with paywall, personalization, and newsletter management. The unsubscribe mechanism uses the {{unsubscribe_url}} merge tag placed in email campaigns, and Piano emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the user profile level with subscription state unified across paywall and newsletter. This guide covers the tag, the publisher subscription model, and how to verify the setup end to end.
piano.io unsubscribe link
| Tag syntax | {{unsubscribe_url}} |
| Placement | Auto-embedded in every campaign footer |
| Scope | User profile-level with subscription unification |
| Config path | Composer > Templates > Email footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in piano.io
Place the merge tag exactly as shown below in the email template. piano.io 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.
Piano subscription commerce origin means user profile unifies paywall access state and newsletter subscription state. An email newsletter opt-out does not cancel a paid subscription (transactional exemption applies to subscription lifecycle emails). Configure per-newsletter list scoping so opt-out from marketing newsletters does not suppress transactional subscription notifications required for billing and account management.
Testing your piano.io unsubscribe link
- Send a test message to a controlled Gmail address you own via the piano.io 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 Piano unsubscribe link (step by step)
- Open your email campaign in the Piano Composer 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 Composer > Templates > Email footer.
- Send a test to a seed address and verify the rendered link routes to the Piano-hosted preference page.
Publisher subscription model and transactional exemption
Piano subscription commerce origin means user profile unifies paywall access state and newsletter subscription state. An email newsletter opt-out does not cancel a paid subscription (transactional exemption applies to subscription lifecycle emails). Configure per-newsletter list scoping so opt-out from marketing newsletters does not suppress transactional subscription notifications required for billing and account management. Content brands running multiple newsletters (daily, weekly, thematic) benefit from per-newsletter granularity.
RFC 8058 one-click headers
Piano 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 Composer > Templates. Publisher domains often run high send volume, making RFC 8058 compliance critical for inbox placement.
Paywall personalization and audience segmentation
Piano paywall personalization and audience segmentation route content and offers based on subscription tier, reading behavior, and engagement scoring. Opt-outs at the marketing newsletter level do not affect paywall access or subscription-related transactional sends. Publisher use cases benefit from distinguishing content newsletters (respect opt-out) from subscription lifecycle emails (transactional exemption applies).
Frequently Asked Questions
What is the Piano unsubscribe tag?
The merge tag is {{unsubscribe_url}}. Piano replaces it at send time with a signed URL scoped to the user profile.
Does newsletter opt-out cancel a Piano paid subscription?
No. Subscription lifecycle emails qualify for transactional exemption and continue for billing and account management. Cancellation happens through the subscription management flow.
Does Piano support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. Piano injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send.
Can Piano handle multiple newsletters per publisher?
Yes. Per-newsletter list scoping lets publishers run daily, weekly, and thematic newsletters with separate opt-out state so users can adjust subscriptions granularly.
How does Piano compare to Sailthru for publishers?
Both target publishers and media. Piano emphasizes paywall+subscription commerce integration. Sailthru focuses on content-driven personalization. Vendor choice depends on subscription monetization vs personalization priorities.
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.
