Campaign Monitor CreateSend is the underlying platform for Campaign Monitor and Emma Email, serving SMBs, agencies, and mid-market brands globally with drag-and-drop editor, transactional API, and multi-account agency management. The unsubscribe mechanism uses the <unsubscribe> merge tag auto-injected into every campaign footer, and CreateSend emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the list level with subscriber-level unsubscribe. This guide covers the tag, the CreateSend platform architecture, and how to verify the setup end to end.
Createsend Ie unsubscribe link
| Tag syntax | <unsubscribe> |
| Placement | Auto-embedded in every campaign footer |
| Scope | Per-list opt-out with account-wide suppression option |
| Config path | Account settings > Client settings > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Createsend Ie
Place the merge tag exactly as shown below in the email template. Createsend Ie 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.
Campaign Monitor CreateSend uses HTML-style angle-bracket tags () rather than curly-brace conventions used by most ESPs. Custom HTML templates must escape actual HTML tags carefully to avoid conflicts with merge tag parsing. Agency multi-account management isolates consent per client account, similar to SharpSpring Mail and GoHighLevel multi-tenant patterns.
Testing your Createsend Ie unsubscribe link
- Send a test message to a controlled Gmail address you own via the Createsend Ie 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 CreateSend unsubscribe link (step by step)
CreateSend 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 CreateSend editor (Campaign Monitor or Emma Email admin).
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
<unsubscribe>. CreateSend replaces it at send time with a signed URL scoped to the subscriber. - Wrap it in an anchor:
<a href="<unsubscribe>">Unsubscribe</a>. - Configure the sender identity under Account settings > Client settings.
- Send a test to a seed address and verify the rendered link routes to the CreateSend-hosted preference page.
Angle-bracket merge tags and template migration
Campaign Monitor CreateSend uses HTML-style angle-bracket tags (<unsubscribe>) rather than curly-brace conventions used by most ESPs. Custom HTML templates must escape actual HTML tags carefully to avoid conflicts with merge tag parsing. Template migration to or from CreateSend requires tag conversion. Agency multi-account management isolates consent per client account, similar to SharpSpring Mail and GoHighLevel multi-tenant patterns.
RFC 8058 one-click headers
CreateSend 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 Account settings > Client settings. SPF and DKIM records must be verified per client account. Multi-region data residency options (Americas, EU, Asia-Pacific) align with regional data localization preferences for enterprise customers.
Multi-account agency management and consent isolation
CreateSend multi-account agency management isolates consent per client account by default. An unsubscribe on Client A does not suppress the contact on Client B (same email may exist in multiple agency-managed client accounts). Agencies serving overlapping contact bases should configure per-client vs cross-client suppression rules based on regulatory interpretation and audience overlap. Transactional API sends (order confirmations, password resets) bypass marketing consent per the transactional exemption.
Frequently Asked Questions
What is the CreateSend unsubscribe tag?
The merge tag is <unsubscribe> in HTML-style angle-bracket format. CreateSend replaces it at send time with a signed URL scoped to the subscriber. Use it inside an anchor: <a href="<unsubscribe>">Unsubscribe</a>.
Is CreateSend the same as Campaign Monitor?
CreateSend is the underlying platform. Campaign Monitor and Emma Email are the customer-facing brands running on CreateSend infrastructure. Merge tag syntax and features are consistent across all CreateSend-based products.
Does CreateSend support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. CreateSend injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Account settings.
Do agency client accounts share suppression?
Not by default. Multi-account agency management isolates consent per client account. Configure per-client vs cross-client suppression rules based on regulatory interpretation and audience overlap.
Can I use HTML tags in CreateSend templates?
Yes but escape actual HTML tags carefully. The angle-bracket merge tag syntax can conflict with regular HTML parsing if templates are not authored with awareness of the CreateSend tag conventions. Follow the official template guide for safe patterns.
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.
