I’m having an issue with this platform. You would think it would be straight forward and simple but it’s been very frustrating.
Here’s what I’m trying to do:
Once someone fills out the pop up form on the site, they get tagged as a ‘New Subscriber’ and enter the Welcome Series flow. If they make a purchase, they will enter into the Post-Purchase Series flow.
This is where I’m having the problems:
After a purchase, how do I set it to automatically remove the tag ‘New Subscriber’ and tag them as ‘Subscriber’? Because at this point they are already removed from the Welcome Series but in order to trigger the General Newsletter flow, they need the tag ‘Subscriber’ to do so.
Also, once a ‘New Subscriber’ completes the Welcome Series but didn’t purchase, how do I remove the ‘New Subscriber’ tag and add the tag ‘Subscriber’ that moves them into the General Newsletter flow?
I feel like this should be much simpler, I’ve tried to use the Profile Property Update action, but it doesn’t give me an option to delete the Profile Property ‘New Subscriber’ that I created once they entered the Welcome Series flow. It only says ‘Subscriber’ in the list of options, so there’s no way to update or delete the previous property that I created. How in the world could they from Welcome Series flow to the General Newsletter? This is very confusing.
Page 1 / 1
Hi @Tk0!
Thanks for your question! I’ll try to answer as much as I can.
First, you won’t be able to see a property in the drop down until at least one profile has that property filled in. I usually create the property (or properties) in my own profile as a test.
From your images, it looks like New Subscriber is a date field, and Subscriber is a text field. Since they are different kinds, you will need to use the Create and Delete property options, instead of update. (If they are the same type of field, please let me know).
In order to delete an existing property ie, New Subscriber, you need to change the first drop down from Update Existing Property to Delete Existing Property, then choose the correct property - your image #4. You would then add another step, choose Create Profile Property, choose Subscriber from the options, and fill what you want the propety to be - I believe it is also Subscriber in your case.
For customers that goe through the entire welcome flow without making a purchase, you are safe to add the New Subscriber property at the begining, delete it at the end, and add the Subscriber field.
I’m not sure how customers are removed from your welcome flow - perhaps you have profile or event triggers before each email send that removes subscribers who have purchased? If so, you could add a profile update to the post purchase flow at the beginning - use a conditional split that checks to see if the customer has the New Subscriber as a property. If so, delete it in the same way explained above, and add the Subscriber field. If they don’t have the New Subscriber field, then just add the Subscriber field. You can then re-join the splits before the emails begin. Hope this helps, let me know if I can explain anything further.
Thank you so much! That helped me out a lot. I had the second step as create new property = New Subscriber (value = New Subscriber) underneath in image 3, it was just cropped out.
But just to make sure that I have everything correct;
I updated the profile property in my own profile and it’s showing up as ‘New Subscriber’ in the list now, which is great.
I have at the beginning of the flow Profile Property Update with step 1 - create new property and stamping with date. Then in step 2 - Create new property = New Subscriber (Value = New Subscriber).
For each part of the flow, there is a filter not to send to anyone who has ‘Placed an Order’ over all time. I am going to create conditions that if they had between any email, then they would get the Profile Property Update before being removed from the flow.
At the end of the flow for non-purchasers, they will get a ‘Delete Existing Property’ then ‘Update Existing property’ to ‘Subscriber’ and then be moved to the next flow. For step 1, should I just have it as update existing property or leave it at delete existing property? Also, how would that affect step 2? Because it doesn’t populate the list with new subscriber in it.
For the ‘General Newsletter’ flow, can the trigger trigger be a property about someone? I think I remember seeing that somewhere but not sure if I remember correctly.
I think that covers everything I have so far, I appreciate your help and feedback!
Thank you so much!
Hi @Tk0, Everything you have so far looks pretty good! I see a few potential problems: In your first image, you have 2 properties with the same name: New Subscriber. I’m pretty sure one is date field and one is a text field, but I would would differentiate them in some way, like: New Subscriber Date - otherwise, when you use the delete property, you won’t be able to tell if you are deleting the time stamp OR the text field.
Also, since you have one field named New Subscriber and another field named Subscriber, you can’t update the existing property of Subscriber - because it doesn’t exist yet for someone who only has New Subscriber as a field. One idea might be to name the date field New Subscriber Date and name the text field Subscriber. Then, when creating the property, you can set the Subscriber field to New when they enter the welcome flow, and update it to Subscriber when they have finished (or purchased). This should solve your question under 4, I think.
You can trigger a flow by using a segment based on a property, but, unless it is an event property, they will only enter the flow once. For your general newsletter, I would suggest sending campaigns to a segment of customers who have the Subscriber text field set to Subscriber. Good luck! Happy to answer more questions next week!
Also, since you have one field named New Subscriber and another field named Subscriber, you can’t update the existing property of Subscriber - because it doesn’t exist yet for someone who only has New Subscriber as a field. One idea might be to name the date field New Subscriber Date and name the text field Subscriber. Then, when creating the property, you can set the Subscriber field to New when they enter the welcome flow, and update it to Subscriber when they have finished (or purchased). This should solve your question under 4, I think.
I’m not understanding what you mean by this…
Hi @Tk0! I’ll try to explain! I should have noted this yesterday: When you created the profile property fields in your own profile, they now exist as fields in general, so you can use them in flows. But they don’t exist for each profile - they need to be added to profiles, either via an import or through a flow as we are talking about.
One of the most important things (in my opinion) is paying attention to how your name your fields and what values you assign to them. For example, if one of your field names has a misspelling in an import, Klaviyo will create a new field with the misspelling, and then the misspelled field will be hard to use in segments and flows, etc. This is also true for capitalization - if you create a profiled property with the name Subscriber, but then later import or create a profile property with the name subscriber, you will then have 2 fields - one capitalized and one not. I understand why Klaviyo does this, but it means we as users have to be super careful!
So back to your question - in your first screen shot (from your reply, not the original question), it shows creating a new property of New Subscriber (date field) and then updating an existing property of New Subscriber (text field):
close up of first screen shot in Tk0’s first reply
Step 1 is fine, it will create the field of New Subscriber with a date value. However, I don’t think step 2 will work for new profiles - they don’t yet have a property of New Subscriber that is a text field, so there is nothing to update. I would change it to Create new property, then it will add the New Subscriber field (text field) to that profile with the value of New Subscriber. (This is also why I suggested changing one of the field names, because it will be hard to know which field you are deleting in subsequent steps - date stamp or text field. Unfortunately once a field is named, I don’t think you can change it. You would have to create a new profile property with the the new name, and then have Klaviyo support delete the field that is not needed.)
In the next two screen shots, it shows updating the existing property of Subscriber:
close up of second screen shot in TK0’s first reply
The issue I see is that a field named New Subscriber was created in the first screen shot, but the field named Subscriber was never created for that specific profile. So in close up 2, when it says to updated existing property, I don’t think it will work because that profile doesn’t yet have Subscriber as a property (just like step 2 in the first close up). So, instead of using Update exiting property for step 2 in screen shot 2, I would use Create New Property of Subscriber (value = Subscriber).
I hope this clears up some things! Starting tomorrow, I’ll be out of town for a few days, but I’ll be glad to explain more when I get back late next week, if needed!
Thank you so much Jessica. I think I figured it out with your help. I configured the segments to reflect a New subscriber vs a Subscriber based on your recommendation of creating a value of ‘New’ for the Subscriber. Once they purchase or finish the flow, they will be updated to Subscriber and move on to the next step which is my general news letter. For them to enter the news letter, they have to have the Updated Profile Property of ‘Subscriber’ or have made a purchase. I appreciate your feedback and help.
