How to call dynamic values in profile property update?

Hi ​@asadhasan93 ,

It seems like you are on the right track by using a Conditional Split to update the Size Label based on the order placed. Since the profile property isn’t updating, there are a few things to check. Check the Trigger Event Data to ensure that the “Placed Order” event contains the correct product size data. You can do this by viewing a recent event under a test profile. If the size isn’t stored correctly, Klaviyo won’t be able to update the profile property. Confirm the Profile Update Step, and if you are using an "Update Profile Property" action in your flow, make sure that it is placed in the correct branch of the Conditional Split and that it correctly maps the size data from the event. Test with a Simple Update by trying a test flow that updates a different property (like a test label) to see if profile updates are working at all. If this doesn’t work, the issue might be with permissions or Klaviyo's ability to update profile data. Ensure the Property is Set to Overwrite because if the size property already exists in a customer’s profile, Klaviyo might not be overwriting it. Double-check that the flow allows updates rather than skipping existing values. If you can share more details on how you structured the Conditional Split and profile update action, I would be happy to take a closer look. Let me know how it goes!

Thanks ​@MANSIR2094,

Well, I didn’t use any product size label in my “Placed Order” because it will restrict it with only a specific value. I used “Placed Order” only so that whenever someone places an order it will automatically trigger and whatever the size customer chooses, it will automatically update the profile property according to the chosen size. Yeah, I am sharing how I structured the conditional split so that you can take a closer look.

You can check these images that how I structured my conditional split. If you want more pics, I will share them, or you need any further information I will love to share with you. If you think there are mistakes in my conditional split or in the structure, kindly do tell me.

Hey ​@asadhasan93,

I have reviewed the Klaviyo flow you shared, and I think I spotted a few issues that might be causing the conditional splits to misfire. It looks like the splits checking for specific "Size Label" values are coming up empty, with 100% of profiles saying "no". This could be because the "Size Label" property isn't being stored correctly in customer profiles, or maybe the data format is off.

For instance, it's possible that the "Size Label" is being stored as an event property from the "Placed Order" event, rather than a profile property. To get to the bottom of this, I recommend checking a few individual profiles to see if "Size Label" is even showing up.

If it's not there, we might need to tweak how we're storing this data when customers place orders. Instead of looking at profile properties, we should be checking event data from the "Placed Order" event. This will ensure we're pulling from the right place.

One more thing - the "Profile Property Update" step is showing zero updates, which suggests that the update action might not be working as expected. If we need to store "Size Label" as a profile property, we need to confirm that the update is happening before we start applying conditions based on it.

What would you like to do next? I can make these adjustments and run some tests to ensure everything is working smoothly.

Your Conditional Split might not be correctly identifying the size or updating the profile property as expected. Double-check that the condition logic matches the exact format of the size value being passed (e.g., "XL" vs. "xl"). Also, ensure that the profile update action is placed after the correct branch in your flow. If possible, test with different sizes and check logs or analytics to see if the flow is triggering.