One use case that comes up often is if you have two Placed Order-like events, say one for online and one for physical POS, and you want to merge them into one Placed Order event. You could use a function triggered on each event, that uses the Klaviyo SDK to send a new “consolidated” event to the profile, with a property on the event’s source, and any other properties you’d want to include.

Hi Saulblum,

Thank you for the you for the example!

We are a online only B2C. Does anybody have use cases when it comes to automation of workflows, better segmentation, easier data collection or similar?

It’s a new feature, so I’m guessing not many customers are using it yet. The “merging of events” was a use case that often came up here inside Klaviyo.

Think of code as an expanded flow webhooks feature. If there were ever a flow webhook you couldn’t do, e.g. because of the need for conditional logic in the data posted to some third-party, you can do that now with a code function.

Another related use case would be to take event properties and save them to profile properties. See the example at https://help.klaviyo.com/hc/en-us/articles/18620644491035#h_01HA9ZWYAYTKHB6V7269WYS8S8

Also, if you have events coming in with properties not at the top-level (meaning you can’t segment off them), you could use a function to either send a new event with the needed properties at the top-level, or save those properties to profile properties.

That sounds great! Thank you for providing more examples.

The event to property especially sounds promising.

Hopefully there will emerge some cool use cases down the line also.