Skip to main content
Solved

Can't create a segment based on Sunset Flow


Forum|alt.badge.img
  • Contributor II
  • 3 replies

Hi there, 

So i’ve only just realised that the sunset flow doesn’t automatically suppress recipents who have hit all the parameters in the flow. With that in mind, I thought I’d be able to set up a segment where it captures the “Unengaged - True” Property, so that I can easily suppress them, however this property isn’t available to add in my segment dropdown for Property Profile values. What am I missing?

 

Thanks so much!

Best answer by emma.owens

@Hord That is exactly right! Setting up a new property labeled ‘Unengaged = True’ is typically what we recommend for a sunset flow. So if a profile makes it all the way to that step of the flow, that property will be added to their profile, and they will then be added to the segment you’ve created. From there, you would suppress the profiles in that Unengaged segment periodically! 

 

View original
Did this topic or the replies in the thread help you find an answer to your question?

8 replies

annasophiefc
Partner - Platinum
Forum|alt.badge.img+22
  • 2025 Champion
  • 99 replies
  • January 24, 2025

Hi ​@Hord 

 

Thank you for posting in the Community!

 

For the property to be added to recipients throughout the flow, you should have it on a profile first. Are you using the boolean Unengaged = TRUE or how is your setup? Is property update set live?

For a quick fix if you are looking to suppress contacts that have already gone through the flow - I would setup a segment saying ‘When someone has received email where flow equals Sunset flow’ and then following the criteria of your sunset flow in your segment, then you can manually suppress these profiles, who should have had the property added through the flow.

I hope this helps!


Forum|alt.badge.img
  • Author
  • Contributor II
  • 3 replies
  • January 24, 2025

Thanks so much for getting back to me - it’s currently set-up as boolean Unengaged = TRUE - I’ve just attached a screenshot. Thanks so much for your quick fix option - I’ll take a look into that right away. I think the first issue I’ve had is that everything was set to manual and so they’ve only just gone “live” today - however I know people have been receiving them as we’ve had a couple of people respond to them for a chat. 

 

How do I place the Unengaged - True to a profile?

Thanks so much for your help so far!

 


annasophiefc
Partner - Platinum
Forum|alt.badge.img+22
  • 2025 Champion
  • 99 replies
  • January 27, 2025

Hi ​@Hord 

 

If it was set to manual, that explains a lot!

Usually before I setup a custom property in a flow, I simply add it to my own profile in Klaviyo beforehand, so I am certain that the right property is being mapped to the individual profiles in the right format.

 


Byrne C
Community Manager
Forum|alt.badge.img+10
  • Community Manager
  • 58 replies
  • January 27, 2025

Hi ​@Hord 

Just wanted to add on to ​@annasophiefc’s answer! Profile properties will only appear in segment/flow dropdown menus after that property appears on at least one profile. To manually add a property to a profile, go to any profile and select “Add custom property” in the custom properties box.

From there, add the property and the value you’re looking to have appear in dropdowns.

 

Let me know if I can answer any additional questions!

-Byrne


Forum|alt.badge.img
  • Problem Solver II
  • 11 replies
  • January 27, 2025

Hey ​@Hord,

You can automatically suppress contacts after they have failed to re-engage with your Sunset flow via webhook. Here is my quick tutorial on how to achieve this easily (it is technical but you just need to copy and paste 😉).

Start by creating an API key with Write Access to Profiles and Subscriptions. Head back to your Sunset flow and drag a new webhook to the end of the flow.

Then you have to fill the webhook data with the following parameters. Only change PRIVATEKEYHERE for your freshly created API key. The rest should stay the same!

 

Destination URL:     https://a.klaviyo.com/api/profile-suppression-bulk-create-jobs

Key Value
accept application/vnd.api+json
content-type application/vnd.api+json
revision 2025-01-15
Authorization Klaviyo-API-Key PRIVATEKEYHERE

 

JSON body

{
  "data": {
    "type": "profile-suppression-bulk-create-job",
    "attributes": {
      "profiles": {
        "data": [
          {
            "type": "profile",
            "attributes": {
              "email": "{{person.email}}"
            }
          }
        ]
      }
    }
  }
}

Save it and test it by clicking on “Preview” (just above the Destination URL) and then on “Send Test Request”. A green banner should appear with a success message. If you open the profile, it will appear as manually suppressed.

This should save you the trouble of having to manually suppress contacts every now and then!

 

Just if you are curious, this webhook makes an API call to Klaviyo’s Bulk Suppress Profiles endpoint. This tells your account that the contacts who triggered the event should be suppressed. This happens dynamically as you are using the variable {{person.email}}.

 

All best,

Andrés @ Melusine Studio // Klaviyo Master Gold

melusine.studio


Forum|alt.badge.img
  • Author
  • Contributor II
  • 3 replies
  • January 31, 2025

Thanks everyone!

I’ve just taken another look and considering the property needs to be assigned to a profile, I’m wondering if I should set it up a little different.

I have had a property assigned with “Accepts Marketing - True” for example and I have realised that our winback series has a mini sunset conditional split in it, where it removes the “accepts marketing  - true” on their profile, however, if the “accepts marketing” tag was never assigned to their profile, would I be better off updating their profile with “accepts marketing - false” then creating a segment that filters all of those profiles ready for suppression? 

With this in mind, would this also work for our Sunset flow?

I really appreciate everyone’s help with this. I set up these flows awhile ago and have only just realised things haven’t been working as anticipated!
 


Forum|alt.badge.img
  • Author
  • Contributor II
  • 3 replies
  • January 31, 2025
Hord wrote:

Thanks everyone!

I’ve just taken another look and considering the property needs to be assigned to a profile, I’m wondering if I should set it up a little different.

I have had a property assigned with “Accepts Marketing - True” for example and I have realised that our winback series has a mini sunset conditional split in it, where it removes the “accepts marketing  - true” on their profile, however, if the “accepts marketing” tag was never assigned to their profile, would I be better off updating their profile with “accepts marketing - false” then creating a segment that filters all of those profiles ready for suppression? 

With this in mind, would this also work for our Sunset flow?

I really appreciate everyone’s help with this. I set up these flows awhile ago and have only just realised things haven’t been working as anticipated
 

Just to add to the above - I found the “accept marketing true/false” not as clear cut as I’d hoped. So I have updated the Sunset flow to have it’s own tag - “Unengaged = True”. So those who have entered the flow and bypassed all the criteria to stay subscribed will then have their profile updated with Unengaged = True. I can then create a segment to find those specific people using this tag and then suppress - does this seem correct? Thanks!


emma.owens
Community Manager
Forum|alt.badge.img+9
  • Community Manager
  • 42 replies
  • Answer
  • February 3, 2025

@Hord That is exactly right! Setting up a new property labeled ‘Unengaged = True’ is typically what we recommend for a sunset flow. So if a profile makes it all the way to that step of the flow, that property will be added to their profile, and they will then be added to the segment you’ve created. From there, you would suppress the profiles in that Unengaged segment periodically!