How Unsubscribe Management Works in Sendrealm

An unsubscribe is both a recipient choice and an operational state change. The link has to be easy to use, the request has to update the right audience memberships, and future campaign targeting has to respect the result.

Sendrealm email campaigns can include a visible unsubscribe footer and one-click unsubscribe headers. Campaign owners choose whether an unsubscribe applies to the campaign's included audiences or to all audiences currently associated with the contact.

What Sendrealm adds to a campaign

When Include unsubscribe link is enabled, Sendrealm creates a recipient-specific unsubscribe URL and adds:

• a visible link in the email body
• a List-Unsubscribe header
• a List-Unsubscribe-Post: List-Unsubscribe=One-Click header

The body link gives the recipient an obvious path. The headers let supporting mailbox providers display a native unsubscribe action and process a one-click request.

The token ties the action to the recipient and campaign. Repeated requests are handled idempotently so the same link does not create conflicting membership changes.

Choose the unsubscribe scope deliberately

Sendrealm provides two scopes.

Included audiences only

The contact is unsubscribed from the audiences targeted by that campaign. Use this when the audiences represent a distinct publication or purpose and the recipient may reasonably want to remain in other programs.

Example: a user leaves the weekly product newsletter but remains subscribed to event updates managed through another audience.

All audiences

The contact is unsubscribed from every current audience membership in the project. Use this when the link is intended as a broad marketing opt-out and the user expectation is “stop marketing email from this organization.”

Example: a general promotional campaign provides a global marketing unsubscribe rather than a publication-specific preference.

The correct choice depends on the meaning of your audiences, the promise made at signup, and applicable law. Do not choose the narrow scope merely to preserve reach when the recipient expects a global opt-out.

Unsubscribe is not suppression

In Sendrealm, unsubscribe changes audience membership subscription state. Suppression is a separate project-level delivery safeguard for signals such as hard bounces and complaints.

This distinction lets a team model different realities:

• a person opts out of one newsletter but remains eligible for another consented topic
• a person leaves all marketing audiences but still has an account contact record
• an address is hard-bounce suppressed and cannot receive a transactional message either

Do not bypass an unsubscribe by creating a new audience, and do not remove a hard-bounce suppression because the contact is still marked subscribed somewhere.

Transactional and marketing messages need different rules

Password resets, receipts, security alerts, and account notices can have a different legal and product basis from marketing campaigns. Keeping them separate helps recipients understand the relationship and prevents promotional traffic from affecting critical mail.

Google and Yahoo require one-click unsubscribe for qualifying marketing and subscribed bulk messages, not ordinary transactional messages. Both also expect an obvious body link and low complaint rates. Review the current Gmail sender guidelines and Yahoo Sender Hub requirements.

Legal requirements vary by jurisdiction and message purpose. This article explains product behavior, not legal advice. Have qualified counsel review your consent and unsubscribe design where necessary.

Configure a campaign safely

Before scheduling a marketing campaign:

1. select the intended audiences and preview the reachable count
2. enable the unsubscribe link
3. choose Included Audiences or All Audiences based on the promised scope
4. review the visible footer in the rendered content
5. send to a controlled test recipient
6. inspect raw headers for one-click unsubscribe
7. use the link and confirm the expected memberships change
8. verify the recipient is excluded from a follow-up campaign

Do not test only the landing page. Test the full state change and the next targeting decision.

Prevent reintroduction after an unsubscribe

Common failure paths include:

• a CSV import marks every row as subscribed
• a CRM sync overwrites the messaging platform with stale consent
• a second audience is created for the same purpose
• a team interprets “contact exists” as “contact may receive marketing”
• a migration exports only active contacts and loses opt-out evidence

Make one system authoritative for each preference and define the direction of synchronization. Preserve timestamps, source, scope, and proof where your policy requires them.

Sendrealm CSV imports do not use a later is_subscribed=false value to override an existing subscribed membership. Process real opt-outs through the unsubscribe or preference workflow rather than treating imports as a replacement.

Design audiences and topics around recipient expectations

An audience is an operational targeting asset. A topic or preference is a user-facing promise. They may overlap, but they are not automatically identical.

Name and document them clearly:

• weekly-product-news describes a publication
• webinar-2026-attendees describes an event cohort
• paid-customers describes customer state, not marketing consent
• security-alerts describes an operational stream

If the team cannot explain what leaving an audience means to the recipient, the unsubscribe scope will be difficult to configure correctly.

Monitor unsubscribe and complaint behavior

Campaign analytics include unsubscribe activity. Review:

• unsubscribe count and rate
• complaint count and rate
• which campaign or source produced the change
• whether the footer and sender identity were clear
• whether frequency matched the signup expectation
• whether a narrow audience was more appropriate

An unsubscribe is often a healthier outcome than a complaint. Do not hide the link or add friction to preserve an inflated list size.

Support workflow for an unsubscribe question

When a recipient asks why they still received a message:

1. identify the campaign and recipient
2. inspect the unsubscribe event and timestamp
3. confirm whether the scope was included audiences or all audiences
4. identify the audience that authorized the later campaign
5. check whether a sync or import changed membership
6. correct the source and future targeting

Explain the scope in plain language and honor the broader request if the recipient clearly asks to stop marketing communication.

Trust depends on the next send

The unsubscribe page is only the visible part of the system. The real test is whether the next campaign excludes the recipient according to the choice they made.

Sendrealm connects the link, headers, campaign scope, audience membership, events, and reporting so teams can operate that promise consistently.