API Reference

Bespoke follows a three-step suppression process, with each step progressively more restrictive than the previous one. This process is designed to carefully manage and control the suppression of sending emails to users. By implementing a multi-step approach, we aim to ensure precision and accuracy in suppressing email communications. The increasing restrictiveness of each step helps maintain a high level of compliance and prevents unintended email deliveries.

Supression Hit Teir 1

In the suppression process, the first hit tier occurs at the consent level. At this stage, the user has the option to subscribe or unsubscribe from a specific list. The first hit tier serves as an initial filter to determine the user's preference regarding their subscription status for a particular list. It allows users to exercise control over their email preferences right from the point of consent, ensuring that their choices are respected.

Email Concent StateMeaning
SUBSCRIBEDSubscribed to a list
UNSUBSCRIBEDUnsubscribed from a list

Supression Hit Tier 2

In the suppression process, the second hit tier occurs at the root subscriber level. At this stage, the subscriber has the ability to make global changes to their subscription status. They can choose to unsubscribe from all lists or mark specific emails as spam. This tier provides an additional level of control to subscribers, allowing them to manage their preferences on a broader scale. By enabling users to unsubscribe globally or report emails as spam, we prioritize their autonomy and aim to deliver a more personalized and relevant email experience.

Email StatusMeaning
SUBSCRIBEDThe subscriber is allowed to receive emails to all lists
UNSBUSCRIBEDThe subscriber is not allowed to receive emails to any of the lists
MARKED_AS_SPAMThe subscriber marked an email as spam. Consequently they are not allowed to recieve emails to any of the lists

At the root subscriber level, if a subscriber chooses to unsubscribe from all lists or marks emails as spam, there is still an opportunity for them to resubscribe. If the subscriber decides to subscribe to any of the individual lists again, it will automatically include them in the root subscriber level as well.

By allowing subscribers to easily opt back in if they wish to receive emails from any specific list, we offer flexibility and ensure that their preferences are respected. This approach empowers subscribers to make informed choices about the emails they wish to receive while maintaining the option to re-engage with the root level list when desired.

The global list level supression is available in the unbuscribe preference page of each subscriber.

Supression Hit Tier 3

In the suppression process, the third hit tier involves root user-level suppression. This tier represents the highest level of restriction in the process. It allows for suppression at the root user level, which means that certain actions or restrictions are applied to the entire root user account.

Root user-level suppression typically involves more comprehensive measures, such as suspending or blocking the root user's account altogether. This level of suppression is implemented in cases where there are significant violations or breaches of terms and conditions, or when there is a need to protect the integrity and security of the system.

By implementing root user-level suppression, Bespoke ensures that appropriate actions can be taken to maintain the overall stability, security, and compliance of the platform.

Email Delivery StatusMeaning
SUBSCRIBEDAllowed to receive emails to the user
BOUNCEDAfter 7 bounces. This user is never allowed to receive any emails.

In the third hit tier of the suppression process, once a subscriber reaches a threshold of seven consecutive bounces, it is not possible to revert back to a subscribed status. Bounces occur when email delivery attempts fail repeatedly, indicating persistent issues with delivering emails to the subscriber's address.

To maintain the integrity of the email system and protect against potential abuse or ineffective communication, the decision to prevent re-subscription after seven bounces is implemented. This ensures that the delivery resources are efficiently allocated and that the user's experience is improved by avoiding ongoing unsuccessful email delivery attempts.

Subscribers who have reached this threshold will remain in the suppressed state and will no longer be able to subscribe again. This restriction helps maintain a high-quality email delivery service and minimizes potential disruptions caused by persistent delivery failures.