Skip to main content
Solved

Custom event properties not showing in trigger split


rsmith
Problem Solver I
Forum|alt.badge.img+2
  • Problem Solver I
  • 4 replies

Hi there,

We have a Metric based flow that utilizes a custom event added to Klaviyo via the Track API. We’re also passing several custom properties along with the event. The properties are available within SMS and email templates, for example: {{ event.prettyDate }} is pulling the correct information in.

However, the same properties are not available within the dimensions of a Trigger Split. We need to split our flow logic halfway through based on certain properties of the event, but none of the properties are showing as available. 

Any ideas or insight would be greatly appreciated! Screenshots attached for reference.

 

Thanks!
- Ryan

Best answer by rsmith

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

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

5 replies

alex.hong
Forum|alt.badge.img+58
  • Klaviyo Alum
  • 1552 replies
  • May 16, 2022

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


rsmith
Problem Solver I
Forum|alt.badge.img+2
  • Author
  • Problem Solver I
  • 4 replies
  • Answer
  • May 18, 2022

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


alex.hong
Forum|alt.badge.img+58
  • Klaviyo Alum
  • 1552 replies
  • May 23, 2022

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


Forum|alt.badge.img+1
  • Contributor I
  • 2 replies
  • November 14, 2023

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


Brian Turcotte
Forum|alt.badge.img+37

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