Understanding and managing the blocklist

The blocklist (or exclusion list) contains email addresses and mobile numbers that should be excluded from your mailings. A contact on the blocklist remains in your database, with all their information, but no longer receives messages on the channel in question.

Splio manages two separate and independent blocklists: one for the email channel, one for the SMS channel. A contact can therefore be blocked on one channel while remaining reachable on the other.

This feature is essential for three specific reasons:

  • It protects your sender reputation by preventing emails from being sent to invalid addresses.

  • It helps you comply with regulatory obligations by excluding contacts who have unsubscribed or withdrawn their consent.

  • It improves the performance of your campaigns by focusing your mailings on recipients who are actually reachable.

1. Prerequisites

  • You have access to the Splio platform with rights to the Data section.

  • To manage the blocklist via the API, you have valid API credentials.

  • You know which channel (email or SMS) you want to use.

2. Access the blocklist

Go to Data > Blocklists . This page centralizes blocked email addresses and mobile numbers. The view is organized into two tabs, one for each channel, and displays a counter of blocked contacts as well as search, filter, and export tools.

3. Understanding the interface

The Data > Blocklists page has two tabs, one per channel.

Tab

Content

E-mail

Blocked email addresses

Mobile

Blocked mobile numbers (SMS channel)

Several actions are available at the top of the list.

Element

Role

To research

Find a specific address or phone number in the list

Filtre par source

Display inputs according to the reason for the blockage. Available on both channels. Each source displays its number of inputs.

Download

Export the complete list

Menu d'actions

Add, delete or import addresses or numbers into the blocklist

4. Understanding the reasons for the blockage

Each entry corresponds to a specific blocking source and indicates the reason for it. The source filter allows each blocking category to be displayed separately on both channels.

4.1 Sources of email blocking

Source

Reason

Application of the block

Hard Rejections (source: bounce )

Address permanently invalid (misspelled, non-existent domain, deleted mailbox)

Immediate, from the very first hard bounce

Soft Rejections (source: softbounce )

Temporary inability to deliver (box full, server unavailable)

After three unsuccessful attempts over three consecutive weeks, a successful delivery in the meantime resets the counter to zero.

Spam complaints (source: fbl )

The contact reports the email as spam from their email client.

Immediate, upon receipt of the complaint

Unsubscribes (source: unsub )

The contact unsubscribes via the link in the email or their email client's tools.

Immediate

Custom email blocklist (source: custom )

The contact was added manually, by a user, via the API, or during an import.

Manual (no automatic mechanism)

4.2 Sources of SMS blocking

The SMS channel also has a filter based on source, on the same principle as email. Its sources differ slightly.

Source

Reason

Application of the block

Non-existent or invalid number (source: bounce )

The number does not exist or is invalid (the equivalent of a hard bounce for email)

Immediate

Soft bounces (source: softbounce )

SMS messages cannot be delivered temporarily.

After several failed deliveries

STOP / Unsubscribe (source: unsub )

The contact replied STOP to the SMS or unsubscribed via the unsubscribe link

Immediate

Custom SMS blocklist (source: custom )

The contact was added manually, by a user, via the API, or during an import.

Manual (no automatic mechanism)

5. View a contact's blocking information

For most blocklists, blocking information is directly accessible from the contact's record. You can see the source of the blocklist, the reason for the block, and the date the contact was added.

6. Add contacts to the blocklist

  1. Open Data > Blocklists .

  2. Open the actions menu, then choose Ajouter des emails ou des numéros à la blocklist

  3. Select the relevant channel: Email or SMS .

  4. Enter the addresses or numbers in the text box. You can enter multiple addresses or numbers, one per line or separated by a comma.

  5. Click Ajouter to confirm. Manually added entries will be included in the "custom blocklist".

You can also perform this operation via the API. See point 10 for more information.

7. Remove contacts from the blocklist

  1. Open the actions menu in Data > Blocklists

  2. Choose Supprimer des emails ou des SMS de la blocklist

  3. Enter the address(es) to be collected, then confirm.

You can only remove manually added entries and unsubscribes. Blocks resulting from a hard bounce, a soft bounce, or a spam complaint cannot be removed: they protect your sender reputation.

You can also perform this operation via the API. See point 10 for more information.

8. Understanding the impact on subscription lists

Email and SMS blocklists are independent: a contact blocked by email can still receive SMS messages, and vice versa.

However, be aware that in a single-list configuration (a single subscription list for both channels), unsubscribing from an email adds the contact to the email blocklist and revokes their consent. Without this opt-in, they no longer appear in the filters and therefore no longer receive SMS messages. On the other hand, a hard bounce from an email does not affect their subscription lists: they remain reachable by SMS.

In a multi-list configuration, unsubscribing from one list only affects that list. The contact can remain opt-in to other lists.

9. The SMTP relay blocklist

If you use Splio's SMTP relay, especially for your transactional emails, be aware that it has its own blocklist, separate from that of your universe.
This separation is voluntary: a contact who no longer wishes to receive your marketing communications can legitimately continue to receive a transactional email, such as an order confirmation or a password reset.

10. Manage the blocklist via the API

All blocklist management actions available in the interface can also be performed via the API, but are not accessible from the Datahub.

The following operations are available:

  • Add addresses to a blocklist: POST /data/blacklists/{channel}

  • Remove addresses from a blocklist based on their source: DELETE /data/blacklists/{channel}/{source}

  • View or export blocked email addresses: GET /data/blacklists/emails

  • View or export blocked phone numbers: GET /data/blacklists/cellphones

The channel parameter can take the values email or cellphone .

The complete reference, including request and response formats, is available on the Developer Portal .

11. FAQ

Q: Is a blocked contact removed from my database?
A: No. It remains in your database with all its information. It is simply excluded from being sent on the channel in question.

Q: Why does a contact on the blocklist still appear in my filters?
A: That's normal. The blocklist isn't taken into account when targeting. The exclusion is applied when the campaign is sent. Therefore, the blocked contact won't receive the message, even if they appear in the filter.

Q: Can I import contacts directly into the blocklist?
A: Yes. You can add email addresses or mobile numbers to the blocklist via manual import or the API. Entries added this way automatically receive the custom source.

Q: Can a contact be blocked by email but not by SMS?
A: Yes. Email and SMS blocklists are completely independent. A contact can be blocked on one channel while remaining reachable on the other. In a single-list configuration, however, unsubscribing from emails removes the contact's consent, which can also prevent SMS messages from being sent.

Q: What is the difference between a blocklist and an opt-out?
A: A blocklist is a technical exclusion applied to an email address or mobile number, preventing any sending through that channel. Opt-out refers to the withdrawal of marketing consent from the contact.

Q: My export contains more lines than the displayed counter, is this a bug?
A: No. The counter is updated once a day and may therefore temporarily differ from the actual number of entries. Furthermore, if you are using the SMTP relay, the same address may appear multiple times if it is blocked on both your universe and the relay.

Q: How can I find out why a contact is blocked?
A: You can view the source of the block from the contact record, use the source filter on the Data > Blocklists page, or query the API. The softbounce blocklist is an exception: its information is only visible on the Data > Blocklists page.