Unsubscribes & suppression | Brixus365 Docs
Docs Spark Unsubscribes & suppression

Unsubscribes & suppression

Every Spark campaign email includes an unsubscribe link automatically. When a recipient clicks it, Brixus365 suppresses them immediately — no code, no list to maintain, nothing to configure.


Every campaign email Brixus365 sends includes an unsubscribe link in the footer — automatically, on every send, with no template configuration required.

Two mechanisms fire simultaneously on every campaign:

  • Footer link — a personalised unsubscribe URL rendered into the email body. When clicked, it opens a confirmation page at app.brixus365.com where the recipient chooses to opt out and optionally selects a reason from a dropdown.
  • RFC 8058 one-click header — added to the email’s metadata. Modern email clients (Gmail, Apple Mail, Outlook) surface a native Unsubscribe button at the top of the message. One tap and they’re done — no inbox-leaving required. This is the mechanism Google and Yahoo require from bulk senders.

Both routes record the same preference change and take effect immediately.

Can I remove the unsubscribe link? No. It is mandatory on all Spark campaign emails — required for CAN-SPAM, DPDP, and GDPR compliance. Transactional emails sent via the API (receipts, OTPs, password resets) are separate and not affected by this rule.


What happens when someone unsubscribes

They are not deleted. The recipient stays in your list. Brixus365 marks their email channel as unsubscribed and excludes them from all future campaign sends — automatically, with no action required from you.

You can see them immediately:

  • The Unsubscribed (All) stat card on the Recipients page increments.
  • Filter the list to Status → Unsubscribed to see every suppressed contact.
  • Opening their profile shows the Email Marketing toggle turned off under Subscription Preferences.

An audit entry is created for every unsubscribe — channel, timestamp, and the campaign that triggered it (if any). Review this under the Audit Trail tab of the recipient’s profile.


Managing preferences from the dashboard

To update a recipient’s subscription preferences manually:

  1. Go to Spark → Recipients.
  2. Search and click the recipient’s name to open their profile.
  3. Under the Overview tab, find Subscription Preferences.
  4. Toggle Email Marketing (All Domains) off to suppress all email sends, or expand it to adjust subscription per sending domain — useful if you want a contact to stay subscribed to one domain but not another.
  5. Toggle SMS Notifications or WhatsApp to adjust those channels independently.

Changes take effect immediately and are recorded in the Audit Trail.

Support use case. If a recipient says they didn’t mean to unsubscribe, turn their toggle back on from this page. The Audit Trail preserves the original event — timestamp, source, and channel — for your records.


Hard-bounced addresses

A hard bounce means the address is permanently undeliverable — the mailbox doesn’t exist, or the domain has no mail server. Brixus365 records hard bounces and excludes those addresses from all future sends automatically.

Hard-bounce suppression is a separate mechanism from unsubscribes:

  • A bounced address still appears in your recipient list.
  • Their subscription toggle may still show as subscribed.
  • But the address is verified and excluded before every campaign dispatch — it will never receive a send.

Why keep them? Retaining the record lets you see the address, review its engagement history, and decide whether to delete it — without any impact on your deliverability.


Re-importing a suppressed address

If you upload a CSV that includes an email address you previously unsubscribed (or one that previously bounced), the import does not re-subscribe them.

Brixus365 finds the existing record, updates any fields in the CSV (name, custom variables, group membership), and leaves the subscription preference exactly as it was.

Why this matters. A recipient who unsubscribed last month may reappear in a new CRM export. Uploading that export won’t accidentally re-add them to your active send list. The suppression is sticky.


Deleting a contact

If a recipient requests erasure of their data under DPDP or GDPR:

  1. Open their recipient profile (Spark → Recipients → click their name).
  2. Click Delete Recipient in the profile actions.
  3. Confirm in the dialog — this action cannot be undone.

The contact is permanently removed from your list and excluded from all future activity.

Unsubscribe vs. delete. Suppressing a recipient (toggling off their preference) stops future emails and keeps the record for your audit trail. If the recipient’s request is specifically about data erasure — not just stopping future sends — use Delete Recipient. For most unsubscribe requests, updating the preference is sufficient and preserves the audit history.


What’s next

You want to…Go to
Add or import new recipientsAdd recipients
Search, filter, and view subscription status across your listView and manage your recipients
See per-recipient delivery historyRead your campaign results
Understand all the statuses a campaign moves throughCampaign statuses
Your list, protected

Suppression, compliance, and audit trails — handled automatically.

Free signup. 9,000 emails a month, full Spark dashboard, no card needed.