Welcome to the Community! We are so glad to have you here. Happy to walk through this with you!
Thanks for popping in here @Spark Bridge Digital LLC, I think your suggestion in spot on! Our fellow user is referencing a workflow that is suggested for our Sunset Flow. A sunset flow is designed to phase out customers who are no longer engaging with your brand. You can use this flow as a last-ditch effort to win back their business, and then delete or suppress anyone who is not responsive. This will help you maintain a clean list and prevent you from sending to unengaged subscribers and possibly harming your deliverability.
Our help center documentation outlines that in this specific flow, users are sent through the flow when they are added to a very disengaged segment called ‘Sunset’ and send one or two ‘last chance to stay subscribed’ messages. At the end of the flow, you can add an update profile property action to the user at the end if the flow as mentioned by @Spark Bridge Digital LLC. This will tag those who do not engage with the email and thus are passively indicating that they would like to unsubscribe. Configure the tag to specify that these contacts should be suppressed. You can do this by creating a new boolean profile property where the value "Suppress" is "True."
Not a sure straightforward way per-say but this is how I handle contacts like this -
At the end of the flow, I’ll plop in the ‘Update Profile Property’ action and update a custom field I create in a demo profile called “Suppression List’ and then in that Action of the flow I update that field to be the name of the Flow or even just TRUE.
Then create a Segment of anyone with that custom field filled in and then making sure this list is excluded from all sends and flows. Then you can also bulk unsubscribe/suppress them from all communications via the segment settings when you create a Snapshot of the segment and then upload them back into https://www.klaviyo.com/people/suppressed.
A bit manual but hope that provides a bit of a solution!
Welcome to the Community! We are so glad to have you here. Happy to walk through this with you!
Thanks for popping in here @Spark Bridge Digital LLC, I think your suggestion in spot on! Our fellow user is referencing a workflow that is suggested for our Sunset Flow. A sunset flow is designed to phase out customers who are no longer engaging with your brand. You can use this flow as a last-ditch effort to win back their business, and then delete or suppress anyone who is not responsive. This will help you maintain a clean list and prevent you from sending to unengaged subscribers and possibly harming your deliverability.
Our help center documentation outlines that in this specific flow, users are sent through the flow when they are added to a very disengaged segment called ‘Sunset’ and send one or two ‘last chance to stay subscribed’ messages. At the end of the flow, you can add an update profile property action to the user at the end if the flow as mentioned by @Spark Bridge Digital LLC. This will tag those who do not engage with the email and thus are passively indicating that they would like to unsubscribe. Configure the tag to specify that these contacts should be suppressed. You can do this by creating a new boolean profile property where the value "Suppress" is "True."
surely be a simple idea to just have an option to unsubscribe someone as sendinblue has an option to “remove from list” as part of their automations which we previously used.
Unfortunately, that isn’t an automated option at the moment. However, I will submit this as a feature request on your behalf and our suggestions should provide a useful workaround!
I did all of this and created a segment with an OR statement for “Suppress is True”. But none of the Suppress is True are showing up in this segment. But they all show up when creating the segment with just this profile property. Please see attached screenshot for the discrepancy of 4,000 profiles. Any ideas why this would happen?
From my experience, because you have so many more conditions in the highlighted segment, it's not surprising to not have the segment capture all of those expected 4,272 profiles that have this custom profile property of Suppress is True. Keep in mind that users must meet all conditions to be included in a segment; meaning that users who have this Suppress is True profile property may potentially be excluded from the segment for not meeting those addition rules.
Another thing to be wary of is your use of the OR condition in the segment. Since you've paired the Suppress is true with the Placed order zero times in the last 400 days, users can qualify for this segment for either of these conditions. A different take on understanding this is users who have Placed order zero times in the last 400 days OR have this Suppression is true profile property as the base of your segment which would then be parsed out based on each of these additional segment conditions. This means that there are two possible ways users can qualify for this segment through meeting all the conditions. The two methods users can qualify for the segment after meeting all the conditions:
Method 1:
Method 2:
What someone has done, Placed Order zero times in the last 400 days
AND
What someone has done, Received Email is at least 20 in the last 90 days
AND
What someone has done, Opened Email zero times in the last 90 days
AND
What someone has done, Clicked Email zero times in the last 365 days
AND
If someone is or is not suppressed, Person is not suppressed for email
AND
What someone has done Viewed Product zero times in the last 365 days
Properties about somebody, Suppress is True
AND
What someone has done, Received Email is at least 20 in the last 90 days
AND
What someone has done, Opened Email zero times in the last 90 days
AND
What someone has done, Clicked Email zero times in the last 365 days
AND
If someone is or is not suppressed, Person is not suppressed for email
AND
What someone has done Viewed Product zero times in the last 365 days
If you are saying of those 219 profiles that are captured by the segment do not have this custom profile property of Suppress is True, then I would suspect they may have been parsed out by these additional conditions meaning that this segment would contain primarily profiles who have not placed an order in the last 400 days. Alternatively, I would suggest further double checking and vetting those profiles captured by the segment. In my opinion, it would be very unlikely that of those 4,272 profiles, none of them would be captured by this segment which contained an OR condition.
The easiest way to vet and very this segment would be exporting this segment to a .CSV and see if this custom profile property of Suppress is an available exportable field. You can then also confirm this by exporting the segment while including this field for review and cross reference in bulk. You can find our guide on how to export a list or segment from the How to Export a List or Segment to a CSV File Help Center article.
Thanks @David To, my overall goal is to have one segment that I can use for List Cleaning/Suppression each month. The custom profile property is created when a profile completes our Sunset Flow without clicking on any of the emails.
With the OR statement, I thought it would capture anyone with the custom property Suppress is TRUE OR anyone who meets all of the conditions connected by the AND’s….Which is what I wanted...a combined list of Unengaged (defined by the all of the connected AND statements), and all of those whose profile has “Suppress is True”.
Thanks for those additional details! If you haven’t already, I would suggest taking a look at our AND vs. OR Guide Help Center article that goes over the use of creating segments while using both the AND/OR conditions.
Unfortunately, in this particular case, simply adding an OR condition to the segment wouldn’t act as a connector piece to achieve your goal of capturing users who have this particular custom profile property or meet those conditions to be defined as unengaged. Instead, including this OR condition to your segment would actually be used more so as a clarifying condition to further refine your segment and further parse it down.
Alternatively, I would recommend keeping these two groups of users separate; your unengaged users as defined by those series of conditions and those who have this particular profile property of Suppression is True. One adjustment I would advise making is to include the “If someone is or is not suppressed, Person is not suppressed” as part of your segment capturing users who have the Suppression is True property. Since it sounds like you’ll be frequently using these two segments to list clean and suppress, including this additional condition will allow for easier organization and prevent you from repeated suppressing users who are already suppressed (though it wouldn’t impact anything).
By clicking “Accept All Cookies,” you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
Privacy Preference Center
Your Privacy
Strictly Necessary Cookies
Performance Cookies
Functional Cookies
Targeting Cookies
Site Analytics
Your Privacy
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
Privacy Notice
Strictly Necessary Cookies
Always Active
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
Performance Cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
Functional Cookies
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
Targeting Cookies
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Site Analytics
These cookies record your visit to our website, and are used to track your visit including information such as: web page interactions (clicks, hovers, focus, mouse movements, browsing, zooms and other interactions), referring web page/source through which you accessed the Sites, heatmaps and scrolls, screen resolution, ISP, and statistics associated with the interaction between device or browser and the Sites. If you are accessing our Services with a European IP address, you have been asked to consent to the use of these cookies (you are free to deny your consent).