APSIS is a Nordic email marketing and marketing automation platform serving Scandinavian mid-market and enterprise customers with GDPR-first defaults, integrated CRM, and Nordic language support. The unsubscribe mechanism uses the {UnsubscribeLink} merge tag auto-injected into every campaign footer, and APSIS emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked at the contact level with Nordic data protection authority alignment. This guide covers the tag, the Nordic regulatory model, and how to verify the setup end to end.
Apsis unsubscribe link
| Tag syntax | {UnsubscribeLink} |
| Placement | Auto-embedded in every campaign footer |
| Scope | Contact-level opt-out with Nordic DPA alignment |
| Config path | Settings > Sender identities > Email footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Apsis
Place the merge tag exactly as shown below in the email template. Apsis 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.
APSIS Nordic GDPR compliance combined with Swedish IMY, Danish Datatilsynet, and Norwegian Datatilsynet enforcement quarantines imported lists without documented consent. Nordic senders migrating from other ESPs must provide GDPR documentation for each contact. Swedish, Danish, Norwegian, and Finnish language templates ship as first-class options for the multi-jurisdiction Nordic market.
Testing your Apsis unsubscribe link
- Send a test message to a controlled Gmail address you own via the Apsis 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 APSIS unsubscribe link (step by step)
APSIS 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 APSIS editor.
- Add or edit a text block in the footer where the unsubscribe link should appear.
- Insert the merge tag
{UnsubscribeLink}. APSIS replaces it at send time with a signed URL scoped to the contact. - Wrap it in an anchor:
<a href="{UnsubscribeLink}">Avregistrera</a>for Swedish,Afmeld</a>for Danish, orUnsubscribefor English. - Configure the sender identity under Settings > Sender identities.
- Send a test to a seed address and verify the rendered link routes to the APSIS-hosted preference page.
Nordic data protection authority alignment
APSIS Nordic GDPR compliance combined with Swedish IMY, Danish Datatilsynet, and Norwegian Datatilsynet enforcement quarantines imported lists without documented consent. Nordic senders migrating from other ESPs must provide GDPR documentation for each contact. Swedish, Danish, Norwegian, and Finnish language templates ship as first-class options for the multi-jurisdiction Nordic market. Each Nordic country s DPA applies GDPR with local interpretation, so cross-border Nordic senders should verify consent bases per jurisdiction.
RFC 8058 one-click headers
APSIS 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 identities. SPF and DKIM records must be verified. Nordic data residency options align with GDPR data localization preferences for regulated industries and Nordic public sector customers.
Integrated CRM and Nordic B2B workflows
APSIS integrated CRM connectors sync opt-out state with Salesforce, HubSpot, and Nordic CRMs (SuperOffice, Lime). B2B workflows respect the contact opt-out flag at every send step. Nordic B2B norms typically expect marketing consent to be documented but permit reasonable sales outreach under legitimate business interest, subject to per-country DPA interpretation. Configure per-team consent scoping if sales and marketing consent should be handled separately.
Frequently Asked Questions
What is the APSIS unsubscribe tag?
The merge tag is {UnsubscribeLink}. APSIS replaces it at send time with a signed URL scoped to the contact. Use it inside an anchor: <a href="{UnsubscribeLink}">Avregistrera</a>.
Does APSIS enforce Nordic GDPR?
Yes by default. Imported contact lists without documented consent are quarantined until confirmed. Swedish IMY, Danish Datatilsynet, and Norwegian Datatilsynet enforcement each apply GDPR with local interpretation.
Does APSIS support one-click unsubscribe for Gmail and Yahoo?
Yes, automatically for authenticated domains. APSIS injects List-Unsubscribe and List-Unsubscribe-Post headers on every marketing send from domains verified under Settings > Sender identities.
Does APSIS support Swedish, Danish, Norwegian, and Finnish?
Yes as first-class template language options. Nordic senders benefit from native language templates and preference center copy for each country s audience.
How does APSIS compare to Ungapped or Get a Newsletter?
All three are Nordic-focused ESPs with GDPR-first defaults. APSIS targets mid-market and enterprise with marketing automation. Ungapped and Get a Newsletter focus on SMB simplicity. Vendor choice depends on feature depth and account size.
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.
