Filterable Klaviyo event data

Every Klaviyo event Subi sends now carries a set of flat, top-level properties alongside the existing nested objects, so you can finally build a Klaviyo segment or a flow split on what Subi sends, without first restructuring the data yourself.

The Canceled Subscription event goes further: it now also carries cancellation_reason (the reason the customer selected, or their own typed-in text), and cancellation_initiated_by, showing whether the customer or the merchant cancelled the subscription. Previously, a cancellation event carried no reason or actor information at all, so a win-back flow triggered by a cancellation had no way to branch on why someone left or who ended the subscription.

This is separate from, and adds to, the cancellation reason already available on Subi's Subscription Canceled webhook: the webhook carries the same reason to your own systems, while this update makes the equivalent information directly filterable inside Klaviyo itself, without needing a webhook integration.

No setup is required. If you already have Subi connected to Klaviyo, the new properties are already arriving on new events; nothing changes for events sent before this update.