Delivra is a US mid-market email marketing and marketing automation platform serving mid-sized brands, associations, and higher education, with a strong focus on managed services and customer support. The unsubscribe mechanism uses a merge tag auto-injected into every campaign footer, and Delivra emits RFC 8058 headers automatically for authenticated sending domains. Consent is tracked as an account-wide Do Not Email flag by default, with per-list opt-out available as a configuration option. This guide covers the tag, the DNE flag model, and the managed-service handover for large campaign compliance reviews.
Delivra unsubscribe link
| Tag syntax | %%unsubscribe_link%% |
| Placement | Auto-embedded in every campaign footer |
| Scope | Account-wide Do Not Email flag |
| Config path | Preferences > Message defaults > Footer |
| RFC 8058 one-click | Yes, automatic for authenticated sending domains |
How to add the unsubscribe tag in Delivra
Place the merge tag exactly as shown below in the email template. Delivra replaces it at send time with a signed URL scoped to the recipient and campaign.
%%unsubscribe_link%%For custom HTML templates, wrap the tag in an anchor to render a proper hyperlink in the delivered email:
<a href="%%unsubscribe_link%%">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.
Delivra API contact updates (bulk import, integration sync) do not respect the Do Not Email flag unless the import explicitly sets the flag on each imported row. If your CRM sync overwrites contact records nightly, previously-unsubscribed contacts get re-added as opted-in, which is a CAN-SPAM violation.
Testing your Delivra unsubscribe link
- Send a test message to a controlled Gmail address you own via the Delivra 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 Delivra handles unsubscribes
Delivra is a mid-market email marketing platform serving associations, nonprofits, and B2B senders. Its unsubscribe mechanism uses the %UNSUBSCRIBE% merge token, replaced with a signed URL at send time. The email editor includes a default footer with the token pre-populated, and Delivra refuses to send campaigns lacking the token. Clicks route to a Delivra-hosted preference page where subscribers can manage list memberships or opt out entirely, matching the account-level configuration.
Association and nonprofit workflow
Because Delivra serves many associations and membership organizations, its preference center supports the segmented-communication model those organizations typically use: separate lists for Newsletter, Event Announcements, Advocacy Alerts, Chapter Updates, and Fundraising Appeals. Subscribers can opt out of specific lists while remaining on the core membership communications, which reduces full-organization unsubscribes significantly. This granularity is critical for member retention in nonprofit and association contexts.
RFC 8058 support
Delivra added RFC 8058 one-click unsubscribe headers in 2024 to meet the Google and Yahoo bulk-sender requirements. The List-Unsubscribe and List-Unsubscribe-Post headers are added automatically on sends from authenticated domains. Domain authentication (SPF, DKIM, DMARC) is completed under Account Configuration, and Delivra customer success guides accounts through the setup during onboarding. Accounts sending from unauthenticated domains lose access to one-click headers and see measurable deliverability degradation.
Compliance and audit trail
Delivra tracks a full consent and opt-out history per subscriber (opt-in timestamp, source, IP, category preferences, opt-out timestamp), which is exposed through the account interface for audit purposes. This is important for associations that operate under specific membership consent frameworks and for nonprofits subject to donor-privacy regulations. The audit trail is retained for the life of the account plus a configurable retention period, satisfying most regulatory record-keeping requirements.
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.
