SimplyCast is a Canadian marketing automation platform serving SMBs and mid-market with email, SMS, voice broadcast, fax, and social media in one unified interface. The unsubscribe mechanism uses the [UnsubscribeLink] merge tag auto-injected into every campaign footer, and SimplyCast emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with Canadian CASL enforcement. This guide covers the tag, the multi-channel CASL model, and how to verify the setup end to end.
SimplyCast unsubscribe link
| Tag syntax | [UnsubscribeLink] |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with Canadian CASL enforcement |
| Config path | Settings > Sender profiles > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in SimplyCast
Place the merge tag exactly as shown below in the email template. SimplyCast replaces it at send time with a signed URL scoped to the recipient and campaign.
[UnsubscribeLink]For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="[UnsubscribeLink]">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.
SimplyCast Canadian founding means CASL (Canadian Anti-Spam Law) enforcement by default: express consent required, unsubscribe within 10 business days, sender identification in every message. Multi-channel automation (email, SMS, voice, fax) requires per-channel consent under CASL. Configure per-channel opt-out granularity to avoid over-suppression across channels the contact may still want.
Testing your SimplyCast unsubscribe link
- Send a test message to a controlled Gmail address you own via the SimplyCast 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 SimplyCast unsubscribe link (step by step)
- Open your campaign or template in the SimplyCast editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
[UnsubscribeLink]. SimplyCast replaces it at send time with a signed URL scoped to the contact. - Wrap it in an anchor:
<a href="[UnsubscribeLink]">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 SimplyCast-hosted preference page.
Canadian CASL enforcement and multi-channel
SimplyCast Canadian founding means CASL (Canadian Anti-Spam Law) enforcement by default: express consent required, unsubscribe within 10 business days, sender identification in every message. Multi-channel automation (email, SMS, voice, fax) requires per-channel consent under CASL interpretation. Configure per-channel opt-out granularity to avoid over-suppression across channels the contact may still want. Voice broadcast and fax broadcast have specific Canadian regulatory overlays beyond CASL.
RFC 8058 one-click headers
SimplyCast 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.
Unified multi-channel messaging
SimplyCast unified multi-channel messaging combines email, SMS, voice broadcast, fax, and social media from a shared contact database. Cross-channel journeys route contacts through the best channel based on preferences and availability. CASL express consent must be documented per channel; imported contact records without documented consent are quarantined per Canadian regulatory expectations.
Frequently Asked Questions
What is the SimplyCast unsubscribe tag?
The merge tag is [UnsubscribeLink]. SimplyCast replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="[UnsubscribeLink]">Unsubscribe</a>.
Does SimplyCast enforce Canadian CASL?
Yes by default. Express consent required for all channels, unsubscribe within 10 business days, sender identification in every message. Imported contacts without documented consent are quarantined.
Does SimplyCast support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. SimplyCast injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Settings > Sender profiles.
Does email opt-out stop SMS on SimplyCast?
Not by default. Per-channel consent granularity under CASL means a contact can opt out of email while continuing SMS. Configure unified cross-channel suppression only when business expectations require it.
How does SimplyCast compare to Envoke or Dialog Insight for Canada?
All three are Canadian-founded with CASL-first defaults. SimplyCast emphasizes multi-channel (email/SMS/voice/fax). Envoke focuses on CASL express consent workflows. Dialog Insight targets enterprise CDP. Vendor choice depends on channel breadth vs depth.
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.
