Bloomreach Engagement automatically adds the list-unsubscribe header to all emails. This header ensures that the unsubscribe button is available right next to the name of the sender. This protects your email reputation as it would normally be much easier and faster to click on the spam button than to look for the unsubscribe link at the bottom of the email (read more in the [Email deliverability](🔗) article). Clicking on this button unsubscribes the customer directly, without being redirected to the consent page where they need to update their preferences.
Unsubscribe button issue with certain email providers
Due to certain email providers’ (including Microsoft Outlook, Hotmail, and Gmail) lack of adoption of the List Unsubscribe feature, the unsubscribe button located in the email header may not function properly, and the end user may not be unsubscribed. This is an issue on the email provider side; however, please be assured that the unsubscribe button in the footer of each email will continue to function properly.
# How it works
This is a built-in function in Bloomreach Engagement.
However, notice that displaying this list-unsubscribe header in the emails is actually subjected to the domain reputation. Thus, it will automatically appear after building up domains reputation.
When a customer clicks on the list-unsubscribe button one event will be tracked into the customer's profile:
**[consent event](🔗)** with attributes `
action = reject`, `source = list-unsubscribe`, and `category` that is equal to the consent category which this email belonged to
Bloomreach Engagement is using _mailto_ unsubscribe links which are supported by most common email clients, such as Gmail, Outlook.com, Yahoo! Mail, and Apple/iOS Mail. When a recipient clicks on the list-unsubscribe link, the email client sends an email (silently) into Bloomreach Engagement's own inbox, where it's processed as an unsubscribe request. Bloomreach Engagement does not forward the unsubscribe requests to integrated ESPs which means email addresses will not be automatically unsubscribed on external unsubscribe lists. There are exceptions, where some ESPs do not allow us to control list-unsubscribe headers and they handle it on their side - read more in your specific ESP documentation ([Sendsay](🔗) and [Sendinblue](🔗)).
The list-unsubscribe header is not added to emails sent under the "general" consent category or those sent through the transactional API.
# How to unsubscribe from more categories
If you want to unsubscribe customers who clicked on this option from more consent categories automatically, you can create a simple [scenario](🔗) for that:
The "On event consent" node should be specified as follows:
Then add the "Add event" node for every consent category you want the customer to unsubscribe from. Set it for the event "consent" and specify the following attributes. Adjust the value of the "category" attribute according to your needs.
Note: Add a separate node for every category to be unsubscribed.
If you don't see the event "consent" or any of its attributes in the list when setting up the nodes, it means it is not tracked in your project yet. Define the event and attributes in the [Data Manager](🔗) first to be able to work with it in this scenario.
# Disabling list unsubscribe
You can disable the list unsubscribe by going to `Settings` > `Project Settings` > `Channels` > `Emails` > `List unsubscribe` and untick the `Enable list unsubcribe links` box.
As list unsubscribe provides significant benefits to your deliverability rating, we do not recommend disabling it unless you have a separate system for unsubscribed customers.