Overview
This article details the technical processes behind the opt-in and unsubscription management in Splio Platform. As a reminder, a contact is considered optin in Splio when subscribed to a list and is opted-out when included into the blocklist and/or is no longer subscribed to a list.
Sending a message via Splio Marketing Automation
Types of campaigns (current naming) | Other names for this campaign type (also known as…) | Channels available | Uses designs from Splio | Contact needs to be in the Splio database | Contact needs to be in a list | Transactional option possible | Universe suppression list (aka blocklist) applied | Global suppression list (aka Splio blocklist) applied |
|---|---|---|---|---|---|---|---|---|
One-shot | Email, SMS, RCS (soon) | ✔️ | ✔️ | ✔️ | ❌ | All blocklists | ✔️ | |
Recurring campaign | Journey recurring, Recurring campaign, Automations | Email, SMS, RCS (soon), WhatsApp Partners (webhooks) | ✔️ | ✔️ | ✔️ | ❌ | All blocklists | ✔️ |
Triggered campaign | Journey triggered, Automations | Email, SMS, RCS (soon), WhatsApp Partners (webhooks) | ✔️ | ✔️ | Marketing: Yes Transactional: No | ✔️ with boolean | Marketing: All blocklists Transactional: Hard bounce and custom suppression list | ✔️ |
Auto legacy and Trigger legacy (deprecated) | Automatic Trigger/Real time trigger | Email, SMS (only for auto legacy) | ✔️ but option to add an external design link in the campaign | ✔️ | ❌ Contact does not need to be in a list (by using the sales filter) | ✔️ with sales filters | Marketing: All blocklists Transactional: All blocklists except soft bounce and unsubscribed | ✔️ |
SMTP relay | Forward | Email, SMS | ❌ | ❌ | ❌ N/A because contact does not need to be in the database | ✔️ | The blocklist of SMTP Relay | ✔️ |
Use cases for contacts in Mono-list vs Multi-list
Assuming that the contact is in the database
Mono-list | Multi-list | |
|---|---|---|
Contact subscribes to a list | Contact is added to the list | Contact is added to the list |
Contact unsubscribes from a list | Contact is removed from the list and added to the unsubscribed blocklist | The contact is unsub from 1 list and not added in the blocklist |
Contact unsubscribes from all lists | N/A | Contact is unsub from all lists and added to the blocklist |
Contact unsubscribes via the mailbox provider button | Contact is unsub from all lists and added to the blocklist | Contact is unsub from all lists and added to the blocklist |
Impact on contacts in a list or not in other scopes
Contact is in a list | Contact is not in a list | Contact is in the database | Audience calculation | |
|---|---|---|---|---|
Target filter/group calculation | Displayed in the audience calculation | Excluded from the audience calculation | Contact needs to be in the database | Blocklisted contacts are not removed from the audience calculation |
Target filter/group export | Displayed in the export | Displayed in the export | Contact needs to be in the database | Blocklisted contacts are not removed from the audience calculation |
Data > Contact page export | Displayed in the export | Excluded from the export | Contact needs to be in the database | N/A |
Statistics calculation (CPD, Campaign statistics) | Metrics can be calculated | Metrics can be calculated for transactional campaigns | Contact needs to be in the database for metrics to be calculated | N/A |
Invoicing | Billed | Not billed BUT Messaging credits are used | Not billed BUT Messaging credits are used | N/A |