Hi there @rsmith,

Thanks for sharing with examples!

Since the prettyDate is being appended to profiles as a property, you'll need to use a conditional split rather than a trigger split. In the conditional split you can specify 'Properties about Someone' and then choose how you would like to filter the value.

Hope that helped!
Alex

Hi @alex.hong,

Thanks for the reply, and apologies for the delayed response. Your answer sparked me to revisit the properties to double check. They were being passed over as properties of the event, but you got me digging and the it seems that the issue turned out to be convoluted properties from various rounds of testing. 

In previous API calls the properties, like “prettyDate”, were indeed being passed as properties of the profile. Then we adjusted them to be passed as properties of the event instead. However, it seems as if Klaviyo took issue to this and was perhaps still referencing them as profile properties, even when deleted from the profiles. When we added in a brand new event property into the API call with the existing properties the new property showed in the dimensions, but the other properties passed with it still did not.

We’re going to have the Klaviyo team purge the old properties to help resolve any confusion. 

Thanks again,

- Ryan

Hi there @rsmith,

Thanks for the detail and your thought process into the avenues you have explored. Hopefully you can come to a conclusion and get everything to work.

All the best,

Alex

I’m having the same issue. How do I purge my old properties as the solution here states?

Hi @gadabout!

You could do this by using an update property block in a flow, and setting it to no value, as described here:

Best,

Brian